Call forwarding to outside number

Discussion in '3CX Phone System - General' started by ryanh, Sep 26, 2012.

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

    Joined:
    Sep 26, 2012
    Messages:
    4
    Likes Received:
    0
    I am attempting to set up call forwarding to a cellphone through the digital receptionist. How this should work is that after hours, someone will call the main line, which is answered by the digital receptionist, and they press 7 to reach the emergency menu. They will then press a number to be transferred to an extension which is not registered but has been set up to forward to a cell phone. This works fine if I test it from inside the building - going through the digital receptionist or just dialing the extension directly. If I call in from an outside line, I get "call transfer failed". I did search for other posts about this and have tried various things with no luck. I do have Enable Outgoing calls in Voicemail Menu selected. I also tested unchecking the Supports Re-Invite and Replaces header options under the Other tab in the extension, and got the same result. Can anyone shed some light on this? Thanks!

    Running:
    3CX V.9 (with all updates)
    Patton 4960 PRI Gateway

    Log of test call:

    16:21:35.386 Currently active calls [none]
    16:21:34.843 [CM503008]: Call(14807): Call is terminated
    16:21:28.947 [MS210003] C:14807.2:Answer provided. Connection(transcoding mode[unsecure]):127.0.0.1:7170(7171)
    16:21:28.946 [MS210001] C:14807.1:Answer received. RTP connection[unsecure]: 10.0.0.228:5018(5019)
    16:21:28.945 Remote SDP is set for legC:14807.1
    16:21:28.820 [MS210002] C:14807.1:Offer provided. Connection(transcoding mode): 10.0.0.30:7168(7169)
    16:21:28.820 [MS210000] C:14807.2:Offer received. RTP connection: 127.0.0.1:40654(40655)
    16:21:28.819 Remote SDP is set for legC:14807.2
    16:21:28.673 [CM503016]: Call(14807): Attempt to reach <sip:1950@127.0.0.1:5060> failed. Reason: Not Found
    16:21:28.671 [CM503003]: Call(14807): Call to sip:12244655732@10.0.0.228:5060 has failed; Cause: 404 Not Found; from IP:10.0.0.228:5060
    16:21:28.654 [CM503002]: Call(14807): Alerting sip:10000@10.0.0.228:5060
    16:21:28.558 [CM503025]: Call(14807): Calling Unknown:12244655732@(Ln.10000@PattonSN4960)@[Dev:sip:10000@10.0.0.228:5060]
    16:21:28.556 [MS210002] C:14807.3:Offer provided. Connection(transcoding mode): 10.0.0.30:7172(7173)
    16:21:28.507 [CM503005]: Call(14807): Forwarding: Unknown:12244655732@(Ln.10000@PattonSN4960)@[Dev:sip:10000@10.0.0.228:5060]
    16:21:28.503 [CM503016]: Call(14807): Attempt to reach <sip:1950@127.0.0.1:5060> failed. Reason: Not Registered
    16:21:28.502 [CM503017]: Call(14807): Target is not registered: Ext:Ext.1950
    16:21:28.501 [CM503010]: Making route(s) to <sip:1950@127.0.0.1:5060>
    16:21:28.500 Refer: from=<sip:8005@127.0.0.1:5060>;tag=d470565a; to="Open DID:"<sip:2245874256@127.0.0.1:5060>;tag=c00e6a1f; RefTo=<sip:1950@127.0.0.1:5060>
    16:21:28.290 [MS210003] C:14807.2:Answer provided. Connection(transcoding mode[unsecure]):127.0.0.1:7170(7171)
    16:21:28.290 [MS210001] C:14807.1:Answer received. RTP connection[unsecure]: 10.0.0.228:5018(5019)
    16:21:28.289 Remote SDP is set for legC:14807.1
    16:21:28.209 [MS210002] C:14807.1:Offer provided. Connection(transcoding mode): 10.0.0.30:7168(7169)
    16:21:28.209 [MS210000] C:14807.2:Offer received. RTP connection: 127.0.0.1:40654(40655)
    16:21:28.207 Remote SDP is set for legC:14807.2
    16:21:23.692 [MS211000] C:14807.1: 10.0.0.228:5018 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
    16:21:13.839 Session 3198305 of leg C:14807.1 is confirmed
    16:21:13.731 [CM503007]: Call(14807): Device joined: sip:8005@127.0.0.1:40600;rinstance=b4b026fd6dcd8e1c
    16:21:13.729 [CM503007]: Call(14807): Device joined: sip:10000@10.0.0.228:5060
    16:21:13.727 [MS210003] C:14807.1:Answer provided. Connection(transcoding mode[unsecure]):10.0.0.30:7168(7169)
    16:21:13.725 [MS210001] C:14807.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40654(40655)
    16:21:13.723 Remote SDP is set for legC:14807.2
    16:21:13.719 [CM505001]: Ext.8005: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:8005@127.0.0.1:5060]
    16:21:13.719 [CM503002]: Call(14807): Alerting sip:8005@127.0.0.1:40600;rinstance=b4b026fd6dcd8e1c
    16:21:13.599 [CM503025]: Call(14807): Calling Ext:Ext.8005@[Dev:sip:8005@127.0.0.1:40600;rinstance=b4b026fd6dcd8e1c]
    16:21:13.599 [MS210002] C:14807.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7170(7171)
    16:21:13.536 [MS210000] C:14807.1:Offer received. RTP connection: 10.0.0.228:5018(5019)
    16:21:13.536 [CM503004]: Call(14807): Route 1: Ext:Ext.8005@[Dev:sip:8005@127.0.0.1:40600;rinstance=b4b026fd6dcd8e1c]
    16:21:13.536 [CM503010]: Making route(s) to <sip:8005@10.0.0.30:5060>
    16:21:13.536 Remote SDP is set for legC:14807.1
    16:21:13.536 [CM503001]: Call(14807): Incoming call from 2245874256@(Ln.10000@PattonSN4960) to <sip:8005@10.0.0.30:5060>
    16:21:13.536 [CM503012]: Inbound any hours rule (Open DID) for 10000 forwards to DN:8005
    16:21:13.536 Looking for inbound target: called=8472895893; caller=2245874256
    16:21:13.521 [CM500002]: Info on incoming INVITE:
    INVITE sip:10000@10.0.0.30:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.228:5060;branch=z9hG4bK647baa5b2741d9b46
    Max-Forwards: 70
    Contact: <sip:2245874256@10.0.0.228:5060>
    To: <sip:8472895893@10.0.0.30:5060>
    From: <sip:2245874256@10.0.0.228:5060>;tag=b306e1677e
    Call-ID: 4d09fbefddd91fee
    CSeq: 10394 INVITE
    Proxy-Authorization: Digest username="10000",realm="3CXPhoneSystem",nonce="414d535c067402c938:51bad12eb89f36aeda77e2b9d182b070",uri="sip:10000@10.0.0.30:5060",response="3bb677c9554b23d29f81fa3a974be02c",algorithm=MD5
    Supported: replaces
    User-Agent: Patton SN4960 1E24V 00A0BA0538F0 R5.4 2010-05-14 H323 RBS SIP M5T SIP Stack/4.0.28.28
    Content-Length: 0
     
  2. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    I have the same thing setup your trying to do. My situation is slightly different.

    digital receptionist answers. Caller presses 5 for emergency. This rings a ring all ring group with phantom extensions all set to forward to a cell phone.

    I set the phanton extensions mobile number on the general page. Under "away" under forwarding rules I set forward internal and external calls to "my mobile number". On the "other" tab I set the current status to "away". I have 5 phantom extensions that all ring mobiles at the same time when someone presses 5.

    You will need to change your outbound parameters on your voip/pstn trunk for "from user part'" to OriginatorCallerID", otherwise the caller ID to the mobile will be your main number or the trunk number or what ever is on the outbound caller ID for that extension.

    I have not tried this with the "rebound" feature yet.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    You dont need that and I would recommend not enabling that...that can be a security risk. Could be used to bounce calls off your system.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    Just for reference I tried using my ring all group that dials my multiple phantom phones with the rebound option checked. It will not work with the rebound option. You can only call one phantom extension that rings a mobile with the rebound option checked.

    I tried several work arounds but couldnt get it to work.

    One way to get around this is to setup google voice and forward your call to the google voice number. You can then use google voice to ring multiple mobiles at the same time with the ability to announce the call. You can also revert it back to the google voicemail system which will transcribe the voicemail and email it out.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. 3CXfoxhallsolutions

    3CXfoxhallsolutions New Member

    Joined:
    Sep 8, 2012
    Messages:
    211
    Likes Received:
    0
    Hi ryanh
    I have had similar problems in not getting calls going to mobiles from the Auto-Attendant.
    My solution was to set up a phantom extension and put the outside number (be it mobile or landline), as the mobile number associated with that extension. I then tick the box to have the mobile ring with the extension ... This seems to make the extension show as registered in 3CX status. I also check the box for 'PBX Delivers Audio' on the 'Other' tab for that extension. It also pays to have a decent delay in the No-Answer section if you want the call to go to e.g. mobile voice-mail if not answered.

    The Auto-Attendant can then be assigned that [phantom] extension as the option for the call-out to the mobile number, or for the time-out - depending on what you want it to do ...

    Although that's a bit of a chore - it seems to be rock-solid!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. paul.hadley

    paul.hadley New Member

    Joined:
    Aug 24, 2010
    Messages:
    122
    Likes Received:
    0
    16:21:28.671 [CM503003]: Call(14807): Call to sip:12244655732@10.0.0.228:5060 has failed; Cause: 404 Not Found; from IP:10.0.0.228:506

    I think you have a dial plan error. If you log a softphone into the extension you are using and try dialing the mobile does the call fail.

    A quick fix to ensure you dial plan is OK is on the extension number you are using for the forwarding add a prefix so 07866 123456 would be 90 07866 123456.

    Then in dial plans generate a outbound rule for 9007866123456 that strips out the first two digits and place it at the top of the outbound rules plan. You can the guarantee which rule is used for the forward. If you want extra security just make the rule only applicable to your unregistered extension.
     
Thread Status:
Not open for further replies.