< Previous by Date Date Index Next by Date >
  Thread Index Next in Thread >

[reSIProcate] Getting unexpected debug errors


Hi,

After getting about 5 or 6 "100 trying" messages in the logs, I got two "180 Ringing"
messages....   See below.

resiprocate/dum/DialogUsageManager.cxx:1493 | Looking for dialogSet: 168292200d150dd4@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs-368b0749 in map: resiprocate/dum/DialogUsageManager.cxx:1494 | [758371fd332c54a1@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs-7345b4b3 -> 0x65878b0, 168292200d150dd4@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs-368b0749 -> 0x659b420] resiprocate/dum/DialogUsageManager.cxx:1395 | DialogUsageManager::processResponse: SipResp: 100 tid=7dd0abc84b784a53 cseq=INVITE / 1 from(wire) resiprocate/Transport.cxx:209 | incoming from: [ V4 213.167.79.25:5060 UDP received on: Transport: [ V4 0.0.0.0:5060 UDP connectionId=0 ] connectionId=0 ] resiprocate/TransactionState.cxx:1535 | Send to TU: TU: DialogUsageManager size=0

This is the response I'm getting back.....
-------------------------------------------
SIP/2.0 180 Ringing R002180550192370401414752M000
To: <sip:u218055@xxxxxxxxxxxxxx>;tag=64bd007ce1ca4c3a953ba264d9776e99
From: <sip:u354@xxxxxxxxxxxxx:5060>;tag=368b0749
Via: SIP/2.0/UDP 192.168.0.4:5060;branch=z9hG4bK-d87543-7dd0abc84b784a53-1--d87543-;rport
Call-ID: 168292200d150dd4@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs
CSeq: 1 INVITE <---- Note: Cseq is not incrementing like the RFC says it's supposed to.
User-Agent: RTC/1.3
Content-Length: 0


resiprocate/dum/DialogUsageManager.cxx:830 | Got: SipResp: 180 tid=7dd0abc84b784a53 cseq=INVITE / 1 from(wire) resiprocate/dum/DialogUsageManager.cxx:1380 | DialogUsageManager::processResponse:

Remote server sends it again....
--------------------------------------------------------------------
SIP/2.0 180 Ringing R002180550192370401414752M000
To: <sip:u218055@xxxxxxxxxxxxxx>;tag=64bd007ce1ca4c3a953ba264d9776e99
From: <sip:u354@xxxxxxxxxxxxx:5060>;tag=368b0749
Via: SIP/2.0/UDP 192.168.0.4:5060;branch=z9hG4bK-d87543-7dd0abc84b784a53-1--d87543-;rport
Call-ID: 168292200d150dd4@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs
CSeq: 1 INVITE
User-Agent: RTC/1.3
Content-Length: 0


Eventually, on the remote side, I "Accept" the call. Not completely sure exactly when at
this stage.

resiprocate/dum/DialogUsageManager.cxx:1493 | Looking for dialogSet: 168292200d150dd4@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs-368b0749 in map: resiprocate/dum/DialogUsageManager.cxx:1494 | [758371fd332c54a1@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs-7345b4b3 -> 0x65878b0, 168292200d150dd4@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs-368b0749 -> 0x659b420] resiprocate/dum/DialogUsageManager.cxx:1395 | DialogUsageManager::processResponse: SipResp: 180 tid=7dd0abc84b784a53 cseq=INVITE / 1 from(wire) resiprocate/dum/DialogId.cxx:50 | DialogId::DialogId: 168292200d150dd4@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs-368b0749-64bd007ce1ca4c3a953ba264d9776e99 resiprocate/dum/DialogSet.cxx:665 | findDialog: 168292200d150dd4@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs-368b0749-64bd007ce1ca4c3a953ba264d9776e99 in []


resiprocate/dum/DialogSet.cxx:585 | Cannot create a dialog, no Contact in 180 <---- What is this?

Why can't it create a dialog?

resiprocate/Transport.cxx:209 | incoming from: [ V4 213.167.79.25:5060 UDP received on: Transport: [ V4 0.0.0.0:5060 UDP connectionId=0 ] connectionId=0 ] resiprocate/TransactionState.cxx:1535 | Send to TU: TU: DialogUsageManager size=0

Remote proxy sends back the "200 OK" anyway....

SIP/2.0 200 OK R002180550192370401414752M000A192.168.0.3P5000
To: <sip:u218055@xxxxxxxxxxxxxx>;tag=64bd007ce1ca4c3a953ba264d9776e99
From: <sip:u354@xxxxxxxxxxxxx:5060>;tag=368b0749
Via: SIP/2.0/UDP 192.168.0.4:5060;branch=z9hG4bK-d87543-7dd0abc84b784a53-1--d87543-;rport
Call-ID: 168292200d150dd4@am9obi1kcmFwZXJzLWNvbXB1dGVyLmxvY2Fs
CSeq: 1 INVITE
Content-Type: application/sdp
User-Agent: RTC/1.3
Content-Length: 194

v=0
o=- 0 0 IN IP4 24.180.24.117
s=WhitePhone Mac
c=IN IP4 192.168.0.3
b=CT:1000
t=0 0
m=audio 5000 RTP/AVP 3 101
a=rtpmap:3 GSM/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16

Anyway,  I'm really getting close to getting Invite request working.
Does anyone see why I'm getting this in my logs?  Any recommendations
on what else I can try?   Or anything I left out?

John