Outgoing Call failing - busy

Discussion in '3CX Phone System - General' started by itsimplified3cx, Aug 13, 2014.

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

    Joined:
    Aug 13, 2014
    Messages:
    4
    Likes Received:
    0
    I have a user trying to make a call and after dialling display says busy, here is the call logs:

    13-Aug-2014 10:35:28.680 Leg L:337.1[Extn] is terminated: Cause: BYE from PBX
    13-Aug-2014 10:35:28.645 [CM503020]: Call(C:337): Normal call termination. Call originator: Extn:213. Reason: Busy
    13-Aug-2014 10:35:28.645 L:337.1[Extn] failed to reach Line:10000>>01252******, reason Busy
    13-Aug-2014 10:35:28.645 Call to T:Line:10000>>01252******@[Dev:sip:08450******@sip.voip-unlimited.net:5060] from L:337.1[Extn] failed, cause: Cause: 486 Busy here/INVITE from ***.***.***.***:5060
    13-Aug-2014 10:35:27.777 [CM503025]: Call(C:337): Calling T:Line:10000>>01252******@[Dev:sip:08450******@sip.voip-unlimited.net:5060] for L:337.1[Extn]
    13-Aug-2014 10:35:27.678 [CM503027]: Call(C:337): From: Extn:213 ("********" <sip:213@192.168.200.25:5060>) to T:Line:10000>>01252******@[Dev:sip:08450******@sip.voip-unlimited.net:5060]
    13-Aug-2014 10:35:27.678 [CM503004]: Call(C:337): Route 1: from L:337.1[Extn] to T:Line:10000>>01252******@[Dev:sip:08450******@sip.voip-unlimited.net:5060]
    13-Aug-2014 10:35:27.678 Call(C:337): Call from Extn:213 to 01252****** matches outbound rule 'Rule for ***************'
    13-Aug-2014 10:35:27.677 [CM503001]: Call(C:337): Incoming call from Extn:213 to <sip:01252******@192.168.200.25:5060>
    13-Aug-2014 10:35:19.283 Leg L:336.1[Extn] is terminated: Cause: BYE from PBX
    13-Aug-2014 10:35:19.227 [CM503020]: Call(C:336): Normal call termination. Call originator: Extn:213. Reason: Busy
    13-Aug-2014 10:35:19.227 L:336.1[Extn] failed to reach Line:10000>>01252******, reason Busy
    13-Aug-2014 10:35:19.227 Call to T:Line:10000>>01252******@[Dev:sip:08450******@sip.voip-unlimited.net:5060] from L:336.1[Extn] failed, cause: Cause: 486 Busy here/INVITE from ***.***.***.***:5060
    13-Aug-2014 10:35:18.348 [CM503025]: Call(C:336): Calling T:Line:10000>>01252******@[Dev:sip:08450******@sip.voip-unlimited.net:5060] for L:336.1[Extn]
    13-Aug-2014 10:35:18.255 [CM503027]: Call(C:336): From: Extn:213 ("*** ***" <sip:213@192.168.200.25:5060>) to T:Line:10000>>01252******@[Dev:sip:08450******@sip.voip-unlimited.net:5060]
    13-Aug-2014 10:35:18.255 [CM503004]: Call(C:336): Route 1: from L:336.1[Extn] to T:Line:10000>>01252******@[Dev:sip:08450******@sip.voip-unlimited.net:5060]
    13-Aug-2014 10:35:18.255 Call(C:336): Call from Extn:213 to 01252****** matches outbound rule 'Rule for A*******'
    13-Aug-2014 10:35:18.254 [CM503001]: Call(C:336): Incoming call from Extn:213 to <sip:01252******@192.168.200.25:5060>

    Many Thanks
    Llewellyn
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,061
    Likes Received:
    56
    A few questions:

    Is it only this particular number that when dialed returns this error?
    Did you try dialing the same number using a mobile phone to see if the number can be reached?
    Is there possibly something at issue with how local, national, international calls get formatted and sent?

    As indicated in the logs, whatever the number dialed the response code is indicating that it is busy and therefor unable to accommodate. Usually, a wait of a few minutes and a retry will resolve the issue and failing that a call to the same number from a different technology (mobile or traditional land line) will provide more insight or even a confirmation with a busy ring-back tone.
     
  3. itsimplified3cx

    Joined:
    Aug 13, 2014
    Messages:
    4
    Likes Received:
    0
    Thank you for response, client will monitor and if happens again will try another technology.
     
  4. itsimplified3cx

    Joined:
    Aug 13, 2014
    Messages:
    4
    Likes Received:
    0
    Hi,

    I checked the server event logs and i found the attached jpeg, this does not seem it was isolated to one number:
    Call or registration to xxxx... has failed......

    from the attached jpeg of the log, is there any indication of what might have been causing the issue?
     

    Attached Files:

  5. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,061
    Likes Received:
    56
    Well, from the looks of things the provider is indicating:

    on the call to 02152 that he made an effort to make the call, but the end device is reporting that it is busy and cannot handle. They only waited 10 seconds between calls and had they waited a little longer, they likely would have made it through.

    on the calls to 6666 and 848160 the provider made an effort to handle the call, but the server was temporarily not able to handle the calls. It may have been too busy or in a maintenance mode.

    On the calls to 0001316, the number or destination was not found. This is usually indicative of a bad or misdialed number and where a cell phone or other landline call to the same number will confirm. The second attempt I think was from the 3CX system as it was not able to communicate with the provider and simply timed out.

    You certainly seem to have a variety of phone number lengths 4, 5, 6 and 7. May I ask what country where this is located?
     
  6. itsimplified3cx

    Joined:
    Aug 13, 2014
    Messages:
    4
    Likes Received:
    0
    Hi,

    this is located in the UK, i have deleted the end parts of the numbers except for the 6666 number, the 848160 is a local number, there are rules that pick up if it is a 6 digit number to add the local area code.
     
Thread Status:
Not open for further replies.