Hi,

Is anyone on here successfully using X-Lite, or a Nokia phone with
CGate Pro & VoIP?

I have X-Lite, and a Nokia VOIP phone registering with CGate Pro. I
can also make outbound calls.

However, for some weird reason, the calls are getting disconnected it
seems about 60 seconds after the call started - and I cannot determine
why. From reading traces it appears CG is sending 200 OK messages to
X-Lite and the Nokia phone, and seems to never receiving ACKs from
those 200s.


Looking at Logs I see this right about the time of disconnection:


19:25:23.857 2 SIPDATA-000320 out: rsp [10.0.69.5]:5060 ->
udp[10.0.69.166]:5060 200-INVITE(836 bytes)

19:25:23.857 5 SIPDATA-000320 out: SIP/2.0 200 OK

19:25:23.857 5 SIPDATA-000320 out: v: SIP/2.0/UDP
10.0.69.166:5060;branch=z9hG4bK6e9rc67ikd3eai2q9o89u3b;rport=5060

19:25:23.857 5 SIPDATA-000320 out: Record-Route: <sip:14.dialog.cgatepro;lr>

19:25:23.857 5 SIPDATA-000320 out: Record-Route: <sip:10.0.69.5:5060;lr>

19:25:23.857 5 SIPDATA-000320 out: f:
<sip:sean@Watkins.silk.com>;tag=lbu4s41bfdhc65ntl71g

19:25:23.857 5 SIPDATA-000320 out: t:
<sip:4039744000@watkins.silk.com;user=phone>;tag=000000000000012-E0BCFF4C-451E5F49

19:25:23.857 5 SIPDATA-000320 out: i: 41Be44emoId7YWD3DILOjI_V6niH7D

19:25:23.857 5 SIPDATA-000320 out: CSeq: 1038 INVITE

19:25:23.857 5 SIPDATA-000320 out: m: <sip:signode-12-451E5F49@10.0.69.5>

19:25:23.857 5 SIPDATA-000320 out: User-Agent: CommuniGatePro-callLeg/5.2.13

19:25:23.857 5 SIPDATA-000320 out: Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,REFER

19:25:23.857 5 SIPDATA-000320 out: c: application/sdp

19:25:23.857 5 SIPDATA-000320 out: l: 265

19:25:23.857 5 SIPDATA-000320 out:

19:25:23.857 5 SIPDATA-000320 out: v=0

19:25:23.857 5 SIPDATA-000320 out: o=CGPLeg000012 2666622609
1333311305 IN IP4 10.0.69.5

19:25:23.857 5 SIPDATA-000320 out: s=FreeSWITCH

19:25:23.857 5 SIPDATA-000320 out: c=IN IP4 72.55.158.156

19:25:23.857 5 SIPDATA-000320 out: t=0 0

19:25:23.857 5 SIPDATA-000320 out: m=audio 21654 RTP/AVP 0 98 13

19:25:23.857 5 SIPDATA-000320 out: c=IN IP4 72.55.158.156

19:25:23.857 5 SIPDATA-000320 out: a=rtpmap:0 PCMU/8000

19:25:23.857 5 SIPDATA-000320 out: a=rtpmap:98 telephone-event/8000

19:25:23.857 5 SIPDATA-000320 out: a=fmtp:98 0-16

19:25:23.857 5 SIPDATA-000320 out: a=rtpmap:13 CN/8000

19:25:23.857 5 SIPDATA-000320 out: a=ptime:20

19:25:23.857 5 SIP [10.0.69.5]:5060 -> [10.0.69.166]:5060 out(836):
SIP/2.0 200 OK\r\nv: SIP/2.0/UDP
10.0.69.166:5060;branch=z9hG4bK6e9rc67ikd3eai2q9o

19:25:23.857 2 SIPS-000194 [000320] 200-INVITE(final) sent
[10.0.69.5]:5060 -> udp[10.0.69.166]:5060

19:25:23.857 5 SIPS-000194 timeout set for 32 secs

19:25:23.857 5 SIPS(1) 000194: enqueued (32 secs)



Which is when the call connects -



I am seeing my endping sending the ACK


19:25:24.254 5 SIP [10.0.69.5]:5060 -> [72.55.158.156]:5060 out(475):
ACK sip:mod_sofia@72.55.158.156:5060;transport=udp SIP/2.0\r\nv:
SIP/2.0/UDP 10.0.

19:25:24.255 2 SIPC-000034 [000322] ACK
sip:mod_sofia@72.55.158.156:5060;transport=udp sent [10.0.69.5]:5060
-> udp[72.55.158.156]:5060

19:25:24.255 5 SIPC(3) 000034: killing

19:25:24.255 4 SIPC-000034 dequeued

19:25:24.324 5 SIP [10.0.69.5]:5060 <- [10.0.69.166]:5060 inp(744):
ACK sip:signode-12-451E5F49@10.0.69.5 SIP/2.0\r\nRoute:
<sip:10.0.69.5:5060;lr>,<s

19:25:24.325 2 SIPDATA-000323 inp: req [10.0.69.5]:5060 <-
udp[10.0.69.166]:5060 ACK(744 bytes) sip:signode-12-451E5F49@10.0.69.5

19:25:24.325 5 SIPDATA-000323 inp: ACK sip:signode-12-451E5F49@10.0.69.5 SIP/2.0

19:25:24.325 5 SIPDATA-000323 inp: Route:
<sip:10.0.69.5:5060;lr>,<sip:14.dialog.cgatepro;lr>

19:25:24.325 5 SIPDATA-000323 inp: Via: SIP/2.0/UDP
10.0.69.166:5060;branch=z9hG4bKmou83fgkqad7si2q9o8ddgj;rport

19:25:24.325 5 SIPDATA-000323 inp: To:
<sip:4039744000@watkins.silk.com;user=phone>;tag=000000000000012-E0BCFF4C-451E5F49

19:25:24.325 5 SIPDATA-000323 inp: From:
<sip:sean@Watkins.silk.com>;tag=lbu4s41bfdhc65ntl71g

19:25:24.325 5 SIPDATA-000323 inp: Call-ID: 41Be44emoId7YWD3DILOjI_V6niH7D

19:25:24.325 5 SIPDATA-000323 inp: CSeq: 1038 ACK

19:25:24.325 5 SIPDATA-000323 inp: Supported: sec-agree

19:25:24.325 5 SIPDATA-000323 inp: Max-Forwards: 70

19:25:24.325 5 SIPDATA-000323 inp:+Authorization: Digest
qop=auth,realm="emachine.*",nonce="BB7A7D8A8CE9D12F8014",opaque="opaqueData",alg

orithm=MD5,username="sean",cnonce="*",nc=00000001,uri="sip:4039744000@watkins.silk.com;user=phone",resp

19:25:24.325 5 SIPDATA-000323 inp: onse="1d74c8fb7bdd567d38ef4c92cbf9585b"

19:25:24.325 5 SIPDATA-000323 inp: Content-Length: 0

19:25:24.325 5 SIPDATA-000323 inp:

19:25:24.325 4 SIPDATA-000323 Hash=1299503642

19:25:24.325 4 SIPDATA-000323 self-route removed: <sip:10.0.69.5:5060;lr>

19:25:24.325 4 SIPDATA-000323 special route detected: sip:14.dialog.cgatepro;lr

19:25:24.325 2 SIPDATA-000323 stand-alone ACK

19:25:27.000 5 SIPS(3) 000188: timeout

19:25:27.000 4 SIPS-000188 J-timer over

19:25:27.000 5 SIPS(3) 000188: killing

19:25:27.000 4 SIPS-000188 dequeued

19:25:38.965 5 SIP [10.0.69.5]:50




Which CGatePro seems to never process, and sends more 200 OKs – 60
seconds later it hangs up the call.



Since this is happening on 2 clients, could it be something in my configuration?



Sean

#############################################################
This message is sent to you because you are subscribed to
 the mailing list <CGatePro@mail.stalker.com>.
To unsubscribe, E-mail to: <CGatePro-off@mail.stalker.com>
To switch to the DIGEST mode, E-mail to <CGatePro-digest@mail.stalker.com>
To switch to the INDEX mode, E-mail to <CGatePro-index@mail.stalker.com>
Send administrative queries to  <CGatePro-request@mail.stalker.com>