Forward to outside nr - getting me nuts

Discussion in '3CX Phone System - General' started by vcstech, Jan 13, 2009.

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

    Joined:
    Jan 13, 2009
    Messages:
    3
    Likes Received:
    0
    Hi all,

    Playing some weeks now with 3CX and must say I'm very pleased.
    Also seriously considering to upgrade to a commercial license for the extra features.
    But first I want the basics running.
    1 thing gets me nuts ...

    Short setup description
    (FYI: All mentioned IP addresses, phone nrs, etc are fake)
    Landline = 2 x ISDN BRI (4 channels) with a 10 nr DDI
    The ISDN NT1 boxes (2) are linked to a Patton 4554 VoIP gateway and serves as the gateway for the 3CX system.
    Internally ... a bunch of devices ... 3CX voip client, Linksys SPA922, Polycom Soundpoint, Patton M-ATA, ...
    Everything works as expected, except ...

    I'll try to explain as simple as possible ...

    When someone calls on the main number 02999999 I have an inbound rule on that number that connects to a ring group EVERYONE (VirtExt800)
    It is configured as a hunt and contains 2 extensions 101 & 103
    If the call goes unanswered > it forwards to a mobile phone, f.e. 90499123456 (9 is the prefix for an outside line)
    3 cases ...
    2 are OK, 1 not

    At phone with ext108 > dial 800 > everything fine ... no one picks up ... the call is correctly forwarded
    Dialing from home to the office > dial 02999999 > idem dito ... the call is correctly forwarded
    Dialing from my mobile phone > forwarding does not work ... I hear a tone sequence indicating "connection error"

    If I change the forwarding to a regular phone nr instead of a mobile phone nr, I have the same problem

    THIS ONE IS NOT OK
    0478123456 (Proximus) > 02999999 (Belgacom) > (DID RULE) Connect to ringgroup 800 (Ext102,Ext109,then outside 90499123456)
    Log ...
    03:00:42.796 [CM503008]: Call(19): Call is terminated
    03:00:42.796 [CM503015]: Call(19): Attempt to reach <sip:800@xxx.xxx.xxx.xxx:5060> failed. Reason: No Answer
    03:00:32.734 [CM503004]: Call(19): Calling: HuntGrp800:109Ext.109@[Dev:sip:109@xxx.xxx.xxx.xxx:5060]
    03:00:32.718 [CM503004]: Call(19): Calling: HuntGrp800:102Ext.102@[Dev:sip:102@xxx.xxx.xxx.xxx:5060]
    03:00:32.718 [CM503010]: Making route(s) to <sip:800@xxx.xxx.xxx.xxx:5060>
    03:00:32.687 [CM503001]: Call(19): Incoming call from 478123456@(Ln.10000@VOIPGATE1) to <sip:800@xxx.xxx.xxx.xxx:5060>
    03:00:32.656 [CM503012]: Inbound out-of-office hours rule for 10000 forwards to DN:800

    THIS ONE IS OK
    02123456 (Telenet) > 02999999 (Belgacom) > (DID RULE) Connect to ring group 800 (Ext102,Ext109,then outside 90499123456)
    Log ...
    02:38:18.624 [CM503008]: Call(18): Call is terminated
    02:38:09.468 [CM503002]: Call(18): Alerting sip:10000@xxx.xxx.xxx.2:5060
    02:38:09.046 [CM503005]: Call(18): Forwarding: Unknown:0499123456@(Ln.10000@VOIPGATE1)@[Dev:sip:10000@xxx.xxx.xxx.2:5060, Dev:sip:10001@xxx.xxx.xxx.2:5062]
    02:38:09.031 [CM503005]: Call(18): Forwarding: Unknown:0499123456@(Ln.10000@VOIPGATE1)@[Dev:sip:10000@xxx.xxx.xxx.2:5060, Dev:sip:10001@xxx.xxx.xxx.2:5062]
    02:38:08.999 [CM503005]: Call(18): Forwarding: Unknown:0499123456@(Ln.10000@VOIPGATE1)@[Dev:sip:10000@xxx.xxx.xxx.2:5060, Dev:sip:10001@xxx.xxx.xxx.2:5062]
    02:37:58.937 [CM503004]: Call(18): Calling: HuntGrp800:109Ext.109@[Dev:sip:109@xxx.xxx.xxx.xxx:5060]
    02:37:58.921 [CM503004]: Call(18): Calling: HuntGrp800:102Ext.102@[Dev:sip:102@xxx.xxx.xxx.xxx:5060]
    02:37:58.921 [CM503010]: Making route(s) to <sip:800@xxx.xxx.xxx.xxx:5060>
    02:37:58.874 [CM503001]: Call(18): Incoming call from 2123456@(Ln.10000@VOIPGATE1) to <sip:800@xxx.xxx.xxx.xxx:5060>
    02:37:58.859 [CM503012]: Inbound out-of-office hours rule for 10000 forwards to DN:800

    Could someone be so kind to have a look at this and hopefully give me some hints?
    A big tx upfront for the effort.
    B.R,
    Mike
     
  2. discovery1

    discovery1 Member

    Joined:
    Aug 4, 2008
    Messages:
    355
    Likes Received:
    0
    The mobile you are forwarding to is not the same one you are calling from is it?
    Can you set your logging to verbose so we can see some more detail?

    Can you recheck your inbound and outbound rules to make sure things are routing correctly - in particular the order of the rules as the order can cause strange things like this to happen.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mbaltus

    Joined:
    Dec 12, 2008
    Messages:
    66
    Likes Received:
    0
    Can you at all reach the 3CX (a local extension) using the cell phones? So is the only problem you have when you are forwarding the call externally when you call with a cell phone?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    Can we see the verbose logs of the call that fails? Ensure that you have a rule that handles the outbound call to mobile. if the outbound rules is restricted by extension then this will fail.

    Try to create a kind of catch all rule that will handle any call starting with 0,1,2,3,4,5,6,7,8,9 and see if that helps.

    NB. The outbound call will NOT be from the original destination extension, but will appear as being form the original caller.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. vcstech

    Joined:
    Jan 13, 2009
    Messages:
    3
    Likes Received:
    0
    Hey guys
    Tx to all for your help, really appreciated!
    It works!!

    Had to do with the outbound rule.
    Only outbound was allowed for extensions 100-400
    So if I called from home (nr 023061234), I saw in the log ... incoming 23061234 ... so 230 is within the allowed extension range
    But calls from a mobile phone (in Belgium 0474, 0475, 0494, ...), I saw in the log f.e. 478123456 ... but 478 isn't an allowed extension and therefore was refused.

    So I cleared the "Calls from extension(s)" and now it works.

    Correct analysis?

    Mike
     
  6. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    That's pretty close. '23061234' is not in the 100-400 range, hence the issue.

    Since you can never assume all possible caller numbers, you need to have a rule that is not extension based that will allow the forwarded all when all other rules dont kick in....consider it like a 'catch all' rule.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.