The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

форумы  помощь  поиск  регистрация  майллист  вход/выход  слежка  RSS
"CISCO ATA 186. Вхлдящие звонки, тишина и обрывы"
Вариант для распечатки  
Пред. тема | След. тема 
Форум Маршрутизаторы CISCO и др. оборудование. (VoIP)
Изначальное сообщение [ Отслеживать ]

"CISCO ATA 186. Вхлдящие звонки, тишина и обрывы"  +/
Сообщение от disia (ok) on 20-Фев-11, 21:10 
Есть Cisco ATA 186, прошивка SIP 3.02.01(050616A) за NAT'ом, аккаунт на одном из западных VOIP серверов и DID с третей стороны. Когда входящий звонок идет на X-LIte - все хорошо, но когда получаю на сиську с обоих сторон тишина и через несколько секунд связь обрывается. На сайте провайдера DID номера написано: supports G.711 u-Law, G.711 A-Law, GSM, G.729 A, and RFC2833.

В циске:

AudioMode: 0x00150015
ConnectMode: 0x00060400

Внешний адрес перед натом, указан

дебаг с циски:

SIP/2.0 200 OK
Via: SIP/2.0/UDP *.*.*.*;branch=z9hG4bK53af.9e17f5d6.0
Via: SIP/2.0/UDP *.*.*.*:5062;rport=5062;branch=z9hG4bKtea0amKKSm72e
Record-Route: <sip:*.*.*.*;lr=on;ftag=F566811r0rXvB;did=c4b.17da9654>
From: "***" <sip:**********@*.*.*.*>;tag=F566811r0rXvB
To: <sip:**********@*.*.*.*>;tag=3044210215
Call-ID: fbf5b57d-b7bc-122e-ac88-0025900af16e
CSeq: 8776101 INVITE
Contact: ****** <sip:**********@*.*.*.*:5060;user=phone;transport=udp>
Server: Cisco ATA 186  v3.2.1 atasip (050616A)
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE

Supported: replaces
Content-Length: 198
Content-Type: application/sdp

v=0
o=********** 34831 34831 IN IP4 10.0.0.5
s=ATA186 Call
c=IN IP4 *.*.*.*
t=0 0
m=audio 16384 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

[0]R2INV Retry 5
[0:0]Re-Tx Msg to *.*.*.*:5060

SIP/2.0 200 OK
Via: SIP/2.0/UDP *.*.*.*;branch=z9hG4bK53af.9e17f5d6.0
Via: SIP/2.0/UDP *.*.*.*:5062;rport=5062;branch=z9hG4bKtea0amKKSm72e
Record-Route: <sip:*.*.*.*;lr=on;ftag=F566811r0rXvB;did=c4b.17da9654>
From: "***" <sip:**********@*.*.*.*>;tag=F566811r0rXvB
To: <sip:**********@*.*.*.*>;tag=3044210215
Call-ID: fbf5b57d-b7bc-122e-ac88-0025900af16e
CSeq: 8776101 INVITE
Contact: ****** <sip:**********@*.*.*.*:5060;user=phone;transport=ud
p>
Server: Cisco ATA 186  v3.2.1 atasip (050616A)
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE

Supported: replaces
Content-Length: 198
Content-Type: application/sdp

v=0
o=********** 34831 34831 IN IP4 10.0.0.5
s=ATA186 Call
c=IN IP4 *.*.*.*
t=0 0
m=audio 16384 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

[0]REGISTER Retry 0
[0:0]Tx Msg to *.*.*.*:5060

REGISTER sip:sip.somevoip.com SIP/2.0
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK774c6fb2408fc3d1
From: ****** <sip:**********@sip.somevoip.com;user=phone>;tag=706039628
To: ****** <sip:**********@sip.somevoip.com;user=phone>
Call-ID: 4147718014@*.*.*.*
CSeq: 5 REGISTER
Contact: ****** <sip:**********@*.*.*.*:5060;user=phone;transport=ud
p>;expires=120
User-Agent: Cisco ATA 186  v3.2.1 atasip (050616A)
Authorization: Digest username="**********",realm="sip.somevoip.com",nonce="TWF
Ux01hU5t8XbQC/hd5c+GmH/FWBsL2",uri="sip:sip.somevoip.com",response="bb6f7f57ed
701ae751ca8e8f0d2a43c2"
Content-Length: 0


[1]REGISTER Retry 0
[1:0]Tx Msg to *.*.*.*:5060

REGISTER sip:sip.somevoip.com SIP/2.0
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK286d4c421312ebb9
From: ******_CH <sip:******@sip.somevoip.com;user=phone>;tag=37908994
18
To: ******_CH <sip:******@sip.somevoip.com;user=phone>
Call-ID: 1629569896@*.*.*.*
CSeq: 5 REGISTER
Contact: ******_CH <sip:******@*.*.*.*:5060;user=phone;transport
=udp>;expires=120
User-Agent: Cisco ATA 186  v3.2.1 atasip (050616A)
Authorization: Digest username="******",realm="sip.somevoip.com",nonce="TWF
Ux01hU5t8XbQC/hd5c+GmH/FWBsL2",uri="sip:sip.somevoip.com",response="a346ccdce7
6fbfe53cb1170fcca1e70d"
Content-Length: 0


[0]Rx Msg from *.*.*.*:5060

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK774c6fb2408fc3d1;rport=1024
From: ****** <sip:**********@sip.somevoip.com;user=phone>;tag=706039628
To: ****** <sip:**********@sip.somevoip.com;user=phone>;tag=05fa965d41f3a
dc51e16f9a7acf1c273.2d6a
Call-ID: 4147718014@*.*.*.*
CSeq: 5 REGISTER
WWW-Authenticate: Digest realm="sip.somevoip.com", nonce="TWFWAE1hVNT2joPY20eN
OQBt7FyJqYu8"
Server: CWU SIP GW
Content-Length: 0


[0]Reg Resp 401; Unauthorized
[0]REGISTER Retry 0
[0:0]Tx Msg to *.*.*.*:5060

REGISTER sip:sip.somevoip.com SIP/2.0
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK7e92a64c3d1526ce
From: ****** <sip:**********@sip.somevoip.com;user=phone>;tag=706039628
To: ****** <sip:**********@sip.somevoip.com;user=phone>
Call-ID: 4147718014@*.*.*.*
CSeq: 6 REGISTER
Contact: ****** <sip:**********@*.*.*.*:5060;user=phone;transport=ud
p>;expires=120
User-Agent: Cisco ATA 186  v3.2.1 atasip (050616A)
Authorization: Digest username="**********",realm="sip.somevoip.com",nonce="TWF
WAE1hVNT2joPY20eNOQBt7FyJqYu8",uri="sip:sip.somevoip.com",response="5b761bd2ca
9f5098fc8b8427af0402ad"
Content-Length: 0


[1]Rx Msg from *.*.*.*:5060

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK286d4c421312ebb9;rport=1024
From: ******_CH <sip:******@sip.somevoip.com;user=phone>;tag=37908994
18
To: ******_CH <sip:******@sip.somevoip.com;user=phone>;tag=05fa965d41
f3adc51e16f9a7acf1c273.53e2
Call-ID: 1629569896@*.*.*.*
CSeq: 5 REGISTER
WWW-Authenticate: Digest realm="sip.somevoip.com", nonce="TWFWAE1hVNT2joPY20eN
OQBt7FyJqYu8"
Server: CWU SIP GW
Content-Length: 0


[1]Reg Resp 401; Unauthorized
[1]REGISTER Retry 0
[1:0]Tx Msg to *.*.*.*:5060

REGISTER sip:sip.somevoip.com SIP/2.0
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK261a06b12d3110a4
From: ******_CH <sip:******@sip.somevoip.com;user=phone>;tag=37908994
18
To: ******_CH <sip:******@sip.somevoip.com;user=phone>
Call-ID: 1629569896@*.*.*.*
CSeq: 6 REGISTER
Contact: ******_CH <sip:******@*.*.*.*:5060;user=phone;transport
=udp>;expires=120
User-Agent: Cisco ATA 186  v3.2.1 atasip (050616A)
Authorization: Digest username="******",realm="sip.somevoip.com",nonce="TWF
WAE1hVNT2joPY20eNOQBt7FyJqYu8",uri="sip:sip.somevoip.com",response="f6654189be
b1cab065bed4d89435a33f"
Content-Length: 0


[0]Rx Msg from *.*.*.*:5060

SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK7e92a64c3d1526ce;rport=1024
From: ****** <sip:**********@sip.somevoip.com;user=phone>;tag=706039628
To: ****** <sip:**********@sip.somevoip.com;user=phone>;tag=05fa965d41f3a
dc51e16f9a7acf1c273.e877
Call-ID: 4147718014@*.*.*.*
CSeq: 6 REGISTER
Contact: <sip:**********@*.*.*.*:5060;user=phone;transport=udp>;expires=12
0;received="sip:*.*.*.*:1024"
Server: CWU SIP GW
Content-Length: 0


[0]Reg Resp 200; OK
[0]Reg OK (120)
NextReg in 104
[1]Rx Msg from *.*.*.*:5060

SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK261a06b12d3110a4;rport=1024
From: ******_CH <sip:******@sip.somevoip.com;user=phone>;tag=37908994
18
To: ******_CH <sip:******@sip.somevoip.com;user=phone>;tag=05fa965d41
f3adc51e16f9a7acf1c273.b81e
Call-ID: 1629569896@*.*.*.*
CSeq: 6 REGISTER
Contact: <sip:******@*.*.*.*:5060;user=phone;transport=udp>;expires=12
0;received="sip:*.*.*.*:1024"
Server: CWU SIP GW
Content-Length: 0


[1]Reg Resp 200; OK
[1]Reg OK (120)
NextReg in 104
[0]R2INV Retry 6
[0:0]Re-Tx Msg to *.*.*.*:5060

SIP/2.0 200 OK
Via: SIP/2.0/UDP *.*.*.*;branch=z9hG4bK53af.9e17f5d6.0
Via: SIP/2.0/UDP *.*.*.*:5062;rport=5062;branch=z9hG4bKtea0amKKSm72e
Record-Route: <sip:*.*.*.*;lr=on;ftag=F566811r0rXvB;did=c4b.17da9654>
From: "***" <sip:**********@*.*.*.*>;tag=F566811r0rXvB
To: <sip:**********@*.*.*.*>;tag=3044210215
Call-ID: fbf5b57d-b7bc-122e-ac88-0025900af16e
CSeq: 8776101 INVITE
Contact: ****** <sip:**********@*.*.*.*:5060;user=phone;transport=ud
p>
Server: Cisco ATA 186  v3.2.1 atasip (050616A)
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE

Supported: replaces
Content-Length: 198
Content-Type: application/sdp

v=0
o=********** 34831 34831 IN IP4 10.0.0.5
s=ATA186 Call
c=IN IP4 *.*.*.*
t=0 0
m=audio 16384 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

[0]R2INV Retry 7
[0:0]Re-Tx Msg to *.*.*.*:5060

SIP/2.0 200 OK
Via: SIP/2.0/UDP *.*.*.*;branch=z9hG4bK53af.9e17f5d6.0
Via: SIP/2.0/UDP *.*.*.*:5062;rport=5062;branch=z9hG4bKtea0amKKSm72e
Record-Route: <sip:*.*.*.*;lr=on;ftag=F566811r0rXvB;did=c4b.17da9654>
From: "***" <sip:**********@*.*.*.*>;tag=F566811r0rXvB
To: <sip:**********@*.*.*.*>;tag=3044210215
Call-ID: fbf5b57d-b7bc-122e-ac88-0025900af16e
CSeq: 8776101 INVITE
Contact: ****** <sip:**********@*.*.*.*:5060;user=phone;transport=ud
p>
Server: Cisco ATA 186  v3.2.1 atasip (050616A)
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE

Supported: replaces
Content-Length: 198
Content-Type: application/sdp

v=0
o=********** 34831 34831 IN IP4 10.0.0.5
s=ATA186 Call
c=IN IP4 *.*.*.*
t=0 0
m=audio 16384 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

6:00;0,0,0,0,
R2INV TO; NoAltProxy
Timeout waiting for ACK
[0]BYE Retry 0
[0:0]Tx Msg to *.*.*.*:5060

BYE sip:**********@*.*.*.*:5062 SIP/2.0
Route: <sip:*.*.*.*;lr=on;ftag=F566811r0rXvB;did=c4b.17da9654>
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK75e7bb7f34c78ef0
From: sip:**********@*.*.*.*;tag=3044210215
To: "***" <sip:**********@*.*.*.*>;tag=F566811r0rXvB
Call-ID: fbf5b57d-b7bc-122e-ac88-0025900af16e
CSeq: 1 BYE
User-Agent: Cisco ATA 186  v3.2.1 atasip (050616A)
Content-Length: 0


[0]Rx Msg from *.*.*.*:5060

SIP/2.0 200 OK
Via: SIP/2.0/UDP *.*.*.*:1459;branch=z9hG4bK75e7bb7f34c78ef0
From: sip:**********@*.*.*.*;tag=3044210215
To: "***" <sip:**********@*.*.*.*>;tag=F566811r0rXvB
Call-ID: fbf5b57d-b7bc-122e-ac88-0025900af16e
CSeq: 1 BYE
User-Agent: CWU SIP GW
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, NOTIFY
Supported: timer, precondition, path, replaces
Content-Length: 0


Got BYE/CANCEL Resp
SCC:ev=13[0:0] 6 0
[0]StartTone 2

Ответить | Правка | Cообщить модератору

Оглавление

Сообщения по теме [Сортировка по времени | RSS]


1. "CISCO ATA 186. Вхлдящие звонки, тишина и обрывы"  +/
Сообщение от disia (ok) on 20-Фев-11, 21:11 
И еще уточнение, проблема только с этим DID провайдером, с другими все работает нормально
Ответить | Правка | ^ к родителю #0 | Наверх | Cообщить модератору

Архив | Удалить

Рекомендовать для помещения в FAQ | Индекс форумов | Темы | Пред. тема | След. тема




Партнёры:
PostgresPro
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру