Sip-trunk м\у нами и провайдером.

Модератор: Administrator

Ответить
Yerbol
Участник форума
Сообщения: 138
Зарегистрирован: Вт 27 май 2008, 09:04
Откуда: Казахстан

Sip-trunk м\у нами и провайдером.

Сообщение Yerbol »

День добрый.

Скажите плиз как решить проблему с Sip-trunk м\у нами и провайдером.

Звонки сразу отбиваются.

CLAN address: 10.198.2.155

SES: 10.198.2.240

Address SIP provider: 195.40.255.90

Есть еще один адррес: 88.205.191.248 это public address наш который мы дали провайдеру. При выходе из нашей сети firewall подемняет наш

внутрений SES: 10.198.2.240 на 88.205.191.248.

Провайдер от нас получает пакеты и он говорит нам следу ющие вещи:

1. Yerbol Test" <sip:77787460000@akcoavayases.com> должен быть <sip:+77787460000@>88.205.191.248

что отправить провайдеру вот так вот :"+77787460000@>88.205.191.248" где мне прописать этот аддресс: 88.205.191.248???

2. "77012112416" <sip:77012112416@195.40.255.90> дожен быть "77012112416" <sip:+77012112416@195.40.255.90

"+" - как отправить? как на авая станций прописать?

Еще один вопрос: IP network region должен быть отдельным?

Сейчас у меня SES и карта CLAN в одном регионе.




Feb 4 12:08:31 2015 matching filter label <hosts>: kzatavayases.okioc.com: [Send Request ]
{connection: host=195.40.255.90 port=5060 protocol=UDP}
INVITE sip:77012112416@195.40.255.90 SIP/2.0
Call-ID: 0e042af54bbe41d5b05407ebb00
CSeq: 1 INVITE
From: "Yerbol Test" <sip:77787460000@akcoavayases.com>;tag=0e042af54bbe41d4b05407ebb00
Record-Route: <sip:10.198.2.240:5060;lr>,<sip:10.198.2.155:5061;lr;transport=tls>
To: "77012112416" <sip:77012112416@195.40.255.90>
Via:SIP/2.0/UDP 10.198.2.240:5060;branch=z9hG4bK0303035656560303034dc53.0,SIP/2.0/TLS 10.198.2.155;psrrposn=2;received=10.198.2.155;branch=z9hG4bK0e042af54bbe41d6b05407ebb00
Content-Length: 234
Content-Type: application/sdp
Contact: "Yerbol Yelzhanov" <sip:77787460000@10.198.2.155>
Max-Forwards: 70
User-Agent: Avaya CM/R015x.02.1.016.4
Allow: INVITE,CANCEL,BYE,ACK,PRACK,SUBSCRIBE,NOTIFY,REFER,OPTIONS,INFO,PUBLISH
Supported: timer,replaces,join,histinfo,100rel
Alert-Info: <cid:internal@195.40.255.90>;avaya-cm-alert-type=internal
Min-SE: 1200
Session-Expires: 1200;refresher=uac
P-Asserted-Identity: "Yerbol Yelzhanov" <sip:77787460000@akcoavayases.com:5061>
History-Info: <sip:77012112416@195.40.255.90>;index=1,"77012112416" <sip:77012112416@195.40.255.90>;index=1.1

v=0
o=- 1 1 IN IP4 10.198.2.155
s=-
c=IN IP4 10.198.2.250
b=AS:64
t=0 0
m=audio 3028 RTP/AVP 8 18 0 127
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:127 telephone-event/8000




12:08:31 active station 2277 cid 0x21cb
12:08:31 G711A ss:off ps:20
rgn:2 [10.191.224.197]:2422
rgn:2 [10.191.2.250]:3016
12:08:32 dial 087012112416 route:ARS
12:08:32 term trunk-group 123 cid 0x21cb
12:08:32 dial 087012112416 route:ARS
12:08:32 route-pattern 779 preference 1 cid 0x21cb
12:08:32 seize trunk-group 123 member 3 cid 0x21cb
12:08:32 Setup digits 77012112416
12:08:32 Calling Number & Name 77787460000 Yerbol Test
12:08:32 Proceed trunk-group 123 member 3 cid 0x21cb
12:08:32 denial event 1192: Temporary failure D1=0x8b2e D2=0x29
12:08:32 idle trunk-group 123 member 3 cid 0x21cb
12:08:33 idle station 2277 cid 0x21cb
sliber
Постоянный участник форума
Сообщения: 176
Зарегистрирован: Пт 30 авг 2013, 09:06
Откуда: Москва

Re: Sip-trunk м\у нами и провайдером.

Сообщение sliber »

Yerbol писал(а):День добрый.

Скажите плиз как решить проблему с Sip-trunk м\у нами и провайдером.

Звонки сразу отбиваются.

CLAN address: 10.198.2.155

SES: 10.198.2.240

Address SIP provider: 195.40.255.90

Есть еще один адррес: 88.205.191.248 это public address наш который мы дали провайдеру. При выходе из нашей сети firewall подемняет наш

внутрений SES: 10.198.2.240 на 88.205.191.248.

Провайдер от нас получает пакеты и он говорит нам следу ющие вещи:

1. Yerbol Test" <sip:77787460000@akcoavayases.com> должен быть <sip:+77787460000@>88.205.191.248

что отправить провайдеру вот так вот :"+77787460000@>88.205.191.248" где мне прописать этот аддресс: 88.205.191.248???

2. "77012112416" <sip:77012112416@195.40.255.90> дожен быть "77012112416" <sip:+77012112416@195.40.255.90

"+" - как отправить? как на авая станций прописать?

Еще один вопрос: IP network region должен быть отдельным?

Сейчас у меня SES и карта CLAN в одном регионе.




Feb 4 12:08:31 2015 matching filter label <hosts>: kzatavayases.okioc.com: [Send Request ]
{connection: host=195.40.255.90 port=5060 protocol=UDP}
INVITE sip:77012112416@195.40.255.90 SIP/2.0
Call-ID: 0e042af54bbe41d5b05407ebb00
CSeq: 1 INVITE
From: "Yerbol Test" <sip:77787460000@akcoavayases.com>;tag=0e042af54bbe41d4b05407ebb00
Record-Route: <sip:10.198.2.240:5060;lr>,<sip:10.198.2.155:5061;lr;transport=tls>
To: "77012112416" <sip:77012112416@195.40.255.90>
Via:SIP/2.0/UDP 10.198.2.240:5060;branch=z9hG4bK0303035656560303034dc53.0,SIP/2.0/TLS 10.198.2.155;psrrposn=2;received=10.198.2.155;branch=z9hG4bK0e042af54bbe41d6b05407ebb00
Content-Length: 234
Content-Type: application/sdp
Contact: "Yerbol Yelzhanov" <sip:77787460000@10.198.2.155>
Max-Forwards: 70
User-Agent: Avaya CM/R015x.02.1.016.4
Allow: INVITE,CANCEL,BYE,ACK,PRACK,SUBSCRIBE,NOTIFY,REFER,OPTIONS,INFO,PUBLISH
Supported: timer,replaces,join,histinfo,100rel
Alert-Info: <cid:internal@195.40.255.90>;avaya-cm-alert-type=internal
Min-SE: 1200
Session-Expires: 1200;refresher=uac
P-Asserted-Identity: "Yerbol Yelzhanov" <sip:77787460000@akcoavayases.com:5061>
History-Info: <sip:77012112416@195.40.255.90>;index=1,"77012112416" <sip:77012112416@195.40.255.90>;index=1.1

v=0
o=- 1 1 IN IP4 10.198.2.155
s=-
c=IN IP4 10.198.2.250
b=AS:64
t=0 0
m=audio 3028 RTP/AVP 8 18 0 127
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:127 telephone-event/8000




12:08:31 active station 2277 cid 0x21cb
12:08:31 G711A ss:off ps:20
rgn:2 [10.191.224.197]:2422
rgn:2 [10.191.2.250]:3016
12:08:32 dial 087012112416 route:ARS
12:08:32 term trunk-group 123 cid 0x21cb
12:08:32 dial 087012112416 route:ARS
12:08:32 route-pattern 779 preference 1 cid 0x21cb
12:08:32 seize trunk-group 123 member 3 cid 0x21cb
12:08:32 Setup digits 77012112416
12:08:32 Calling Number & Name 77787460000 Yerbol Test
12:08:32 Proceed trunk-group 123 member 3 cid 0x21cb
12:08:32 denial event 1192: Temporary failure D1=0x8b2e D2=0x29
12:08:32 idle trunk-group 123 member 3 cid 0x21cb
12:08:33 idle station 2277 cid 0x21cb
Cause Value 41
[0x29/0xA9] -
Temporary Failure
The call cannot be completed because the ISDN network is functioning incorrectly. The condition is not likely to last a long period of
time. The call will complete if the user reattempts the call.
Cause Value 41 also indicates:
• The failure of channel negotiation at the terminating interface.
• A data link layer malfunction has occurred locally or at the remote network interface.
• The call is cleared as a result of one or more protocol errors at the remote network interface.
See also Cause Value 63 on page 36 and Cause Value 79 on page 38.

Cause Value 63
[0x3F/0xBF] -
Service or option not available, unspecified
This Cause Value indicates that the requested service or option is unavailable when no other cause in the Service or option not
available class applies. Event Data
Release 6.3 June 2014 37
As an implementation option, this Cause Value either passes to the user or is mapped to Cause Value 41 (Temporary Failure) when
it is received at a CO as part of SS7 call handling.
Communication Manager does not originate Cause Value 63
Cause Value 79
[0x4F/0xCF] -
Service or option not implemented, unspecified
The call cannot be completed because the equipment sending this Cause Value has not implemented a service, feature, or
supplementary service requested by the user, and none of the other Cause Values in the Service or option apply.
As an implementation option, this Cause Value is mapped to Cause Value 41 (Temporary Failure) when it is received at a CO as
part of SS7 call handling.
Communication Manager does not originate Cause Value 79.
sliber
Постоянный участник форума
Сообщения: 176
Зарегистрирован: Пт 30 авг 2013, 09:06
Откуда: Москва

Re: Sip-trunk м\у нами и провайдером.

Сообщение sliber »

sliber писал(а):
Yerbol писал(а):День добрый.

Скажите плиз как решить проблему с Sip-trunk м\у нами и провайдером.

Звонки сразу отбиваются.

CLAN address: 10.198.2.155

SES: 10.198.2.240

Address SIP provider: 195.40.255.90

Есть еще один адррес: 88.205.191.248 это public address наш который мы дали провайдеру. При выходе из нашей сети firewall подемняет наш

внутрений SES: 10.198.2.240 на 88.205.191.248.

Провайдер от нас получает пакеты и он говорит нам следу ющие вещи:

1. Yerbol Test" <sip:77787460000@akcoavayases.com> должен быть <sip:+77787460000@>88.205.191.248

что отправить провайдеру вот так вот :"+77787460000@>88.205.191.248" где мне прописать этот аддресс: 88.205.191.248???

2. "77012112416" <sip:77012112416@195.40.255.90> дожен быть "77012112416" <sip:+77012112416@195.40.255.90

"+" - как отправить? как на авая станций прописать?

Еще один вопрос: IP network region должен быть отдельным?

Сейчас у меня SES и карта CLAN в одном регионе.




Feb 4 12:08:31 2015 matching filter label <hosts>: kzatavayases.okioc.com: [Send Request ]
{connection: host=195.40.255.90 port=5060 protocol=UDP}
INVITE sip:77012112416@195.40.255.90 SIP/2.0
Call-ID: 0e042af54bbe41d5b05407ebb00
CSeq: 1 INVITE
From: "Yerbol Test" <sip:77787460000@akcoavayases.com>;tag=0e042af54bbe41d4b05407ebb00
Record-Route: <sip:10.198.2.240:5060;lr>,<sip:10.198.2.155:5061;lr;transport=tls>
To: "77012112416" <sip:77012112416@195.40.255.90>
Via:SIP/2.0/UDP 10.198.2.240:5060;branch=z9hG4bK0303035656560303034dc53.0,SIP/2.0/TLS 10.198.2.155;psrrposn=2;received=10.198.2.155;branch=z9hG4bK0e042af54bbe41d6b05407ebb00
Content-Length: 234
Content-Type: application/sdp
Contact: "Yerbol Yelzhanov" <sip:77787460000@10.198.2.155>
Max-Forwards: 70
User-Agent: Avaya CM/R015x.02.1.016.4
Allow: INVITE,CANCEL,BYE,ACK,PRACK,SUBSCRIBE,NOTIFY,REFER,OPTIONS,INFO,PUBLISH
Supported: timer,replaces,join,histinfo,100rel
Alert-Info: <cid:internal@195.40.255.90>;avaya-cm-alert-type=internal
Min-SE: 1200
Session-Expires: 1200;refresher=uac
P-Asserted-Identity: "Yerbol Yelzhanov" <sip:77787460000@akcoavayases.com:5061>
History-Info: <sip:77012112416@195.40.255.90>;index=1,"77012112416" <sip:77012112416@195.40.255.90>;index=1.1

v=0
o=- 1 1 IN IP4 10.198.2.155
s=-
c=IN IP4 10.198.2.250
b=AS:64
t=0 0
m=audio 3028 RTP/AVP 8 18 0 127
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:127 telephone-event/8000




12:08:31 active station 2277 cid 0x21cb
12:08:31 G711A ss:off ps:20
rgn:2 [10.191.224.197]:2422
rgn:2 [10.191.2.250]:3016
12:08:32 dial 087012112416 route:ARS
12:08:32 term trunk-group 123 cid 0x21cb
12:08:32 dial 087012112416 route:ARS
12:08:32 route-pattern 779 preference 1 cid 0x21cb
12:08:32 seize trunk-group 123 member 3 cid 0x21cb
12:08:32 Setup digits 77012112416
12:08:32 Calling Number & Name 77787460000 Yerbol Test
12:08:32 Proceed trunk-group 123 member 3 cid 0x21cb
12:08:32 denial event 1192: Temporary failure D1=0x8b2e D2=0x29
12:08:32 idle trunk-group 123 member 3 cid 0x21cb
12:08:33 idle station 2277 cid 0x21cb
Cause Value 41
[0x29/0xA9] -
Temporary Failure
The call cannot be completed because the ISDN network is functioning incorrectly. The condition is not likely to last a long period of
time. The call will complete if the user reattempts the call.
Cause Value 41 also indicates:
• The failure of channel negotiation at the terminating interface.
• A data link layer malfunction has occurred locally or at the remote network interface.
• The call is cleared as a result of one or more protocol errors at the remote network interface.
See also Cause Value 63 on page 36 and Cause Value 79 on page 38.

Cause Value 63
[0x3F/0xBF] -
Service or option not available, unspecified
This Cause Value indicates that the requested service or option is unavailable when no other cause in the Service or option not
available class applies. Event Data
Release 6.3 June 2014 37
As an implementation option, this Cause Value either passes to the user or is mapped to Cause Value 41 (Temporary Failure) when
it is received at a CO as part of SS7 call handling.
Communication Manager does not originate Cause Value 63
Cause Value 79
[0x4F/0xCF] -
Service or option not implemented, unspecified
The call cannot be completed because the equipment sending this Cause Value has not implemented a service, feature, or
supplementary service requested by the user, and none of the other Cause Values in the Service or option apply.
As an implementation option, this Cause Value is mapped to Cause Value 41 (Temporary Failure) when it is received at a CO as
part of SS7 call handling.
Communication Manager does not originate Cause Value 79.
Вот для 5
Cause Value 41
[0x29/0xA9] -
Temporary Failure
The call was not completed because the ISDN network is not functioning correctly. The
condition is not likely to last a long period of time. If the user attempts the call again it will
probably complete.
Cause Value 41 might also indicate:
• The failure of channel negotiation at the terminating interface.
• A data link layer malfunction has occurred locally or at the remote network interface.
• The call is being cleared as a result of one or more protocol errors at the remote network
interface.
See also Cause Value 63 on page 42 and Cause Value 79 on page 45.
Cause Value 63
[0x3F/0xBF] -
Service or option not available, unspecified
This Cause Value indicates that the requested service or option is unavailable when no other
cause in the Service or option not available class applies.
As an implementation option, this Cause Value shall either be passed to the user or mapped to
Cause Value 41 (Temporary Failure) when it is received at a CO as part of SS7 call handling.
Communication Manager does not originate Cause Value 63
Cause Value 79
[0x4F/0xCF] -
Service or option not implemented, unspecified
The call could not be completed because the equipment sending this Cause Value has not
implemented a service, feature, or supplementary service requested by the user, and none of
the other Cause Values in the Service or option not implemented class apply.
As an implementation option, this Cause Value might be mapped to Cause Value 41 (Temporary
Failure) when it is received at a CO as part of SS7 call handling.
Communication Manager does not originate Cause Value 79.
gosha
Постоянный участник форума
Сообщения: 967
Зарегистрирован: Чт 18 сен 2008, 23:05

Re: Sip-trunk м\у нами и провайдером.

Сообщение gosha »

А NATилку как зовут?
Yerbol
Участник форума
Сообщения: 138
Зарегистрирован: Вт 27 май 2008, 09:04
Откуда: Казахстан

Re: Sip-trunk м\у нами и провайдером.

Сообщение Yerbol »

Добрый день звонок проходить но не слышно вообще подскажите где копать?

Contact: "Yerbol Test" <sip:77787460000@10.198.2.155> как здесь поменять на 88.205.191.248???

Feb 9 16:01:05 2015 matching filter label <hosts>: kzatses.okioc.com: [Send Request ]
{connection: host=195.47.255.97 port=5060 protocol=UDP}
INVITE sip:77012112416@195.40.255.90 SIP/2.0
Call-ID: 80a079d6e2b9e41795d5407ebb00
CSeq: 1 INVITE
From: Yerbol Test" <sip:77787460000@akcoavayases.com>;tag=80a079d6e2b9e41785d5407ebb00
Record-Route: <sip:10.198.2.240:5060;lr>,<sip:10.198.2.155:5061;lr;transport=tls>
To: "77012112416" <sip:77012112416@195.40.255.90>
Via: SIP/2.0/UDP 10.198.2.240:5060;branch=z9hG4bK83838303030316161629fda.0,SIP/2.0/TLS 10.198.2.155;psrrposn=2;received=10.198.2.155;branch=z9hG4bK80a079d6e2b9e417a5d5407ebb00
Content-Length: 234
Content-Type: application/sdp
Contact: "Yerbol Test" <sip:77787460000@10.198.2.155>
Max-Forwards: 70
User-Agent: Avaya CM/R015x.02.1.016.4
Allow: INVITE,CANCEL,BYE,ACK,PRACK,SUBSCRIBE,NOTIFY,REFER,OPTIONS,INFO,PUBLISH
Supported: timer,replaces,join,histinfo,100rel
Alert-Info: <cid:internal@195.40.255.90 >;avaya-cm-alert-type=internal
Min-SE: 1200
Session-Expires: 1200;refresher=uac
P-Asserted-Identity: "Yerbol Test" <sip:77787460000@ 88.205.191.248:5061>
History-Info: <sip:77012112416@195.40.255.90>;index=1,"77012112416" <sip:77012112416@195.40.255.90>;index=1.1

v=0
o=- 1 1 IN IP4 10.198.2.155
s=-
c=IN IP4 10.198.2.158
b=AS:64
t=0 0
m=audio 3248 RTP/AVP 8 18 0 127
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:127 telephone-event/8000
gosha
Постоянный участник форума
Сообщения: 967
Зарегистрирован: Чт 18 сен 2008, 23:05

Re: Sip-trunk м\у нами и провайдером.

Сообщение gosha »

Для начала - посмотреть такую же трассировку, но на внешнем интерфейсе firewall'а
Ответить