International calling issues

Discussion in '3CX Phone System - General' started by Brian Oli, Nov 8, 2017.

Thread Status:
Not open for further replies.
  1. Brian Oli

    Joined:
    Dec 9, 2016
    Messages:
    6
    Likes Received:
    0
    Hello Everyone:

    I am having a problem calling internationally to singapore. I have called other singapore numbers with success. When I call these 2 particular numbers, I get the call can not be completed as dialed. I was wondering if my rule was setup incorrectly. I am simply taking any international calling and sending if over I fiber. Do I need to select the number of digits in the rule?

    Any assistance would be appreciated.

    Below is the call log and the Rule snapshot is attached.

    08-Nov-2017 11:51:00.195 Leg L:5305.1[Extn:225] is terminated: Cause: BYE from PBX
    08-Nov-2017 11:51:00.194 Leg L:5305.2[Line:10000>>011656688xxxx] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.1.199:5060
    08-Nov-2017 11:51:00.194 [CM503020]: Call(C:5305): Normal call termination. Call originator: Extn:225. Reason: Terminated
    08-Nov-2017 11:51:00.194 L:5305.1[Extn:225] failed to reach Line:10000>>011656688xxxx, reason Request Terminated
    08-Nov-2017 11:51:00.194 Call to T:Line:10000>>011656688xxxx@[Dev:sip:7162043xxx@192.168.1.199:5060] from L:5305.1[Extn:225] failed, cause: Cause: 487 Request Terminated/INVITE from 192.168.1.199:5060
    08-Nov-2017 11:51:00.194 [CM503003]: Call(C:5305): Call to <sip:011656688xxxx@192.168.1.199:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.199:5060
    08-Nov-2017 11:51:00.168 Currently active calls - 3: [5301,5304,5305]
    08-Nov-2017 11:50:53.979 [CM505003]: Provider:[TWC Fiber] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [ESBC9378-4B-2.0.13.0-Build8] PBX contact: [sip:7162043xxx@192.168.1.11:5060]
    08-Nov-2017 11:50:52.634 [CM503025]: Call(C:5305): Calling T:Line:10000>>011656688xxxx@[Dev:sip:7162043xxx@192.168.1.199:5060] for L:5305.1[Extn:225]
    08-Nov-2017 11:50:52.618 [CM503027]: Call(C:5305): From: Extn:225 ("Brian Olinski" <sip:225@192.168.1.11:5060>) to T:Line:10000>>011656688xxxx@[Dev:sip:7162043xxx@192.168.1.199:5060]
    08-Nov-2017 11:50:52.618 [CM503004]: Call(C:5305): Route 1: from L:5305.1[Extn:225] to T:Line:10000>>011656688xxxx@[Dev:sip:7162043570@192.168.1.199:5060]
    08-Nov-2017 11:50:52.617 Line limit check: Current # of calls for line Lc:10000(@TWC Fiber[<sip:7162043xxx@192.168.1.199:5060>]) is 2; limit is 7
    08-Nov-2017 11:50:52.617 Call(C:5305): Call from Extn:225 to 011656688xxxxmatches outbound rule 'international'
    08-Nov-2017 11:50:52.617 [CM503001]: Call(C:5305): Incoming call from Extn:225 to <sip:011656688xxxx@192.168.1.11:5060>

    international.JPG
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,750
    Likes Received:
    285
    Would you please post a working log for a call to the same country code.

    All call tests are being made from the same extension? I don't see a rejection message. You don't have a restriction set as to the number of concurrent calls per trunk, do you? How many trunks do you have in the TWC group?
     
    Brian Oli likes this.
  3. Brian Oli

    Joined:
    Dec 9, 2016
    Messages:
    6
    Likes Received:
    0
    Below is the log for a successful cal made to singapore

    08-Nov-2017 13:43:00.839 Leg L:5324.1[Extn:225] is terminated: Cause: BYE from 192.168.1.140:5060
    08-Nov-2017 13:42:55.450 [CM503007]: Call(C:5324): Extn:225 has joined, contact <sip:225@192.168.1.140:5060>
    08-Nov-2017 13:42:55.450 L:5324.2[Line:10000>>011656275xxxx has joined to L:5324.1[Extn:225]
    08-Nov-2017 13:42:47.188 [CM503025]: Call(C:5324): Calling T:Line:10000>>01165627xxxx@[Dev:sip:7162043570@192.168.1.199:5060] for L:5324.1[Extn:225]
    08-Nov-2017 13:42:47.137 [CM503027]: Call(C:5324): From: Extn:225 ("Brian " <sip:225@192.168.1.11:5060>) to T:Line:10000>>011656275xxxx@[Dev:sip:7162043570@192.168.1.199:5060]
    08-Nov-2017 13:42:47.137 [CM503004]: Call(C:5324): Route 1: from L:5324.1[Extn:225] to T:Line:10000>>011656275xxxx@[Dev:sip:7162043570@192.168.1.199:5060]
    08-Nov-2017 13:42:47.137 Call(C:5324): Call from Extn:225 to 011656275xxxx matches outbound rule 'international'


    Test calls were made from different extensions. We only have one trunk group.


    Thanks for your assistance.
     
  4. Brian Oli

    Joined:
    Dec 9, 2016
    Messages:
    6
    Likes Received:
    0

    Below is the log for a successful cal made to singapore

    08-Nov-2017 13:43:00.839 Leg L:5324.1[Extn:225] is terminated: Cause: BYE from 192.168.1.140:5060
    08-Nov-2017 13:42:55.450 [CM503007]: Call(C:5324): Extn:225 has joined, contact <sip:225@192.168.1.140:5060>
    08-Nov-2017 13:42:55.450 L:5324.2[Line:10000>>011656275xxxx] has joined to L:5324.1[Extn:225]
    08-Nov-2017 13:42:47.188 [CM503025]: Call(C:5324): Calling T:Line:10000>>011656275xxxx@[Dev:sip:716204xxxx@192.168.1.199:5060] for L:5324.1[Extn:225]
    08-Nov-2017 13:42:47.137 [CM503027]: Call(C:5324): From: Extn:225 ("Brian " <sip:225@192.168.1.11:5060>) to T:Line:10000>>011656275xxxx@[Dev:sip:7162043570@192.168.1.199:5060]
    08-Nov-2017 13:42:47.137 [CM503004]: Call(C:5324): Route 1: from L:5324.1[Extn:225] to T:Line:10000>>011656275xxxx@[Dev:sip:7162043xxx@192.168.1.199:5060]
    08-Nov-2017 13:42:47.137 Call(C:5324): Call from Extn:225 to 011656275xxxx matches outbound rule 'international'


    Test calls were made from different extensions. We only have one trunk group.


    Thanks for your assistance.
     
  5. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    You need to check with TWC (Spectrum). It is their side that terminated the request with a 487. A wireshark might show more as I am uncertain as to the log mode and how a complete capture of the messaging translates into the 3CX log.

    "Request Terminated/INVITE from 192.168.1.199:5060"
    The .199 is assumed to be their eSBC.

    As the numbers used to show a bad and good call, I assume it possible that it may have something to do with the number itself (non-existent, out of service, etc.) and you are ultimately getting back a message that may be an interpretation (or not) of how the error made its way back from where ever the issue was seen.
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,750
    Likes Received:
    285
    The two logs you posted appear to one in the same.
    Have you successfully called the number from another line? Could the number you are calling, be a mobile number, billed at a rate higher than you have authorized?
     
Thread Status:
Not open for further replies.