Cannot make outbound call from extension.

Discussion in '3CX Phone System - General' started by MB1, Dec 22, 2011.

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

    MB1

    Joined:
    Nov 2, 2007
    Messages:
    39
    Likes Received:
    0
    Hi All,

    I am trying to make an external call from an iPhone using the 3CX softphone (Version 1.1.4) on the same LAN as my 3CX system. Each time I try to make an external call my VOIP provider appears to block the call. I am able to make calls from another 3CX extension which is registered to my gateway (FXS) port and ultimately routes via 3CX to the same VOIP provider.

    Any ideas?

    Thanks.

    12:36:39.463 [CM503020]: Normal call termination. Reason: Forbidden
    12:36:39.463 [CM503016]: Call(3): Attempt to reach <sip:01293xxxxxx@192.168.30.31:5060> failed. Reason: Forbidden
    12:36:39.447 [CM503003]: Call(3): Call to sip:01293xxxxxx@registry.tgsa.co.uk:5060 has failed; Cause: 603 Declined; from IP:217.33.6.254:5060
    12:36:39.025 [CM503025]: Call(3): Calling VoIPline:01293xxxxxx@(Ln.10000@Call UK)@[Dev:sip:44208002xxxx@registry.tgsa.co.uk:5060]
    12:36:39.025 [MS210002] C:3.2:Offer provided. Connection(transcoding mode): 194.158.81.95:9004(9005)
    12:36:38.619 [CM503004]: Call(3): Route 1: VoIPline:01293xxxxxx@(Ln.10000@Call UK)@[Dev:sip:44208002xxxx@registry.tgsa.co.uk:5060]
    12:36:38.431 [CM503010]: Making route(s) to <sip:01293xxxxxx@192.168.30.31:5060>
    12:36:38.431 [MS210000] C:3.1:Offer received. RTP connection: 192.168.30.5:4000(4001)
    12:36:38.431 Remote SDP is set for legC:3.1
    12:36:38.431 [CM505001]: Ext.15: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for iPhone 1.1.4] PBX contact: [sip:15@192.168.30.31:5060]
    12:36:38.369 [CM503001]: Call(3): Incoming call from Ext.15 to <sip:01293xxxxxx@192.168.30.31:5060>
    12:36:36.072 [CM500002]: Info on incoming INVITE:
    INVITE sip:01293xxxxxx@192.168.30.31:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.30.5:57900;rport=57900;branch=z9hG4bKPj0vawX5lbI8vN52yAXo-GDpUC4XX21lI.
    Max-Forwards: 70
    Contact: "Marcus Barnard"<sip:15@192.168.30.5:57900;ob>
    To: <sip:01293xxxxxx@192.168.30.31:5060>
    From: "MB"<sip:15@192.168.30.31:5060>;tag=UmaD4VI3gI9BZzuyXTLAXNlfF.9YJGYa
    Call-ID: V2BfTcO6kwfs8n0DeeD-76azTKm9YSG3
    CSeq: 27328 INVITE
    Session-Expires: 1800
    Min-SE: 90
    Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
    Proxy-Authorization: Digest username="15",realm="3CXPhoneSystem",nonce="414d535c0503b55303:0422127ecd8a06c3d9f4f911cfad576e",uri="sip:01293xxxxxx@192.168.30.31:5060",response="beb2a7d904e96818084c6fcdbea92d65",algorithm=MD5
    Supported: replaces, 100rel, timer, norefersub
    User-Agent: 3CXPhone for iPhone 1.1.4
    Content-Length: 0
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,594
    Likes Received:
    255
    Your provider is refusing the number as dialled.
    Compare these log lines, in the failed call, to the same lines in a working call, any difference(s)?
     
  3. MB1

    MB1

    Joined:
    Nov 2, 2007
    Messages:
    39
    Likes Received:
    0
    Hi Leejor, Thanks for the speedy reply.

    Here is an identical call made from the other extension that is registered to the gateway. I can't see a huge difference between the two logs.


    13:09:58.229 [MS210003] C:4.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.30.xx:7006(7007)
    13:09:58.229 [MS210001] C:4.2:Answer received. RTP connection[unsecure]: 80.95.48.11:12076(12077)
    13:09:58.229 Remote SDP is set for legC:4.2
    13:09:58.229 [CM505003]: Provider:[Call UK] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [processor2] PBX contact: [sip:44208002xxxx@194.158.81.95:5060]
    13:09:58.229 [CM503002]: Call(4): Alerting sip:44208002xxxx@registry.tgsa.co.uk:5060
    13:09:57.854 [CM503025]: Call(4): Calling VoIPline:01293xxxxxx@(Ln.10000@Call UK)@[Dev:sip:44208002xxxx@registry.tgsa.co.uk:5060]
    13:09:57.854 [MS210002] C:4.2:Offer provided. Connection(transcoding mode): 194.158.81.95:9006(9007)
    13:09:57.838 [CM503004]: Call(4): Route 1: VoIPline:01293xxxxxx@(Ln.10000@Call UK)@[Dev:sip:44208002xxxx@registry.tgsa.co.uk:5060]
    13:09:57.838 [CM503010]: Making route(s) to <sip:01293xxxxxx@192.168.30.xx;user=phone>
    13:09:57.838 [MS210000] C:4.1:Offer received. RTP connection: 192.168.30.xx:6030(6031)
    13:09:57.823 Remote SDP is set for legC:4.1
    13:09:57.823 [CM505001]: Ext.5: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Audiocodes-Sip-Gateway-MP-114 FXS_FXO/v.6.20A.022.003] PBX contact: [sip:5@192.168.30.xx:5060]
    13:09:57.823 [CM503001]: Call(4): Incoming call from Ext.5 to <sip:01293xxxxxx@192.168.30.xx;user=phone>
    13:09:57.760 [CM500002]: Info on incoming INVITE:
    INVITE sip:01293xxxxxx@192.168.30.xx;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.30.xx;branch=z9hG4bKac596532247
    Max-Forwards: 70
    Contact: <sip:11@192.168.30.xx:5060>
    To: <sip:01293xxxxxx@192.168.30.xx;user=phone>
    From: <sip:5@192.168.30.xx>;tag=1c596189346
    Call-ID: 5961887822212201113957@192.168.30.xx
    CSeq: 2 INVITE
    Allow: REGISTER, OPTIONS, INVITE, ACK, CANCEL, BYE, NOTIFY, PRACK, REFER, INFO, SUBSCRIBE, UPDATE
    Proxy-Authorization: Digest username="5",realm="3CXPhoneSystem",nonce="414d535c0503bd2525:156ca2024979c084fb89472e3ca63077",uri="sip:01293xxxxxx@192.168.30.xx",algorithm=MD5,response="d7a55048ba87f348fe195216ea210109"
    Supported: em, timer, replaces, path, resource-priority, sdp-anat
    User-Agent: Audiocodes-Sip-Gateway-MP-114 FXS_FXO/v.6.20A.022.003
    Content-Length: 0
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,594
    Likes Received:
    255
    The thing that stands out, (and what may be causing the call to fail may be something you can only see if using something like wireshark), is that fact that you have a name involved as a part of the contact, of the failing call.

    On the working call, for some reason, even though it is extension 11, the user name shows as 5

    Whereas on extension 15, the username is 15, also the response is included here but not in the failing call

    I'm not sure if those differences are what is causing the failure, you may want to contact your provider to see if they can offer an explanation that may save you some troubleshooting time. Or, download a copy of Wireshark and start looking at what is actually being sent for each call.
     
  5. MB1

    MB1

    Joined:
    Nov 2, 2007
    Messages:
    39
    Likes Received:
    0
    This is probably my fault as I was trying to remove any sensitive network information I obviously didn't do a very good job! I'll try wiresharking later. Thanks again for your help.
     
  6. MB1

    MB1

    Joined:
    Nov 2, 2007
    Messages:
    39
    Likes Received:
    0
    Fixed!
    The outbound call ID entry in 3CX was different to VOIP provider's caller ID hence the rejection.

    Thanks again for your help Leejor.
     
Thread Status:
Not open for further replies.