Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Forward to outside ##

Discussion in '3CX Phone System - General' started by looker44, Feb 12, 2013.

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

    Joined:
    Dec 31, 2012
    Messages:
    37
    Likes Received:
    0
    I am having trouble forwarding a virtual extension (has not been registered, will not have a device attached to it)
    Basically DID to 4693173299 is to dial outside ##817-583-8799 is being stopped because i do not have an outbound rule for Line:1000
    HOW TO FIX??
    i have been able to fwd a call from another extension to an outside line
    logs show
    12-Feb-2013 15:03:10.938 Leg L:251.1[Line:10000<<2142154569] is terminated: Cause: BYE from PBX
    12-Feb-2013 15:03:10.912 [CM503020]: Call(C:251): Normal call termination. Call originator: Line:10000<<2142154569. Reason: Not found
    12-Feb-2013 15:03:10.912 [CM503014]: Call(C:251): No known route from Line:10000<<2142154569 to target: <sip:817-583-8799@10.0.0.151:5060>
    12-Feb-2013 15:03:10.912 Call(C:251): from Line:10000<<2142154569 to 817-583-8799 doesn't match any outbound rule. No outbound rule could be selected.
    12-Feb-2013 15:03:10.912 [Flow] Target endpoint for 817-583-8799 can not be built!
    12-Feb-2013 15:03:10.911 [CM505003]: Provider:[VoipProvider1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [VoipProvider Fusion] PBX contact: [sip:97247951899@209.163.183.151:5060]
    12-Feb-2013 15:03:10.906 [CM503001]: Call(C:251): Incoming call from Line:10000<<2142154569 to <sip:817-583-8799@10.0.0.151:5060>
    12-Feb-2013 15:03:10.905 Line limit check: Current # of calls for line Lc:10000(@VoipProvider1[<sip:97247951899@ln01-04.fs.VoipProvider.net:5060>]) is 2; limit is 6
    12-Feb-2013 15:03:10.890 [CM503012]: Inbound specific hours w/o holidays rule (NUC-Line) for 10000 forwards to DN:817-583-8799
    12-Feb-2013 15:03:10.332 Leg L:250.1[Line:10000<<2142154569] is terminated: Cause: BYE from PBX
    12-Feb-2013 15:03:10.310 [CM503020]: Call(C:250): Normal call termination. Call originator: Line:10000<<2142154569. Reason: Not found
    12-Feb-2013 15:03:10.310 [CM503014]: Call(C:250): No known route from Line:10000<<2142154569 to target: <sip:817-583-8799@10.0.0.151:5060>
    12-Feb-2013 15:03:10.310 Call(C:250): from Line:10000<<2142154569 to 817-583-8799 doesn't match any outbound rule. No outbound rule could be selected.
    12-Feb-2013 15:03:10.310 [Flow] Target endpoint for 817-583-8799 can not be built!
    12-Feb-2013 15:03:10.309 [CM505003]: Provider:[VoipProvider1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [VoipProvider Fusion] PBX contact: [sip:97247951899@209.163.183.151:5060]
    12-Feb-2013 15:03:10.302 [CM503001]: Call(C:250): Incoming call from Line:10000<<2142154569 to <sip:817-583-8799@10.0.0.151:5060>
    12-Feb-2013 15:03:10.299 Line limit check: Current # of calls for line Lc:10000(@VoipProvider1[<sip:97247951899@ln01-04.fs.VoipProvider.net:5060>]) is 2; limit is 6
    12-Feb-2013 15:03:10.284 [CM503012]: Inbound specific hours w/o holidays rule (NUC-Line) for 10000 forwards to DN:817-583-8799
     
  2. kevin

    kevin Member

    Joined:
    Nov 23, 2006
    Messages:
    316
    Likes Received:
    1
    Hi there

    This may be due to the way the outbound rules are evaluating whether the call is allowed to be forwarded.

    What *may* be happening is that your outbound rule is restricting access by Extension Numbers, so that a call that is coming into the PBX is passing through the outbound rules, and the rule does not handle the call because the Extension Number restriction is being applied to the Originator's Number.

    You could confirm this by running a test call before making changes (that will fail), then removing the Extension Number restriction, and trying a repeat of the test call (that should succeed).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,095
    Likes Received:
    327
    Would the dashes, in the number (817-583-8799), be making any difference in finding a match in the outbound rules?
     
  4. kevin

    kevin Member

    Joined:
    Nov 23, 2006
    Messages:
    316
    Likes Received:
    1
    Hi

    Definitely yes. I had not realised that only numbers with dashes were being blocked...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. looker44

    Joined:
    Dec 31, 2012
    Messages:
    37
    Likes Received:
    0
    Ok my outbound rule is calls from extensions 300-899 go to voip provider1
    when i remove those extensions no calls go out
    when i naturally dial the outside number from an internal extension all works fine
    when i dial into the system and ask system to forward call to outside number it fails
    14-Feb-2013 15:21:21.964 Caller '2142154599' is not found in the list of allowed extensions: 300-899
    2142154599 is the caller ID of the phone from which I am calling

    how do I get around this?
     
  6. looker44

    Joined:
    Dec 31, 2012
    Messages:
    37
    Likes Received:
    0
    my workaround is to make a rule of calls with a length of 10 to go out my VOIP
     
Thread Status:
Not open for further replies.