Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Calls do not hang up

Discussion in '3CX Phone System - General' started by ChameleonPaul, Jan 11, 2010.

Thread Status:
Not open for further replies.
  1. ChameleonPaul

    Joined:
    Jan 11, 2010
    Messages:
    11
    Likes Received:
    0
    Hi.

    Yes - I am a 3cx noob...

    Have just downloaded and Installed the free 3cx Voip PABX. Is early days... Playing with config / setup...

    Our ISP is Exetel (australia http://www.exetel.com.au) – not listed, supported or tested so if have any advice on setup re exetel – much appreciated.

    All seems fine so far – can make outbound calls. But they won't hang up. 3cx soft phone or x-litesoft phone, hang up – show hung up. Check status in 3cx server manager – shows call terminated – but it isn't – is still connected... Need to resolve this.

    Another – 3cx assistant times out in loggin attempt to server.

    Plan is to have inbound calls to 4-5 softphones(extensions), and later fax phone and pstn via ata.

    Any tips suggestions gr8ly app.
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,095
    Likes Received:
    327
    You might want to post a 3CX log of an outbound call from a point during the conversation to a point after you have hung up but the trunk is still held up. It could shed some light on why the call isn't dropping.
     
  3. ChameleonPaul

    Joined:
    Jan 11, 2010
    Messages:
    11
    Likes Received:
    0
    Hi.

    Thanks for you reply. Sorry about the late reply - got tasked on other duties for a while.

    Behaviour seems intermittent, but frequent enough to be a concern. Log below shows behaviour when a call is made to a Cell phone (mine on desk next to me). Mid call attempt, the call is terminated our end via 3cx soft phone. Call does not hang up - cell continues ringing. Attempt call again - get diverted to voicemail by cell as is still engaged with previous connection. Same for follow ups - repeated trials

    In log below, call did terminate after a time. However at other times the call did not terminate.

    I have tested it and the call has hung up on terminate via soft phone. but is less frequent than not hang up.

    Any clues?

    Log follows.
    11:42:59.156 [CM503008]: Call(94): Call is terminated
    11:42:58.156 [CM503007]: Call(94): Device joined: sip:0280072941@sip1.exetel.com.au:5060
    11:42:58.156 [CM503007]: Call(94): Device joined: sip:10@192.168.1.123:62778;rinstance=a96a091c1600a062
    11:42:54.749 [CM505003]: Provider:[Exetel] Device info: Device Identified: [Man: Counterpath;Mod: Bria;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Bria release 2.5.4 stamp 53956] PBX contact: [sip:0280072941@220.233.46.199:5060]
    11:42:54.749 [CM503002]: Call(94): Alerting sip:0280072941@sip1.exetel.com.au:5060
    11:42:50.749 [CM503025]: Call(94): Calling VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:42:50.328 [CM503004]: Call(94): Route 1: VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:42:50.328 [CM503010]: Making route(s) to <sip:0418315608@192.168.1.100:5060>
    11:42:50.328 [CM505001]: Ext.10: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CXVoipPhone;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9878.0] PBX contact: [sip:10@192.168.1.100:5060]
    11:42:50.328 [CM503001]: Call(94): Incoming call from Ext.10 to <sip:0418315608@192.168.1.100:5060>
    11:42:38.281 [MS105000] C:93.1: No RTP packets were received:remoteAddr=192.168.1.123:40010,extAddr=0.0.0.0:0,localAddr=192.168.1.100:7258
    11:42:37.406 [CM503008]: Call(93): Call is terminated
    11:42:35.296 [CM505003]: Provider:[Exetel] Device info: Device Identified: [Man: Counterpath;Mod: Bria;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Bria release 2.5.4 stamp 53956] PBX contact: [sip:0280072941@220.233.46.199:5060]
    11:42:35.296 [CM503002]: Call(93): Alerting sip:0280072941@sip1.exetel.com.au:5060
    11:42:33.546 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 94.228.101.70:3478 over Transport 192.168.1.100:5060
    11:42:30.734 [CM503025]: Call(93): Calling VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:42:30.312 [CM503004]: Call(93): Route 1: VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:42:30.312 [CM503010]: Making route(s) to <sip:0418315608@192.168.1.100:5060>
    11:42:30.312 [CM505001]: Ext.10: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CXVoipPhone;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9878.0] PBX contact: [sip:10@192.168.1.100:5060]
    11:42:30.312 [CM503001]: Call(93): Incoming call from Ext.10 to <sip:0418315608@192.168.1.100:5060>
    11:42:23.093 [CM503008]: Call(92): Call is terminated
    11:42:20.702 [CM503007]: Call(92): Device joined: sip:0280072941@sip1.exetel.com.au:5060
    11:42:20.702 [CM503007]: Call(92): Device joined: sip:10@192.168.1.123:62778;rinstance=a96a091c1600a062
    11:42:18.843 [CM505003]: Provider:[Exetel] Device info: Device Identified: [Man: Counterpath;Mod: Bria;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Bria release 2.5.4 stamp 53956] PBX contact: [sip:0280072941@220.233.46.199:5060]
    11:42:18.843 [CM503002]: Call(92): Alerting sip:0280072941@sip1.exetel.com.au:5060
    11:42:15.030 [CM503025]: Call(92): Calling VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:42:14.609 [CM503004]: Call(92): Route 1: VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:42:14.609 [CM503010]: Making route(s) to <sip:0418315608@192.168.1.100:5060>
    11:42:14.609 [CM505001]: Ext.10: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CXVoipPhone;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9878.0] PBX contact: [sip:10@192.168.1.100:5060]
    11:42:14.609 [CM503001]: Call(92): Incoming call from Ext.10 to <sip:0418315608@192.168.1.100:5060>
    11:42:06.405 [CM503008]: Call(91): Call is terminated
    11:42:03.702 [CM503007]: Call(91): Device joined: sip:0280072941@sip1.exetel.com.au:5060
    11:42:03.702 [CM503007]: Call(91): Device joined: sip:10@192.168.1.123:62778;rinstance=a96a091c1600a062
    11:42:01.890 [CM505003]: Provider:[Exetel] Device info: Device Identified: [Man: Counterpath;Mod: Bria;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Bria release 2.5.4 stamp 53956] PBX contact: [sip:0280072941@220.233.46.199:5060]
    11:42:01.890 [CM503002]: Call(91): Alerting sip:0280072941@sip1.exetel.com.au:5060
    11:41:58.187 [CM503025]: Call(91): Calling VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:41:57.765 [CM503004]: Call(91): Route 1: VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:41:57.765 [CM503010]: Making route(s) to <sip:0418315608@192.168.1.100:5060>
    11:41:57.765 [CM505001]: Ext.10: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CXVoipPhone;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9878.0] PBX contact: [sip:10@192.168.1.100:5060]
    11:41:57.765 [CM503001]: Call(91): Incoming call from Ext.10 to <sip:0418315608@192.168.1.100:5060>
    11:41:48.937 [MS105000] C:90.1: No RTP packets were received:remoteAddr=192.168.1.123:40004,extAddr=0.0.0.0:0,localAddr=192.168.1.100:7252
    11:41:47.952 [CM503008]: Call(90): Call is terminated
    11:41:46.046 [CM505003]: Provider:[Exetel] Device info: Device Identified: [Man: Counterpath;Mod: Bria;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Bria release 2.5.4 stamp 53956] PBX contact: [sip:0280072941@220.233.46.199:5060]
    11:41:46.046 [CM503002]: Call(90): Alerting sip:0280072941@sip1.exetel.com.au:5060
    11:41:40.093 [CM503025]: Call(90): Calling VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:41:39.671 [CM503004]: Call(90): Route 1: VoIPline:0418315608@(Ln.10000@Exetel)@[Dev:sip:0280072941@sip1.exetel.com.au:5060]
    11:41:39.671 [CM503010]: Making route(s) to <sip:0418315608@192.168.1.100:5060>
    11:41:39.671 [CM505001]: Ext.10: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CXVoipPhone;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9878.0] PBX contact: [sip:10@192.168.1.100:5060]
    11:41:39.671 [CM503001]: Call(90): Incoming call from Ext.10 to <sip:0418315608@192.168.1.100:5060>
    11:41:31.811 [MS105000] C:89.1: No RTP packets were received:remoteAddr=192.168.1.123:40002,extAddr=0.0.0.0:0,localAddr=192.168.1.100:7250
    11:41:31.561 [CM503008]: Call(89): Call is terminated
     
  4. ChameleonPaul

    Joined:
    Jan 11, 2010
    Messages:
    11
    Likes Received:
    0
    Further Info.

    I tested with an x-lite soft phone via other voip did account to same cell, same voip provider, independent of the 3CX gateway. In all cases calls terminated when initiated from softphone.

    Further - direct call via x-lite makes connection/ringing almost instantly. Call via 3cx soft phone via gateway and there is significant lag/time taken to establish connection/ringing. [correction: this may be perceived - not actual. 3cx gives dial tone/ringing tone immediately and can hear when connection takes place as second overlay ringing tone occurs. With the x-lite there is slience until connection is made and then only 1 ringing tone is heard].

    So problem appears to be termination via the 3CX voip gateway and/or config - setup.

    Any clues / advice?
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,095
    Likes Received:
    327
    The No RTP packets received usually indicates that some of your ports aren't opened or a firewall could be causing an issue. It's probably NOT a good thing in any case.

    In the 3CX softphone you can change the option to suppress the "false" British style ringback tone, it can be misleading but some people like to have a RB tone immediately after they dial.

    What happens if you hang up AFTER the called party has answered? Does the call drop immediately then? Have you tried calls to other numbers besides your mobile? Is there a two way voice path? What about calls to a land line where you hang up and the called party is still ringing?

    There have been posts involving some VoIP providers not sending the expected (proper) messages and this could be the case. You may have to "Wireshark" the LAN connection to show more detail about what SIP messages are and aren't being passed between 3CX and your VoIP provider.
     
  6. ChameleonPaul

    Joined:
    Jan 11, 2010
    Messages:
    11
    Likes Received:
    0
    Hi.

    Thanks for your reply.

    I'll investigate the ports on the server. I tried the firewall checker... I do not have rights to that server (stop services etc)- will need to arrange rights to proceed.

    Re the suppress false british style playback tone - where do I find this option? - looking but not found yet...

    Re the calls and testing - it did seem to only occur if the call was not answered and we terminated at our end and then re-tried. I tested to another voip number (different provider) with same result. On pick up there is a 2 way voice path - we can make calls etc, it is only the hang up issue... I'll try to arrange further tests to fixed pots landline number and compare no answer vs pick up.

    If we go down the track of wireshark - what packet (proper message) would I be looking for?

    FYI: appears to be very little on 3cx in our voip providers forums... (Exetel).

    Cheers,

    Paul
    PS - I love this product and can see huge potential for it - so am keen to 'get in to it' ...
     
  7. ChameleonPaul

    Joined:
    Jan 11, 2010
    Messages:
    11
    Likes Received:
    0
    Hi.

    Further info

    Got rights to server and did a firewall check - failed..

    Firewall Check Result:
    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved. <09:39:30>: Phase 1, checking servers connection, please wait... <09:39:30>: Stun Checker service is reachable. Phase 1 check passed. <09:39:30>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait... <09:39:40>: UDP SIP Port is set to 5060. NO RESPONSE received. Phase 2a check FAILED. Application exit code is -2

    We do not have firewall on server. Firewall is on router. Ports are open on the router:
    Port Forwarding:
    VOIP - 3CX
    ALL UDP 9000 - 9010 192.168.1.100 9000 - 9010

    VOIP - 3CX
    ALL TCP/UDP 5060 192.168.1.100 5060

    VOIP - 3CX
    ALL TCP/UDP 5090 192.168.1.100 5090
     
  8. ChameleonPaul

    Joined:
    Jan 11, 2010
    Messages:
    11
    Likes Received:
    0
    Hi. One more bit of information:

    DTMF tones do not appear to be OK. Call a service with digital operator, press tones are ignored/fail particularly #... Any clues (am also looking through the forums).
     
  9. ChameleonPaul

    Joined:
    Jan 11, 2010
    Messages:
    11
    Likes Received:
    0
    Hi.

    Just trialled x-lite softphone (at defaults) on 3cx pbx... Guess what - no issues.

    Call terminated as expected;
    No false British tone;
    Appeared to connect quicly..

    (So issue is with 3cx soft phone client??)

    Have not tested with 'press 1 for...' services yet.
     
  10. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,527
    Likes Received:
    71
    http://www.3cx.com/forums/3cx-soft-phone-client-issues-13772.html
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.