Call fails from Digital receptionist transfered to extension

Discussion in '3CX Phone System - General' started by netswork, Oct 7, 2011.

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

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    I have a situation where the customer needs an on call person after hours. The on call person changes. So my solution was to pick one phone and have them forward that phone to their cell phone after hours. Phones are cisco SPA 525's.

    Call comes into patton PRI gateway, after hours digital receptionist answers. Caller presses 2 which is set to transfer to the extension. The extension is set to forward to a number (9xxxxxxx). Call fails. There is an outbound route for the patton with 9 + 7 digits stripping the 9. we can dial 7 digits just fine.

    I have another customer doing this exact same thing, only difference is they use a voip service rather than a patton and PRI. Here is the call log, any help would be appreciated.

    Digital receptionist is 8001. The extension is 2000 forwarded to 93526852

    I Know the problem lies here 07:55:20.219 [CM503014]: Call(164): No known route to target: <sip:93526852@192.168.0.150:5060>

    But there is a route for 9xxxxxx....we can dial that number just fine.


    07:55:20.220 [CM503016]: Call(164): Attempt to reach <sip:2000@127.0.0.1:5060> failed. Reason: Redirected
    07:55:20.219 [CM503003]: Call(164): Call to sip:2000@192.168.0.150 has failed; Cause: 302 Moved Temporarily; from IP:192.168.0.160:5060
    07:55:20.219 [CM503014]: Call(164): No known route to target: <sip:93526852@192.168.0.150:5060>
    07:55:20.218 [CM503006]: Call(164): Diverted to: <sip:93526852@192.168.0.150:5060>
    07:55:20.148 [CM503025]: Call(164): Calling Ext:Ext.2000@[Dev:sip:2000@192.168.0.160:5060]
    07:55:20.096 [CM503004]: Call(164): Route 1: Ext:Ext.2000@[Dev:sip:2000@192.168.0.160:5060]
    07:55:20.095 [CM503010]: Making route(s) to <sip:2000@127.0.0.1:5060>
    07:55:13.152 Currently active calls - 1: [164]
    07:55:03.169 [CM503016]: Call(164): Attempt to reach <sip:2000@127.0.0.1:5060> failed. Reason: Redirected
    07:55:03.167 [CM503003]: Call(164): Call to sip:2000@192.168.0.150 has failed; Cause: 302 Moved Temporarily; from IP:192.168.0.160:5060
    07:55:03.167 [CM503014]: Call(164): No known route to target: <sip:93526852@192.168.0.150:5060>
    07:55:03.166 [CM503006]: Call(164): Diverted to: <sip:93526852@192.168.0.150:5060>
    07:55:03.093 [CM503025]: Call(164): Calling Ext:Ext.2000@[Dev:sip:2000@192.168.0.160:5060]
    07:55:03.041 [CM503004]: Call(164): Route 1: Ext:Ext.2000@[Dev:sip:2000@192.168.0.160:5060]
    07:55:03.040 [CM503010]: Making route(s) to <sip:2000@127.0.0.1:5060>
    07:54:42.022 [CM503007]: Call(164): Device joined: sip:8001@127.0.0.1:40600;rinstance=63c24f7de3021e13
    07:54:42.020 [CM503007]: Call(164): Device joined: sip:10000@192.168.0.151:5060
    07:54:42.017 [CM505001]: Ext.8001: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:8001@127.0.0.1:5060]
    07:54:42.017 [CM503002]: Call(164): Alerting sip:8001@127.0.0.1:40600;rinstance=63c24f7de3021e13
    07:54:41.865 [CM503025]: Call(164): Calling Ext:Ext.8001@[Dev:sip:8001@127.0.0.1:40600;rinstance=63c24f7de3021e13]
    07:54:41.824 [CM503004]: Call(164): Route 1: Ext:Ext.8001@[Dev:sip:8001@127.0.0.1:40600;rinstance=63c24f7de3021e13]
    07:54:41.824 [CM503010]: Making route(s) to <sip:8001@192.168.0.150:5060>
    07:54:41.817 [CM503001]: Call(164): Incoming call from 4325577601@(Ln.10000@Patton) to <sip:8001@192.168.0.150:5060>
    07:54:41.813 [CM503012]: Inbound outside specific hours incl. holidays rule (unnamed) for 10000 forwards to DN:8001
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    Re: Call fails from Digital receptionist transfered to exten

    Ok I found that if I take my inbound number and ring an extension directly...that is configured for call forwarding...these fail also...so it has nothing to do with the digital receptionist. Here is what I have found...but I dont know how to fix it.

    in my outbound rules I have them configured to only work from certain extensions. I need this because I have two locations...one dials out PRI one dials out SIP trunk voip provider. If I make a new outbound rule with the prefix of the number I am forwarding to...with no restrictions on extensions...the call goes out. From the logs it looks like the call is orginating from extension 10000...which is the virtual extension for the patton PRI gateway where the inbound call is coming from. I can not add that extension in the allowed extension list because I get an error about the ENL value.

    "The entered extensions doesnt respect the ENL value."

    My only work around I can come up with right now is to create an outbound dial rule for every cell phone for every employee that might be on call with no restrictions on extension...this is not the best scenario. I compared this to my other install which does not have extension restrictions on the outbound rules and it works fine.
     
    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
    Re: Call fails from Digital receptionist transfered to exten

    I suppose I could change the virtual extension of the patton gateway to be a 4 digit extension like the rest of the phones and possibly get around this problem by adding that new extension in the allowed list for outbound routes. This is in production and I would prefer to not have to do that if anyone knows how to fix this....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Re: Call fails from Digital receptionist transfered to exten

    I think that the best way to resolve issue is to use "call forwarding profiles" of the extension.
    User can switch them manually(using different methods) and PBX can be configured to schedule an automatic switching.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    Re: Call fails from Digital receptionist transfered to exten

    Thanks for your reply. Would I not still run into this outbound route issue with the patton?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    Re: Call fails from Digital receptionist transfered to exten

    Also not everyone has PC and the numbers that need to be forwarded to change often.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    Re: Call fails from Digital receptionist transfered to exten

    From what I can tell working with 3CX support on this issue, the problem is that the sip call outbound is coming from the patton. The patton's extension is 10000. This was assigned to the patton by 3cx. My extension are xxxx. So when I have outbound rules with allowed extensions only allowing some 4 digit extensions the call fails. If I remove the allowed extensions the call works.

    Because of my 2 locations using different gateways I am required to use allowed extension rules on my outbound routes. 3CX will not allow me to enter 10000 as an allowed extension because the system is configured for 4 digit extensions. So my current work around was to create outbound routes with the prefix of the entire cell phone number that the customer is going to forward calls to. about 15 different routes. These routes have no extension restrictions and thus work.

    Looks like the solution is to change the extension of the patton to a 4 digit extension...Note to anyone who may be deploying a patton smartnode 4960. I will say the patton deployment was sooooooo simple compared to configuring a MGCP voice gateway on a cisco router.

    I am working with 3cx support to see if there is a way to modify the system to allow me to enter a 5 digit extension in the allowed extension list on the outbound route. If thats a no go then I will have to reconfigure the patton. I will update the post on the outcome.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Re: Call fails from Digital receptionist transfered to exten

    It is easy to verify. You have an environment where you can check it.
    It is the weighty argument and I'm not able to argue against, because there are many ways to resolve this issue but all solutions are not instant...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.