Re: Re: sip questions

а) клиент - на помойку, потому что он этот :5060 всовывает даже в To: хедер, где это прямо и недвусмысленно запрещено стандартом.

б) не работает оно не поэтому. А потому, что у Вас sip.on-line.ru не прописан как алиас домена on-line.ru - вот он и пытается туда релеить...

On Fri, 9 Dec 2005 18:04:23 +0300
  "Vladimir Mendelevich" <CGatePro@mx.ru> wrote:
> Hello, Vladimir!
> You wrote to "CommuniGate Pro Russian Discussions" <CGatePro@mx.ru> on
>Thu,
> 08 Dec 2005 08:26:54 -0800:
>
> VAB> Нужен ЦЕЛИКОМ (SIPDATA-xxxxx 5 ) содержимое этого пакета INVITE.
> VAB> Который пришел на сервер. И - тот пакет, который он попытался
> VAB> отправить. И всё, что между ними.
>
> ---------------------
> 18:01:42.86 2 SIPDATA-62329 inp: req tcp [172.20.128.45:4488] INVITE(928
> bytes) sip:200@sip.on-line.ru:5060;user=phone
> 18:01:42.86 5 SIPDATA-62329 inp: INVITE
> sip:200@sip.on-line.ru:5060;user=phone SIP/2.0
> 18:01:42.86 5 SIPDATA-62329 inp: Via: SIP/2.0/TCP 172.20.128.45:10729
> 18:01:42.86 5 SIPDATA-62329 inp: Max-Forwards: 70
> 18:01:42.86 5 SIPDATA-62329 inp: From: "hedgehog@on-line.ru"
> <sip:hedgehog@on-line.ru>;tag=4a6623802add4918a18b7051bd10cb6a;epid=0f585961
> 27
> 18:01:42.86 5 SIPDATA-62329 inp: To:
> <sip:200@sip.on-line.ru:5060;user=phone>
> 18:01:42.86 5 SIPDATA-62329 inp: Call-ID: d92b16ce5e2d44cc8ec10d3b6f7a0319
> 18:01:42.86 5 SIPDATA-62329 inp: CSeq: 1 INVITE
> 18:01:42.86 5 SIPDATA-62329 inp: Contact:
> <sip:hedgehog@on-line.ru:10729;maddr=172.20.128.45;transport=tcp>;proxy=repl
> ace
> 18:01:42.86 5 SIPDATA-62329 inp: User-Agent: RTC/1.3
> 18:01:42.86 5 SIPDATA-62329 inp: Proxy-Authorization: NTLM qop="auth",
> realm="on-line.ru", opaque="ABCD004A", crand="4c731326", cnum="6",
> targetname="on-line.ru", response="0100000032333830176a8af862853469"
> 18:01:42.86 5 SIPDATA-62329 inp: Content-Type: application/sdp
> 18:01:42.86 5 SIPDATA-62329 inp: Content-Length: 264
> 18:01:42.86 5 SIPDATA-62329 inp:
> 18:01:42.86 5 SIPDATA-62329 inp: v=0
> 18:01:42.86 5 SIPDATA-62329 inp: o=- 0 0 IN IP4 172.20.128.45
> 18:01:42.86 5 SIPDATA-62329 inp: s=session
> 18:01:42.86 5 SIPDATA-62329 inp: c=IN IP4 172.20.128.45
> 18:01:42.86 5 SIPDATA-62329 inp: b=CT:1000
> 18:01:42.86 5 SIPDATA-62329 inp: t=0 0
> 18:01:42.86 5 SIPDATA-62329 inp: m=audio 53544 RTP/AVP 97 0 8 4 101
> 18:01:42.86 5 SIPDATA-62329 inp: a=rtpmap:97 red/8000
> 18:01:42.86 5 SIPDATA-62329 inp: a=rtpmap:0 PCMU/8000
> 18:01:42.86 5 SIPDATA-62329 inp: a=rtpmap:8 PCMA/8000
> 18:01:42.86 5 SIPDATA-62329 inp: a=rtpmap:4 G723/8000
> 18:01:42.86 5 SIPDATA-62329 inp: a=rtpmap:101 telephone-event/8000
> 18:01:42.86 5 SIPDATA-62329 inp: a=fmtp:101 0-16
> 18:01:42.86 5 SIPDATA-62329 Hash=96347
> 18:01:42.86 5 SIPS 6406: enqueued
> 18:01:42.86 2 SIPS-06406 enqueued
> 18:01:42.86 5 SIPS-06406 INITIAL posted
> 18:01:42.86 2 SIPDATA-62329 created SIPS-06406
> 18:01:42.86 5 SIPS(2) 6406: processing INITIAL
> 18:01:42.86 2 SIPS-06406 [62329] INVITE
> sip:200@sip.on-line.ru:5060;user=phone from tcp [172.20.128.45:4488]
> 18:01:42.86 4 SIP signer 'ABCD004A' retrieved
> 18:01:42.86 4 SIPS-06406 authenticated as 'menv@on-line.ru' by signature
> 18:01:42.86 4 SIPS-06406 dialog start from a signing endpoint
> 18:01:42.86 2 SIPDATA-62331 out: rsp tcp [172.20.128.45:4488]
>100-INVITE(517
> bytes)
> 18:01:42.86 5 SIPDATA-62331 out: SIP/2.0 100 Trying
> 18:01:42.86 5 SIPDATA-62331 out: Authentication-Info: NTLM
> rspauth="01000000000000004783cfd962853469",srand="4D3C5016",snum="7",
> opaque="ABCD004A", qop="auth", targetname="on-line.ru", realm="on-line.ru"
> 18:01:42.86 5 SIPDATA-62331 out: Via: SIP/2.0/TCP
> 172.20.128.45:10729;received=172.20.128.45
> 18:01:42.86 5 SIPDATA-62331 out: From: "hedgehog@on-line.ru"
> <sip:hedgehog@on-line.ru>;tag=4a6623802add4918a18b7051bd10cb6a;epid=0f585961
> 27
> 18:01:42.86 5 SIPDATA-62331 out: To:
> <sip:200@sip.on-line.ru:5060;user=phone>
> 18:01:42.86 5 SIPDATA-62331 out: Call-ID: d92b16ce5e2d44cc8ec10d3b6f7a0319
> 18:01:42.86 5 SIPDATA-62331 out: CSeq: 1 INVITE
> 18:01:42.86 5 SIPDATA-62331 out: Server: CommuniGatePro/5.0.3
> 18:01:42.86 5 SIPDATA-62331 out: Content-Length: 0
> 18:01:42.86 5 SIPDATA-62331 out:
> 18:01:42.86 4 SIPTCP-00063 [62331] enqueued. 517 bytes
> 18:01:42.86 2 SIPS-06406 [62331] 100-INVITE(trying) sent to tcp
> [172.20.128.45:4488]
> 18:01:42.86 2 SIPS-06406 created SIGNAL-06318
> 18:01:42.86 5 SIPS(2) 6406: idling
> 18:01:42.86 5 SIPTCP-00063 out: SIP/2.0 100 Trying\r\nAuthentication-Info:
> NTLM rspauth="01000000000000004783cfd962853469",srand="4D3C5016",snum="7",
> opaque="ABCD004A", qop="auth", targetname="on-line.ru",
> realm="on-line.ru"\r\nVia: SIP/2.0/TCP
> 172.20.128.45:10729;received=172.20.128.45\r\nFrom: "he
> 18:01:42.86 2 SIGNAL-06318 SIPS-06406: INVITE
> sip:200@sip.on-line.ru:5060;user=phone
> 18:01:42.86 4 SIPTCP-00063 [62331] sent to [172.20.128.45:4488]
> 18:01:42.86 2 SIGNAL-06318 INVITE sip:200@sip.on-line.ru:5060;user=phone
>via
> sip:200@sip.on-line.ru:5060;user=phone
> 18:01:42.86 2 SIGNAL-06318 relaying to sip:200@sip.on-line.ru:5060 via
> sip:sip.on-line.ru:5060
> 18:01:42.86 5 SIPC 5026: enqueued
> 18:01:42.86 2 SIPC-05026 enqueued
> 18:01:42.86 5 SIPC-05026 INITIAL posted
> 18:01:42.86 2 SIGNAL-06318 INVITE relayed to SIPC-05026:
> sip:200@sip.on-line.ru:5060
> 18:01:42.86 5 SIPC(3) 5026: processing INITIAL
> 18:01:42.86 2 SIPC-05026 INVITE sip:200@sip.on-line.ru:5060 via
> sip:sip.on-line.ru:5060
> 18:01:42.86 4 SIPC-05026 resolving sip:sip.on-line.ru:5060
> 18:01:42.86 4 SIPC-05026 resolved: 1 address(es)
> 18:01:42.86 4 SIPC-05026 trying: sip:213.247.194.65:5060
> 18:01:42.86 3 SIPC-05026 failed to send to [213.247.194.65:5060]. Error
> Code=SIP loop detected
> 18:01:42.86 1 SIPC-05026 sending failed. Error Code=SIP loop detected
> 18:01:42.86 5 SIPC(3) 5026: killing
> 18:01:42.86 2 SIPC-05026 dequeued
> 18:01:42.86 2 SIGNAL-06318 483 received from SIPC-05026
> 18:01:42.86 5 SIPS-06406 FINAL posted
> 18:01:42.86 5 SIPS(1) 6406: processing FINAL
> 18:01:42.86 2 SIPDATA-62332 out: rsp tcp [172.20.128.45:4488]
>483-INVITE(549
> bytes)
> 18:01:42.86 5 SIPDATA-62332 out: SIP/2.0 483 SIP loop detected
> 18:01:42.86 5 SIPDATA-62332 out: Authentication-Info: NTLM
> rspauth="0100000000000000e14d67d562853469",srand="4D3C5016",snum="8",
> opaque="ABCD004A", qop="auth", targetname="on-line.ru", realm="on-line.ru"
> 18:01:42.86 5 SIPDATA-62332 out: Via: SIP/2.0/TCP
> 172.20.128.45:10729;received=172.20.128.45
> 18:01:42.86 5 SIPDATA-62332 out: From: "hedgehog@on-line.ru"
> <sip:hedgehog@on-line.ru>;tag=4a6623802add4918a18b7051bd10cb6a;epid=0f585961
> 27
> 18:01:42.86 5 SIPDATA-62332 out: To:
> <sip:200@sip.on-line.ru:5060;user=phone>;tag=CD545826AA1DF58A
> 18:01:42.86 5 SIPDATA-62332 out: Call-ID: d92b16ce5e2d44cc8ec10d3b6f7a0319
> 18:01:42.86 5 SIPDATA-62332 out: CSeq: 1 INVITE
> 18:01:42.86 5 SIPDATA-62332 out: Server: CommuniGatePro/5.0.3
> 18:01:42.86 5 SIPDATA-62332 out: Content-Length: 0
> 18:01:42.86 5 SIPDATA-62332 out:
> 18:01:42.86 4 SIPTCP-00063 [62332] enqueued. 549 bytes
> 18:01:42.86 2 SIPS-06406 [62332] 483-INVITE(final) sent to tcp
> [172.20.128.45:4488]
> 18:01:42.86 4 SIPS-06406 completed
> 18:01:42.86 5 SIPS-06406 timeout set for 32 secs
> 18:01:42.86 5 SIPS(1) 6406: enqueued (32 secs)
> 18:01:42.86 5 SIPTCP-00063 out: SIP/2.0 483 SIP loop
> detected\r\nAuthentication-Info: NTLM
> rspauth="0100000000000000e14d67d562853469",srand="4D3C5016",snum="8",
> opaque="ABCD004A", qop="auth", targetname="on-line.ru",
> realm="on-line.ru"\r\nVia: SIP/2.0/TCP
> 172.20.128.45:10729;received=172.20.128.45\r
> 18:01:42.86 4 SIPTCP-00063 [62332] sent to [172.20.128.45:4488]
> 18:01:42.99 2 SIPDATA-62330 inp: req tcp [172.20.128.45:4488] ACK(556
>bytes)
> sip:200@sip.on-line.ru:5060;user=phone
> 18:01:42.99 5 SIPDATA-62330 inp: ACK
>sip:200@sip.on-line.ru:5060;user=phone
> SIP/2.0
> 18:01:42.99 5 SIPDATA-62330 inp: Via: SIP/2.0/TCP 172.20.128.45:10729
> 18:01:42.99 5 SIPDATA-62330 inp: Max-Forwards: 70
> 18:01:42.99 5 SIPDATA-62330 inp: From: "hedgehog@on-line.ru"
> <sip:hedgehog@on-line.ru>;tag=4a6623802add4918a18b7051bd10cb6a;epid=0f585961
> 27
> 18:01:42.99 5 SIPDATA-62330 inp: To:
> <sip:200@sip.on-line.ru:5060;user=phone>;tag=CD545826AA1DF58A
> 18:01:42.99 5 SIPDATA-62330 inp: Call-ID: d92b16ce5e2d44cc8ec10d3b6f7a0319
> 18:01:42.99 5 SIPDATA-62330 inp: CSeq: 1 ACK
> 18:01:42.99 5 SIPDATA-62330 inp: User-Agent: RTC/1.3
> 18:01:42.99 5 SIPDATA-62330 inp: Proxy-Authorization: NTLM qop="auth",
> realm="on-line.ru", opaque="ABCD004A", crand="733e331d", cnum="7",
> targetname="on-line.ru", response="01000000323338302eee232662853469"
> 18:01:42.99 5 SIPDATA-62330 inp: Content-Length: 0
> 18:01:42.99 5 SIPDATA-62330 inp:
> 18:01:42.99 5 SIPDATA-62330 Hash=96347
> 18:01:42.99 5 SIPS-06406 SUPPL posted
> 18:01:42.99 2 SIPDATA-62330 sent to SIPS-06406
> 18:01:42.99 5 SIPS(3) 6406: processing SUPPL
> 18:01:42.99 2 SIPS-06406 [62330] confirmed: ACK received
> 18:01:42.99 5 SIPS(3) 6406: killing
> 18:01:42.99 2 SIPS-06406 dequeued
> -----------------------
>
> Это?
>
> Звонок осуществляется из WM посредством нажатия на кнопочку make a phone
> call. Если нажимать make a conversation, то невозможно посылать DTMF. Но в
> Make a conversation все работает как надо. То-есть, я получаю ответ от
>pbx.
>
>
> С уважением,
>
> Сетевой отдел компании "1С-Рарус"
> UIN:9244669
> Phone:+7(095)250-6393

Sincerely,
Vladimir Получено Fri Dec 09 15:36:26 2005