Sidebar Sidebar
  • V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Line does not disconnect

Status
Not open for further replies.

jlebeau

Joined
May 22, 2007
Messages
32
Reaction score
0
I am running 3CX with a Grandstream GXW4108 gateway and GXP2000 phones. The issue I am having is that when I make a call to someone outside of the network over the PSTN lines, if they hang up first, my phone never disconnects the line and eventually I get the operator message saying "If you would like to make a call, please hang up and try again."

I have contacted Grandstream tech support and they are questioning the SIP signalling coming from the 3CX system. I have SYSLOG captures from the gateway and phone, and the red flag I am seeing is that when the PSTN side hangs up, the GXP2000 shows that it receives a SIP message and then has a parse error. Here are the lines from the syslog server:

2007-07-19 11:55:05 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIPReceive(4, Account1):
2007-07-19 11:55:05 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Received SIP message: parse error
2007-07-19 11:55:24 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Send SIP message: BYE To 192.168.3.207:5060, sip_handle: 0x004B809A

The last line is the BYE message it gets when I hang up the GXP2000 after receiving the operator message.

Any thoughts or help?
 
jlebeau said:
I am running 3CX with a Grandstream GXW4108 gateway and GXP2000 phones. The issue I am having is that when I make a call to someone outside of the network over the PSTN lines, if they hang up first, my phone never disconnects the line and eventually I get the operator message saying "If you would like to make a call, please hang up and try again."

I have contacted Grandstream tech support and they are questioning the SIP signalling coming from the 3CX system. I have SYSLOG captures from the gateway and phone, and the red flag I am seeing is that when the PSTN side hangs up, the GXP2000 shows that it receives a SIP message and then has a parse error. Here are the lines from the syslog server:

2007-07-19 11:55:05 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIPReceive(4, Account1):
2007-07-19 11:55:05 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Received SIP message: parse error
2007-07-19 11:55:24 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Send SIP message: BYE To 192.168.3.207:5060, sip_handle: 0x004B809A

The last line is the BYE message it gets when I hang up the GXP2000 after receiving the operator message.

Any thoughts or help?
Click to expand...

Just show content of all SIP messages, then it will be a conversation :)

Thanks,
Stepan
 
Here is the full syslog capture from the GXP2000 during the call where the external phone hangs up first:

2007-07-19 11:54:34 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Send SIP message: INVITE To 192.168.3.207:5060, sip_handle: 0x004B809A
2007-07-19 11:54:34 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] sip_len: 907, sip_handle: 0x004B809A, INVITE sip:8555****@192.168.3.207 SIP/2.0 Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK3364365d40122e5a From: "John Doe" <sip:[email protected]>;tag=3b234a87952ceac5 To: <sip:8555****@192.168.3.207> Contact: <sip:[email protected]:5060;transport=udp> Supported: replaces, timer, path Call-ID: [email protected] CSeq: 60823 INVITE User-Agent: Grandstream GXP2000 1.1.2.23 Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Type: application/sdp Content-Length: 348 v=0 o=113 8000 8000 IN IP4 192.168.3.37 s=SIP Call c=IN IP4 192.168.3.37 t=0 0 m=audio 5004 RTP/AVP 0 8 4 18 2 99 9 3 a=sendrecv a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:4 G723/8000 a=rtpmap:18 G729/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:99 iLBC/8000 a=fmtp:99 mode=20 a=rtpmap:9 G722/16000 a=rtpmap:3 GSM/8000 a=ptime:20
2007-07-19 11:54:34 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIPReceive(451, Account1): SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK3364365d40122e5a Proxy-Authenticate: Digest nonce="12829337674:7f86558a25b395fb53c256aba12abe2c",algorithm=MD5,realm="3CXPhoneSystem" To: <sip:8555****@192.168.3.207>;tag=4c6bdb31 From: "John Doe"<sip:[email protected]>;tag=3b234a87952ceac5 Call-ID: [email protected] CSeq: 60823 INVITE User-Agent: 3CXPhoneSystem Content-Length: 0
2007-07-19 11:54:34 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Received SIP message: 407
2007-07-19 11:54:34 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIP dialog matched to channel 0
2007-07-19 11:54:34 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Send SIP message: ACK To 192.168.3.207:5060, sip_handle: 0x004B809A
2007-07-19 11:54:34 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] sip_len: 520, sip_handle: 0x004B809A, ACK sip:8555****@192.168.3.207 SIP/2.0 Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK3364365d40122e5a From: "John Doe" <sip:[email protected]>;tag=3b234a87952ceac5 To: <sip:8555****@192.168.3.207>;tag=4c6bdb31 Contact: <sip:[email protected]:5060;transport=udp> Supported: path Call-ID: [email protected] CSeq: 60823 ACK User-Agent: Grandstream GXP2000 1.1.2.23 Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Length: 0
2007-07-19 11:54:34 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Send SIP message: INVITE To 192.168.3.207:5060, sip_handle: 0x004B809A
2007-07-19 11:54:34 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] sip_len: 1123, sip_handle: 0x004B809A, INVITE sip:8555****@192.168.3.207 SIP/2.0 Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK77b875dbf260010e From: "John Doe" <sip:[email protected]>;tag=3b234a87952ceac5 To: <sip:8555****@192.168.3.207> Contact: <sip:[email protected]:5060;transport=udp> Supported: replaces, timer, path Proxy-Authorization: Digest username="113", realm="3CXPhoneSystem", algorithm=MD5, uri="sip:8555****@192.168.3.207", nonce="12829337674:7f86558a25b395fb53c256aba12abe2c", response="111a486be02556cc40e2c6f30547105a" Call-ID: [email protected] CSeq: 60824 INVITE User-Agent: Grandstream GXP2000 1.1.2.23 Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Type: application/sdp Content-Length: 348 v=0 o=113 8000 8001 IN IP4 192.168.3.37 s=SIP Call c=IN IP4 192.168.3.37 t=0 0 m=audio 5004 RTP/AVP 0 8 4 18 2 99 9 3 a=sendrecv a=rtpmap:0 PCMU/80...
2007-07-19 11:54:35 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIPReceive(310, Account1): SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK77b875dbf260010e To: <sip:8555****@192.168.3.207>;tag=34571476 From: "John Doe"<sip:[email protected]>;tag=3b234a87952ceac5 Call-ID: [email protected] CSeq: 60824 INVITE User-Agent: 3CXPhoneSystem Content-Length: 0
2007-07-19 11:54:35 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Received SIP message: 100
2007-07-19 11:54:35 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIP dialog matched to channel 0
2007-07-19 11:54:37 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIPReceive(353, Account1): SIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK77b875dbf260010e Contact: <sip:[email protected]:5060> To: <sip:8555****@192.168.3.207>;tag=34571476 From: "John Doe"<sip:[email protected]>;tag=3b234a87952ceac5 Call-ID: [email protected] CSeq: 60824 INVITE User-Agent: 3CXPhoneSystem Content-Length: 0
2007-07-19 11:54:37 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Received SIP message: 180
2007-07-19 11:54:37 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIP dialog matched to channel 0
2007-07-19 11:54:37 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIPReceive(758, Account1): SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK77b875dbf260010e Contact: <sip:[email protected]:5060> To: <sip:8555****@192.168.3.207>;tag=34571476 From: "John Doe"<sip:[email protected]>;tag=3b234a87952ceac5 Call-ID: [email protected] CSeq: 60824 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO Content-Type: application/sdp User-Agent: 3CXPhoneSystem Content-Length: 293 v=0 o=3cxPS 12829337674959 12829337674961 IN IP4 192.168.3.207 s=3cxPS Audio call c=IN IP4 192.168.3.207 t=0 0 m=audio 7156 RTP/AVP 0 8 99 3 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:99 iLBC/8000 a=fmtp:99 mode=20 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000
2007-07-19 11:54:37 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Received SIP message: 200
2007-07-19 11:54:37 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIP dialog matched to channel 0
2007-07-19 11:54:37 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Session Info: Payload-Type=0, Frames/Packet=2, DTMF=101
2007-07-19 11:54:37 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Send SIP message: ACK To 192.168.3.207:5060, sip_handle: 0x004B809A
2007-07-19 11:54:37 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] sip_len: 739, sip_handle: 0x004B809A, ACK sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK24f584a27ab9659d From: "John Doe" <sip:[email protected]>;tag=3b234a87952ceac5 To: <sip:8555****@192.168.3.207>;tag=34571476 Contact: <sip:[email protected]:5060;transport=udp> Supported: path Proxy-Authorization: Digest username="113", realm="3CXPhoneSystem", algorithm=MD5, uri="sip:8555****@192.168.3.207", nonce="12829337674:7f86558a25b395fb53c256aba12abe2c", response="111a486be02556cc40e2c6f30547105a" Call-ID: [email protected] CSeq: 60824 ACK User-Agent: Grandstream GXP2000 1.1.2.23 Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Length: 0
2007-07-19 11:54:37 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] RTP session starts. Channel: 0 Local RTP port: 5004 Remote RTP endpoint: 192.168.3.207:7156
2007-07-19 11:55:05 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIPReceive(4, Account1):
2007-07-19 11:55:05 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Received SIP message: parse error
2007-07-19 11:55:24 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Send SIP message: BYE To 192.168.3.207:5060, sip_handle: 0x004B809A
2007-07-19 11:55:24 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] sip_len: 690, sip_handle: 0x004B809A, BYE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK5df6bc07b7d69109 From: "John Doe" <sip:[email protected]>;tag=3b234a87952ceac5 To: <sip:8555****@192.168.3.207>;tag=34571476 Supported: path Proxy-Authorization: Digest username="113", realm="3CXPhoneSystem", algorithm=MD5, uri="sip:[email protected]:5060", nonce="12829337674:7f86558a25b395fb53c256aba12abe2c", response="00bd58c079cd7284bbe73dbb0e36b49a" Call-ID: [email protected] CSeq: 60825 BYE User-Agent: Grandstream GXP2000 1.1.2.23 Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE Content-Length: 0
2007-07-19 11:55:24 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIPReceive(345, Account1): SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.3.37:5060;branch=z9hG4bK5df6bc07b7d69109 Contact: <sip:[email protected]:5060> To: <sip:8555****@192.168.3.207>;tag=34571476 From: "John Doe"<sip:[email protected]>;tag=3b234a87952ceac5 Call-ID: [email protected] CSeq: 60825 BYE User-Agent: 3CXPhoneSystem Content-Length: 0
2007-07-19 11:55:24 User.Info 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] Received SIP message: 200
2007-07-19 11:55:24 User.Debug 192.168.3.37 GS_LOG: [00:0B:82:0D:F0:4E][000][FF71][01010217] SIP dialog matched to channel 0
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Members Online Now

Total: 518 (members: 24, guests: 494)

Forum statistics

Threads
141,917
Messages
751,137
Members
145,338
Latest member
driscolls.it
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Verify your Email

Check your inbox!

We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).

Upon verification you will be directed to the 3CX setup wizard.

Top Bottom
Back