call hangup problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A client makes up a call to a server and the call is established.
But the server can't hangup the call.

DEBUG: 15:26:08.392   pjsua_core.c        pjsua  RX 868 bytes Request msg
INVITE/cseq=1 (rdata0FDADAAC) from UDP 118.36.168.14:5060:
INVITE sip:1001 at 115.68.7.18;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.0.37;branch=z9hG4bKac242814607;rport
From: "9001001" <sip:9001001@192.168.0.37>;tag=1c242808723
To: <sip:1001 at 115.68.7.18;user=phone>
CSeq: 1 INVITE
Contact: <sip:9001001 at 192.168.0.37:5060>
DEBUG: 15:26:08.397   pjsua_core.c      cti3464  TX 770 bytes Response msg
200/INVITE/cseq=1 (tdta1061FF00) to UDP 118.36.168.14:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.0.37;rport=5060;received=118.36.168.14;branch=z9hG4bKac242814607
From: "9001001" <sip:9001001@192.168.0.37>;tag=1c242808723
To: <sip:1001 at 115.68.7.18;user=phone>;tag=be18a80ffbf144d289b3a08f6fbe9909
CSeq: 1 INVITE
Contact: <sip:115.68.7.18:5093>
The BYTE message can't be delivered to the caller.

TRACE: 15:26:08.450  sip_resolve.c      cti3464  Target '192.168.0.37:5060'
type=Unspecified resolved to '192.168.0.37:5060' type=UDP (UDP transport)
DEBUG: 15:26:08.451   pjsua_core.c      cti3464  TX 397 bytes Request msg
BYE/cseq=26500 (tdta1061FF00) to UDP 192.168.0.37:5060:
BYE sip:9001001 at 192.168.0.37:5060 SIP/2.0
Via: SIP/2.0/UDP 115.68.7.18:5093
;rport;branch=z9hG4bKPjf2f60035eaab4e5d90233e33e7354703
From: <sip:1001@115.68.7.18;user=phone>;tag=be18a80ffbf144d289b3a08f6fbe9909
To: "9001001" <sip:9001001 at 192.168.0.37>;tag=1c242808723
CSeq: 26500 BYE
If the INVITE message is as following, the server can hangup the call.

DEBUG: 15:14:17.163   pjsua_core.c        pjsua  RX 803 bytes Request msg
INVITE/cseq=1 (rdata101D4974) from UDP 118.36.168.14:43084:
INVITE sip:1001 at 115.68.7.18:5093 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.2:43084
;branch=z9hG4bK-d8754z-fa129c7c170cee05-1---d8754z-;rport
Contact: <sip:9001001 at 118.36.168.14:43084>
To: "1001"<sip:1001 at 115.68.7.18:5093>
From: <sip:9001001@115.68.7.18:5093>;tag=a166441e
CSeq: 1 INVITE
User-Agent: X-Lite release 1104o stamp 56125
TRACE: 15:14:17.331  sip_resolve.c      cti3280  Target '118.36.168.14:43084'
type=Unspecified resolved to '118.36.168.14:43084' type=UDP (UDP transport)
DEBUG: 15:14:17.331   pjsua_core.c      cti3280  TX 393 bytes Request msg
BYE/cseq=26500 (tdta1082BFB8) to UDP 118.36.168.14:43084:
BYE sip:9001001 at 118.36.168.14:43084 SIP/2.0
Via: SIP/2.0/UDP 115.68.7.18:5093
;rport;branch=z9hG4bKPj7738145c9ca24b9e906a30940a4ef2ec
From: "1001" <sip:1001@115.68.7.18>;tag=169c50cef8b842b48f5ae9f218f4668a
To: <sip:9001001 at 115.68.7.18>;tag=a166441e
CSeq: 26500 BYE
The major difference between the two cases is the callers' Contact
addresses.
In the first case, the Contact address is local ip address, and in the
second, public ip address.

How to solve this problem?

regards.
seo, hangal.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20110510/bc76ea05/attachment-0001.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux