nokia E70 и communigate

От: Oleg Shumsky <CGatePro_at_mx_ru>
Дата: Thu 02 Nov 2006 - 17:35:51 MSK


Здравствуйте.

Коллеги, я снова буду раздражать вас глупыми вопросами :)

Итак, есть 5.1.0 и модифицированный gatewaycaller. Всяческие зухели, sjphone и прочее работают нормально. Но вот в парке железа появилась Nokia E70.

Все выглядит следующим образом. Абонент набирает какой-либо номер (в pstn сети), звонок проходит. На другом конце поднимают трубку, дальше нокие говорит "Услуга интернет телефонии недоступна".

Теперь как это выглядит внутри:

Я так понял, что все дело в 491-м коде. А что это за код? И что с ним должно происходить в gatewaycaller ?

Спасибо!

18:33:53.824 2 SIPDATA-000492 inp: req [0.0.0.0]:5060 <- udp [83.102.163.30]:5060 INVITE(768 bytes)
sip:signode-26-E6D8FF75@195.14.50.93 18:33:53.824 5 SIPDATA-000492 inp: INVITE sip:signode-26-E6D8FF75@195.14.50.93
SIP/2.0 18:33:53.824 5 SIPDATA-000492 inp: Via: SIP/2.0/UDP 83.102.163.30:5060;branch=z9hG4bKo2o9os99r1hc6dt10fqo073

18:33:53.824 5 SIPDATA-000492 inp: To:
<sip:8901yyyyyyy@sip.corbina.ru>;tag=000000000000026-46F8BED0-E6D8FF75

18:33:53.824 5 SIPDATA-000492 inp: From: <sip:xxxx@sip.corbina.ru>;tag=ht99osdfs5hc6rsnttjp

18:33:53.824 5 SIPDATA-000492 inp: Contact: <sip:xxxx@83.102.163.30>

18:33:53.824 5 SIPDATA-000492 inp: Call-ID: NaOsssscoIfH9-ZDIZ_DhTKjPlVc0z

18:33:53.824 5 SIPDATA-000492 inp: CSeq: 1766 INVITE 18:33:53.824 5 SIPDATA-000492 inp: Allow: INVITE,ACK,BYE,CANCEL,REFER,NOTIFY 18:33:53.824 5 SIPDATA-000492 inp: expires: 120

18:33:53.824 5 SIPDATA-000492 inp: Max-Forwards: 70

18:33:53.824 5 SIPDATA-000492 inp: Content-Type: application/sdp

18:33:53.824 5 SIPDATA-000492 inp: Accept: application/sdp

18:33:53.824 5 SIPDATA-000492 inp: Content-Length: 257

18:33:53.824 5 SIPDATA-000492
inp:

18:33:53.824 5 SIPDATA-000492 inp:
v=0

18:33:53.824 5 SIPDATA-000492 inp: o=Nokia-SIPUA 63330662041396250 63330662041396251 IN IP4
83.102.163.30 18:33:53.824 5 SIPDATA-000492 inp:
s=-

18:33:53.824 5 SIPDATA-000492 inp: c=IN IP4 83.102.163.30

18:33:53.824 5 SIPDATA-000492 inp: t=0
0

18:33:53.824 5 SIPDATA-000492 inp: m=audio 16386 RTP/AVP 0 98

18:33:53.824 5 SIPDATA-000492 inp:
a=sendrecv

18:33:53.824 5 SIPDATA-000492 inp:
a=ptime:20

18:33:53.824 5 SIPDATA-000492 inp:
a=maxptime:200

18:33:53.824 5 SIPDATA-000492 inp: a=fmtp:98 0-15

18:33:53.824 5 SIPDATA-000492 inp: a=rtpmap:0 PCMU/8000/1 18:33:53.824 5 SIPDATA-000492 inp: a=rtpmap:98 telephone-event/8000/1

18:33:53.824 4 SIPDATA-000492
Hash=949513668

18:33:53.824 4 SIPDATA-000492 request for a local object

18:33:53.824 5 SIPS 228:
enqueued

18:33:53.824 2 SIPS-000228
enqueued

18:33:53.824 5 SIPS-000228 INITIAL
posted

18:33:53.824 2 SIPDATA-000492 created
SIPS-000228 18:33:53.824 5 SIPS(67) 228: processing INITIAL 18:33:53.824 2 SIPS-000228 [000492] INVITE sip:signode-26-E6D8FF75@195.14.50.93 from udp [83.102.163.30]:5060 18:33:53.824 2 SIPDATA-000493 out: rsp [0.0.0.0]:5060 -> udp [83.102.163.30]:5060 100-INVITE(348
bytes) 18:33:53.824 5 SIPDATA-000493 out: SIP/2.0 100 Trying

18:33:53.824 5 SIPDATA-000493 out: Via: SIP/2.0/UDP 83.102.163.30:5060;branch=z9hG4bKo2o9os99r1hc6dt10fqo073

18:33:53.824 5 SIPDATA-000493 out: To:
<sip:8901yyyyyyy@sip.corbina.ru>;tag=000000000000026-46F8BED0-E6D8FF75

18:33:53.824 5 SIPDATA-000493 out: From: <sip:xxxx@sip.corbina.ru>;tag=ht99osdfs5hc6rsnttjp

18:33:53.824 5 SIPDATA-000493 out: Call-ID: NaOsssscoIfH9-ZDIZ_DhTKjPlVc0z

18:33:53.824 5 SIPDATA-000493 out: CSeq: 1766 INVITE 18:33:53.824 5 SIPDATA-000493 out: Server: CommuniGatePro/5.1.0 _trial_

18:33:53.824 5 SIPDATA-000493 out: Content-Length: 0

18:33:53.824 5 SIPDATA-000493
out:

18:33:53.824 5 SIP [0.0.0.0]:5060 -> [83.102.163.30]:5060 out(348): SIP/2.0 100 Trying\r\nVia: SIP/2.0/UDP
83.102.163.30:5060;branch=z9hG4bKo2o9os
18:33:53.824 2 SIPS-000228 [000493] 100-INVITE(trying) sent to udp [83.102.163.30]:5060

18:33:53.824 2 SIGNAL-000256
enqueued

18:33:53.824 2 SIPS-000228 created
SIGNAL-000256 18:33:53.824 5 SIPS(67) 228:
idling

18:33:53.824 2 SIGNAL-000256 SIPS-000228: INVITE sip:signode-26-E6D8FF75@195.14.50.93

18:33:53.824 2 SIGNAL-000256 INVITE sip:signode-26-E6D8FF75@195.14.50.93 via sip:signode-26-E6D8FF75@195.14.50.93 18:33:53.824 2 SIGNAL-000256 {1} sent to NODE-000026: INVITE sip:signode-26-E6D8FF75@195.14.50.93

18:33:53.824 3 PBXLEG-000026 INVITE: bad leg status=4

18:33:53.824 2 SIGNAL-000256 491 received from NODE-000026 18:33:53.824 2 SIGNAL-000256 491
relaying

18:33:53.824 5 SIPS-000228 FINAL
posted

18:33:53.824 2 SIGNAL-000256
dequeued

18:33:53.824 5 SIPS(21) 228: processing FINAL 18:33:53.824 2 SIPDATA-000494 out: rsp [0.0.0.0]:5060 -> udp [83.102.163.30]:5060 491-INVITE(357
bytes) 18:33:53.824 5 SIPDATA-000494 out: SIP/2.0 491 Request pending

18:33:53.824 5 SIPDATA-000494 out: Via: SIP/2.0/UDP 83.102.163.30:5060;branch=z9hG4bKo2o9os99r1hc6dt10fqo073

18:33:53.824 5 SIPDATA-000494 out: To:
<sip:8901yyyyyyy@sip.corbina.ru>;tag=000000000000026-46F8BED0-E6D8FF75

18:33:53.824 5 SIPDATA-000494 out: From: <sip:xxxx@sip.corbina.ru>;tag=ht99osdfs5hc6rsnttjp

18:33:53.824 5 SIPDATA-000494 out: Call-ID: NaOsssscoIfH9-ZDIZ_DhTKjPlVc0z

18:33:53.824 5 SIPDATA-000494 out: CSeq: 1766 INVITE 18:33:53.824 5 SIPDATA-000494 out: Server: CommuniGatePro/5.1.0 _trial_

18:33:53.824 5 SIPDATA-000494 out: Content-Length: 0

18:33:53.824 5 SIPDATA-000494
out:

18:33:53.824 5 SIP [0.0.0.0]:5060 -> [83.102.163.30]:5060 out(357): SIP/2.0 491 Request pending\r\nVia: SIP/2.0/UDP 83.102.163.30:5060;branch=z9hG
18:33:53.824 2 SIPS-000228 [000494] 491-INVITE(final) sent to udp [83.102.163.30]:5060

18:33:53.824 4 SIPS-000228
completed

18:33:53.824 5 SIPS-000228 timeout set for 2 secs

18:33:53.824 5 SIPS(21) 228: enqueued (2 secs)

18:33:53.825 5 SIP [0.0.0.0]:5060 <- [83.102.163.30]:5060 inp(291): SIP/2.0 100 Trying\r\nVia: SIP/2.0/UDP
195.14.50.93:5060;branch=z9hG4bK44;rpor
18:33:53.825 2 SIPDATA-000495 inp: rsp [0.0.0.0]:5060 <- udp [83.102.163.30]:5060 100-INVITE(291
bytes) 18:33:53.825 5 SIPDATA-000495 inp: SIP/2.0 100 Trying

18:33:53.825 5 SIPDATA-000495 inp: Via: SIP/2.0/UDP 195.14.50.93:5060;branch=z9hG4bK44;rport

18:33:53.825 5 SIPDATA-000495 inp: To:
<sip:xxxx@sip.corbina.ru>;tag=ht99osdfs5hc6rsnttjp

18:33:53.825 5 SIPDATA-000495 inp: From: <sip:8901yyyyyyy@sip.corbina.ru>;tag=000000000000026-46F8BED0-E6D8FF75

18:33:53.825 5 SIPDATA-000495 inp: Call-ID: NaOsssscoIfH9-ZDIZ_DhTKjPlVc0z

18:33:53.825 5 SIPDATA-000495 inp: CSeq: 1 INVITE 18:33:53.825 5 SIPDATA-000495 inp: Content-Length: 0

18:33:53.825 5 SIPDATA-000495
inp:

18:33:53.825 5 SIPC-000044 RESPONSE
posted

18:33:53.825 2 SIPDATA-000495 sent to
SIPC-000044 18:33:53.825 5 SIPC(57) 44: processing
RESPONSE 18:33:53.825 2 SIPC-000044 [000495] 100-INVITE received

18:33:53.825 5 SIPC-000044 timeout set for 180 secs

18:33:53.825 5 SIPC(57) 44: enqueued (180 secs)

18:33:53.831 3 MEDIA-000007 mixing noise=100%, overflows=00%, avgLevel=0000

18:33:53.832 5 SIP [0.0.0.0]:5060 <- [83.102.163.30]:5060 inp(335): SIP/2.0 491 Request Pending\r\nVia: SIP/2.0/UDP 195.14.50.93:5060;branch=z9hG4
18:33:53.832 2 SIPDATA-000496 inp: rsp [0.0.0.0]:5060 <- udp [83.102.163.30]:5060 491-INVITE(335
bytes) 18:33:53.832 5 SIPDATA-000496 inp: SIP/2.0 491 Request Pending

18:33:53.832 5 SIPDATA-000496 inp: Via: SIP/2.0/UDP 195.14.50.93:5060;branch=z9hG4bK44;rport

18:33:53.832 5 SIPDATA-000496 inp: To:
<sip:xxxx@sip.corbina.ru>;tag=ht99osdfs5hc6rsnttjp

18:33:53.832 5 SIPDATA-000496 inp: Contact: <sip:xxxx@83.102.163.30>

18:33:53.832 5 SIPDATA-000496 inp: From: <sip:8901yyyyyyy@sip.corbina.ru>;tag=000000000000026-46F8BED0-E6D8FF75

18:33:53.832 5 SIPDATA-000496 inp: Call-ID: NaOsssscoIfH9-ZDIZ_DhTKjPlVc0z

18:33:53.832 5 SIPDATA-000496 inp: CSeq: 1 INVITE 18:33:53.832 5 SIPDATA-000496 inp: Content-Length: 0

18:33:53.832 5 SIPDATA-000496
inp:

18:33:53.832 5 SIPC-000044 RESPONSE
posted

18:33:53.832 5 SIPC-000044 RESPONSE
posted

18:33:53.832 2 SIPDATA-000496 sent to
SIPC-000044 18:33:53.832 5 SIPC(58) 44: processing
RESPONSE 18:33:53.832 2 SIPC-000044 [000496] 491-INVITE received

18:33:53.832 4 SIPC-000044 completed, sending ACK 18:33:53.832 4 SIPC-000044 sending
ACK 18:33:53.832 2 SIPDATA-000497 out: req [195.14.50.93]:0 -> udp [83.102.163.30]:5060 ACK(369 bytes)
sip:xxxx@83.102.163.30 18:33:53.832 5 SIPDATA-000497 out: ACK sip:xxxx@83.102.163.30 SIP/2.0 18:33:53.832 5 SIPDATA-000497 out: P-Asserted-Identity: <sip:ext@sip.corbina.ru>

18:33:53.832 5 SIPDATA-000497 out: Via: SIP/2.0/UDP 195.14.50.93:5060;branch=z9hG4bK44;rport

18:33:53.832 5 SIPDATA-000497 out: Max-Forwards: 70

18:33:53.832 5 SIPDATA-000497 out: To:
<sip:xxxx@sip.corbina.ru>;tag=ht99osdfs5hc6rsnttjp

18:33:53.832 5 SIPDATA-000497 out: From: <sip:8901yyyyyyy@sip.corbina.ru>;tag=000000000000026-46F8BED0-E6D8FF75

18:33:53.832 5 SIPDATA-000497 out: Call-ID: NaOsssscoIfH9-ZDIZ_DhTKjPlVc0z

18:33:53.832 5 SIPDATA-000497 out: CSeq: 1 ACK 18:33:53.832 5 SIPDATA-000497 out: Content-Length: 0

18:33:53.832 5 SIPDATA-000497
out:

18:33:53.832 5 SIP [0.0.0.0]:5060 -> [83.102.163.30]:5060 out(369): ACK sip:xxxx@83.102.163.30 SIP/2.0\r\nP-Asserted-Identity: <sip:ext@sip.corbin 18:33:53.832 2 SIPC-000044 [000497] ACK sip:xxxx@83.102.163.30 sent [195.14.50.93]:0 -> udp
[83.102.163.30]:5060 18:33:53.832 5 SIPC-000044 timeout set for 32 secs

18:33:53.832 5 SIPC(58) 44: enqueued (32 secs)

18:33:53.832 2 SIGNAL-000254 491 received from SIPC-000044 18:33:53.832 2 SIGNAL-000254 491
relaying

18:33:53.832 2 SIGNAL-000254
dequeued

18:33:53.832 3 PBXLEG-000026 collision detected, resending

18:33:53.832 2 SIGNAL-000258
enqueued

если нужно дальше, то могу прислать.

-- 
Oleg V. Shumsky
Corbina Telecom NOC, VoIP Dept. Ph.: +7 495 7284000, ext. 2174, ICQ: 110474048
Получено Thu Nov 02 14:35:53 2006

Этот архив был сгенерирован hypermail 2.1.8 : Fri 24 Apr 2015 - 16:15:11 MSK