Portech 370 no outbound calls

Discussion in '3CX Phone System - General' started by efthimis, Dec 18, 2014.

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

    Joined:
    Jun 13, 2014
    Messages:
    40
    Likes Received:
    2
    Hello, i have setup a Portech 370 GSM Gateway and i have problem with outgoing calls. The inbound calls works normally but when i call outside i get this: ( i have updated the firmware to Tue Apr 7 17:27:09 2009.) What is the problem?

    Leg L:518.1[Extn] is terminated: Cause: BYE from PBX
    [CM503020]: Call(C:518): Normal call termination. Call originator: Extn:105. Reason: No answer
    Leg L:518.2[Line:10009>>xxxxxxxxxxxx] is terminated: Cause: 408 Request Timeout/INVITE from local
    L:518.1[Extn] failed to reach Line:10009>>xxxxxxxxx, reason No Answer
    Call to T:Line:10009>>xxxxxxxxx@[Dev:sip:10009@192.168.x.x:5060] from L:518.1[Extn] failed, cause: Cause: 408 Request Timeout/INVITE from local
    [CM503003]: Call(C:518): Call to <sip:xxxxxxxx@102.168.x.x:5060> has failed; Cause: 408 Request Timeout/INVITE from local
    Currently active calls - 1: [518]
    [CM503025]: Call(C:518): Calling T:Line:10009>>xxxxxxxxx@[Dev:sip:10009@192.168.x.x:5060] for L:518.1[Extn]
    [CM503027]: Call(C:518): From: Extn:105 ("someone" <sip:105@192.168.x.x:5060>) to T:Line:10009>>xxxxxxxxx@[Dev:sip:10009@192.168.x.x:5060]
    [CM503004]: Call(C:518): Route 1: from L:518.1[Extn] to T:Line:10009>>xxxxxxxx@[Dev:sip:10009@192.168.x.x:5060]
    Line limit check: Current # of calls for line Lc:10009(@Mobile Gateway[<sip:10009@192.168.x.x:5060>]) is 0; limit is 2
    Call(C:518): Call from Extn:105 to xxxxxxxxxx matches outbound rule 'Mobile GW'
    [CM503001]: Call(C:518): Incoming call from Extn:105 to <sip:xxxxxxxxx@192.168.x.x:5060>
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,757
    Likes Received:
    286
    I suspect that in the 3CX trunk settings, for this gateway, you have a typo in the gateways IP address and put in 102 instead of 192.
     
  3. efthimis

    Joined:
    Jun 13, 2014
    Messages:
    40
    Likes Received:
    2
    Hello,

    It is just a paste typo... :oops:
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,757
    Likes Received:
    286
    If the outbound calls are being directed to the correct IP (and port) set in the device, then, I would hazard a guess that there is some setting in the gateway that is not correct (one stage dialling?). If the gateway has the ability to log errors to a syslog server, then I would make use of that option. You would have more information as to why the gateway is not responding.
     
Thread Status:
Not open for further replies.