Call destination cannot be resolved_Outbound calling

Discussion in '3CX Phone System - General' started by Anonymous, Dec 13, 2006.

  1. Anonymous

    Anonymous Guest

    Nice software - very easy to install, understand and configure except for outbound calling.

    My 3CX is sitting behind a server on 10.1.1.3. There are two machines on the network behind a router is 10.1.1.1.

    The router has DHCP. I have a pvc 10.1.1.3 with the following ports open;-

    TCP,UDP 5060 6000

    TCP,UDP 9000 9100

    TCP,UDP 3478 3480

    On the server
    internal ports are 7000 -7500
    external ports are9000 -9100


    My extensions are voip providers are all on hook status.

    I have several voip providers and believe that the switching between them should be done on the 3CX server and not within the phone.
    Is this correct?

    I have played with setting up outbound rules. I am using both the 3CX phone and xlite phone. However when i dial a number i get the Call destination cannot be resolved.

    My xlite domain has 10.1.1.3
    Proxy Domian is on with target domain selected

    Firewall Traversal - discover global address
    Stun server -discover


    What have i missed or doing wrong?

    Thanks
     
  2. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,677
    Likes Received:
    17
    Call rules

    Thank you for your feedback.

    One thing - does the phonesystem have a fixed ip? I assume so.

    In regards to your questions - you mentioned your VOIP providers are configured as extensions and that the switching is handled on the phone system not on the phone? I did not understand your setup in this regard.

    Usually one would have internal extensions using either soft or hardware sip phones which can, using a particular prefix, dial out via a particular voip provider. Is this the setup you need or do you have something else in mind?

    What number are you dialing? What prefix have you configured for each of the VOIP providers? Can you post the server status log?
     
  3. Anonymous

    Anonymous Guest

    The phones have fixed IPs of 10.1.1.3 and 10.1.1.4 for extensions 100 and 101

    Voip Providers configured as external lines 10000 and 10001 for fonosip and sipgate.co.uk.

    I have not configured my xlite sftphone with either provider as i assume when call is placed that the carrier will be determined by outbound rules (unless i specify on xlite when dailing ie 393613@fonosip or 10000@sipgate.co.uk)

    Below is log.


    14:05:12.578 Registrar::eek:nRefresh: Refresh: sip:101@10.1.1.4:28512
    13:57:37.500 Registrar::eek:nRefresh: Refresh: sip:100@10.1.1.3:7268
    13:11:11.796 Registrar::eek:nRefresh: Refresh: sip:101@10.1.1.4:28512
    13:03:45.453 Terminated c13 "100"<sip:100@10.1.1.3> "827827@fonosip.com"<sip:827827@fonosip.com> Call ended
    13:03:45.437 Rejected c13 "100"<sip:100@10.1.1.3> "827827@fonosip.com"<sip:827827@fonosip.com> Call destination cannot be resolved
    13:03:45.437 CallConf::findDestination: Found destination Dummy for caller Ext:100
    13:03:45.437 Registrar::resolveAddress: Registrar can not resolve "827827@fonosip.com"<sip:827827@fonosip.com>
    13:03:45.437 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:7268;rinstance=aed4bf421f9b7535>
    13:03:45.437 Incoming c13 "100"<sip:100@10.1.1.3> "827827@fonosip.com"<sip:827827@fonosip.com> Incoming call from 100
    13:03:40.843 Terminated c12 "100"<sip:100@10.1.1.3> "10000@sipgate.co.uk"<sip:10000@sipgate.co.uk> Call ended
    13:03:40.812 Rejected c12 "100"<sip:100@10.1.1.3> "10000@sipgate.co.uk"<sip:10000@sipgate.co.uk> Call destination cannot be resolved
    13:03:40.796 CallConf::findDestination: Found destination Dummy for caller Ext:100
    13:03:40.796 Registrar::resolveAddress: Registrar can not resolve "10000@sipgate.co.uk"<sip:10000@sipgate.co.uk>
    13:03:40.781 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:7268;rinstance=aed4bf421f9b7535>
    13:03:40.765 Incoming c12 "100"<sip:100@10.1.1.3> "10000@sipgate.co.uk"<sip:10000@sipgate.co.uk> Incoming call from 100
    13:03:36.750 Registrar::eek:nAdd: Add: sip:100@10.1.1.3:7268
    13:03:36.140 Registrar::eek:nRemove: Remove: sip:100@127.0.0.1:7268
    13:03:35.531 Registrar::eek:nAdd: Add: sip:100@127.0.0.1:7268
    13:03:34.125 Registrar::eek:nRemove: Remove: sip:100@10.1.1.3:7100
    13:02:56.890 Terminated c11 "100"<sip:100@10.1.1.3> "827827@fonosip.com"<sip:827827@fonosip.com> Call ended
    13:02:56.843 Rejected c11 "100"<sip:100@10.1.1.3> "827827@fonosip.com"<sip:827827@fonosip.com> Call destination cannot be resolved
    13:02:56.843 CallConf::findDestination: Found destination Dummy for caller Ext:100
    13:02:56.843 Registrar::resolveAddress: Registrar can not resolve "827827@fonosip.com"<sip:827827@fonosip.com>
    13:02:56.828 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:7100;rinstance=56b0a54de8822816>
    13:02:56.812 Incoming c11 "100"<sip:100@10.1.1.3> "827827@fonosip.com"<sip:827827@fonosip.com> Incoming call from 100
    13:01:56.828 Terminated c10 "100"<sip:100@10.1.1.3> "10000@sipgate.co.uk"<sip:10000@sipgate.co.uk> Call ended
    13:01:56.812 Rejected c10 "100"<sip:100@10.1.1.3> "10000@sipgate.co.uk"<sip:10000@sipgate.co.uk> Call destination cannot be resolved
    13:01:56.812 CallConf::findDestination: Found destination Dummy for caller Ext:100
    13:01:56.812 Registrar::resolveAddress: Registrar can not resolve "10000@sipgate.co.uk"<sip:10000@sipgate.co.uk>
    13:01:56.781 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:7100;rinstance=56b0a54de8822816>
    13:01:56.765 Incoming c10 "100"<sip:100@10.1.1.3> "10000@sipgate.co.uk"<sip:10000@sipgate.co.uk> Incoming call from 100
    13:01:26.078 Terminated c9 "100"<sip:100@10.1.1.3> "1"<sip:1@10.1.1.3> Call ended
    13:01:26.062 Rejected c9 "100"<sip:100@10.1.1.3> "1"<sip:1@10.1.1.3> Call destination cannot be resolved
    13:01:26.062 CallConf::findDestination: Found destination Dummy for caller Ext:100
    13:01:26.062 Registrar::resolveAddress: Registrar can not resolve "1"<sip:1@10.1.1.3>
    13:01:26.046 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:7100;rinstance=56b0a54de8822816>
    13:01:26.031 Incoming c9 "100"<sip:100@10.1.1.3> "1"<sip:1@10.1.1.3> Incoming call from 100
    12:55:31.921 Terminated c8 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Call ended
    12:55:31.921 Rejected c8 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Call destination cannot be resolved
    12:55:31.921 CallConf::findDestination: Found destination Dummy for caller Ext:100
    12:55:31.906 Registrar::resolveAddress: Registrar can not resolve "10000"<sip:10000@10.1.1.3>
    12:55:31.890 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:7100;rinstance=56b0a54de8822816>
    12:55:31.890 Incoming c8 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Incoming call from 100
    12:55:25.765 Registrar::eek:nAdd: Add: sip:100@10.1.1.3:7100
    12:55:25.156 Registrar::eek:nRemove: Remove: sip:100@127.0.0.1:7100
    12:55:24.562 Registrar::eek:nAdd: Add: sip:100@127.0.0.1:7100
    12:55:19.765 Registrar::eek:nRemove: Remove: sip:100@10.1.1.3:7392
    12:33:08.468 Terminated c7 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Call ended
    12:33:08.453 Rejected c7 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Call destination cannot be resolved
    12:33:08.453 CallConf::findDestination: Found destination Dummy for caller Ext:100
    12:33:08.453 Registrar::resolveAddress: Registrar can not resolve "10000"<sip:10000@10.1.1.3>
    12:33:08.437 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:7392;rinstance=9a8d16c033b0d614>
    12:33:08.437 Incoming c7 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Incoming call from 100
    12:33:01.953 Registrar::eek:nAdd: Add: sip:100@10.1.1.3:7392
    12:33:01.359 Registrar::eek:nRemove: Remove: sip:100@127.0.0.1:7392
    12:33:00.750 Registrar::eek:nAdd: Add: sip:100@127.0.0.1:7392
    12:32:59.390 Registrar::eek:nRemove: Remove: sip:100@127.0.0.1:7322
    12:17:11.015 Registrar::eek:nRefresh: Refresh: sip:101@10.1.1.4:28512
    12:11:55.406 Terminated c6 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Call ended
    12:11:55.359 Rejected c6 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Call destination cannot be resolved
    12:11:55.343 CallConf::findDestination: Found destination Dummy for caller Ext:100
    12:11:55.343 Registrar::resolveAddress: Registrar can not resolve "10000"<sip:10000@10.1.1.3>
    12:11:55.328 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@127.0.0.1:7322;rinstance=49c9d3a972f03c33>
    12:11:55.312 Incoming c6 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Incoming call from 100
    12:11:48.343 Registrar::eek:nAdd: Add: sip:100@127.0.0.1:7322
    12:11:43.718 Registrar::eek:nRemove: Remove: sip:100@10.1.1.3:50196
    11:56:45.375 Terminated c5 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Call ended
    11:56:45.328 Rejected c5 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Call destination cannot be resolved
    11:56:45.328 CallConf::findDestination: Found destination Dummy for caller Ext:100
    11:56:45.312 Registrar::resolveAddress: Registrar can not resolve "10000"<sip:10000@10.1.1.3>
    11:56:45.296 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:50196;rinstance=8893f27747ee104b>
    11:56:45.296 Incoming c5 "100"<sip:100@10.1.1.3> "10000"<sip:10000@10.1.1.3> Incoming call from 100
    11:51:22.093 Terminated c4 "100"<sip:100@10.1.1.3> "10001"<sip:10001@10.1.1.3> Call ended
    11:51:22.046 Rejected c4 "100"<sip:100@10.1.1.3> "10001"<sip:10001@10.1.1.3> Call destination cannot be resolved
    11:51:22.046 CallConf::findDestination: Found destination Dummy for caller Ext:100
    11:51:22.031 Registrar::resolveAddress: Registrar can not resolve "10001"<sip:10001@10.1.1.3>
    11:51:22.031 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:50196;rinstance=8893f27747ee104b>
    11:51:22.015 Incoming c4 "100"<sip:100@10.1.1.3> "10001"<sip:10001@10.1.1.3> Incoming call from 100
    11:51:13.890 Terminated c3 "100"<sip:100@10.1.1.3> "100001"<sip:100001@10.1.1.3> Call ended
    11:51:13.875 Rejected c3 "100"<sip:100@10.1.1.3> "100001"<sip:100001@10.1.1.3> Call destination cannot be resolved
    11:51:13.875 CallConf::findDestination: Found destination Dummy for caller Ext:100
    11:51:13.875 Registrar::resolveAddress: Registrar can not resolve "100001"<sip:100001@10.1.1.3>
    11:51:13.859 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:50196;rinstance=8893f27747ee104b>
    11:51:13.843 Incoming c3 "100"<sip:100@10.1.1.3> "100001"<sip:100001@10.1.1.3> Incoming call from 100
    11:50:16.578 Terminated c2 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> Call ended
    11:49:39.062 Established c2 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> Call is established
    11:49:31.125 CallConf::eek:nOutgoingResp: Got response from <sip:101@10.1.1.4:28512;rinstance=00abe7672784a89e>;tag=425bc62b on invite from <sip:100@10.1.1.3>;tag=042bfc7b. Response line: SIP/2.0 180 Ringing
    11:49:30.656 Calling c2 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> Send INVITE to Ext:101
    11:49:30.578 Routed c2 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> From: Ext:100; To: Ext:101
    11:49:30.578 CallConf::findDestination: Found destination Ext:101 for caller Ext:100
    11:49:30.562 Registrar::checkAor: Registrar resolved sip:101@10.1.1.3 as <sip:101@10.1.1.4:28512;rinstance=00abe7672784a89e>
    11:49:30.562 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:50196;rinstance=8893f27747ee104b>
    11:49:30.546 Incoming c2 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> Incoming call from 100
    11:49:30.531 Terminated c1 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> Call ended
    11:49:25.171 Registrar::eek:nAdd: Add: sip:100@10.1.1.3:50196
    11:49:24.562 Registrar::eek:nRemove: Remove: sip:100@127.0.0.1:50196
    11:49:23.953 Registrar::eek:nAdd: Add: sip:100@127.0.0.1:50196
    11:49:22.593 Registrar::eek:nRemove: Remove: sip:100@10.1.1.3:64018
    11:48:53.765 Calling c1 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> Send INVITE to IVR:101
    11:48:53.765 Session::processOffer: sip:10.1.1.3
    11:48:53.609 Session::eek:nNoAnswer: Redirect call to VoiceMail (IVR:101)
    11:48:53.609 Session::eek:nNoAnswer: L:<s1-s2>:left hasn't answered. Cancel ringing.
    11:48:47.500 CallConf::eek:nOutgoingResp: Got response from <sip:101@10.1.1.4:28512;rinstance=00abe7672784a89e>;tag=4b43185b on invite from <sip:100@10.1.1.3>;tag=1521c212. Response line: SIP/2.0 180 Ringing
    11:48:39.359 Calling c1 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> Send INVITE to Ext:101
    11:48:39.234 Routed c1 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> From: Ext:100; To: Ext:101
    11:48:39.234 CallConf::findDestination: Found destination Ext:101 for caller Ext:100
    11:48:39.218 Registrar::checkAor: Registrar resolved sip:101@10.1.1.3 as <sip:101@10.1.1.4:28512;rinstance=00abe7672784a89e>
    11:48:39.078 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:64018;rinstance=14ed44a09cfe32d1>
    11:48:38.343 Incoming c1 "100"<sip:100@10.1.1.3> "101"<sip:101@10.1.1.3> Incoming call from 100
    11:48:24.234 Registrar::eek:nAdd: Add: sip:100@10.1.1.3:64018
    11:48:23.625 Registrar::eek:nRemove: Remove: sip:100@127.0.0.1:64018
    11:48:23.015 Registrar::eek:nAdd: Add: sip:100@127.0.0.1:64018
    11:46:49.078 Registrar::eek:nSuccess: RegHandler: success in registering <sip:827827@10.1.1.3> for sip:10000@10.1.1.3
    11:45:58.906 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    11:45:28.937 LineImpl::registered: Line [#8133313 @sipgate.co.uk] has been registered at provider
    11:45:28.937 Registrar::eek:nSuccess: RegHandler: success in registering <sip:8133313@10.1.1.3> for sip:10001@10.1.1.3
    11:44:30.656 LineImpl::update: Line: register line 8133313
    11:44:30.625 LineImpl::update: Line: register line 827827
    11:43:28.531 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    11:41:58.296 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    11:40:28.062 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    11:32:56.937 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    11:23:10.203 Registrar::eek:nRefresh: Refresh: sip:101@10.1.1.4:28512
    10:36:18.359 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    10:35:54.531 Registrar::eek:nRemove: Remove: sip:100@127.0.0.1:37426
    10:35:18.203 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    10:34:42.390 Registrar::eek:nAdd: Add: sip:100@127.0.0.1:37426
    10:34:23.359 ??: SL: connected Einstein:0/PHPExtension_0 at [Einstein]/PHPExtension_0
    10:34:18.062 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    10:29:09.312 Registrar::eek:nRefresh: Refresh: sip:101@10.1.1.4:28512
    09:38:44.343 LineImpl::registered: Line [#827827 @fonosip.com] has been registered at provider
    09:38:44.328 Registrar::eek:nSuccess: RegHandler: success in registering <sip:827827@10.1.1.3> for sip:10000@10.1.1.3
    09:37:39.437 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    09:36:09.203 Registrar::eek:nRequestRetry: Request retry for <sip:827827@10.1.1.3>
    09:35:08.671 Registrar::eek:nAdd: Add: sip:101@10.1.1.4:28512
    09:33:49.015 SessionMgr::thread: ** Entering Main Loop **
    09:33:49.015 SessionMgr::run: ** Start Session Manager **
    09:33:49.000 SessionMgr::run: ** Initialize Status Monitor **
    09:33:49.000 LineImpl::update: Line: register line 827827
    09:33:42.250 DBA: ** Database connection Ok **
    09:33:38.593 SessionMgr::run: ** Initialize Lines Manager **
    09:33:38.593 SessionMgr::run: STUN hasn't been able to resolve external IP!
    09:33:36.234 MediaServerConnected: Media Server is connected
    09:33:36.203 ??: SL: connected Einstein:0/MediaServer at [Einstein]/MediaServer
    09:33:35.593 SessionMgr::run: ** Initialize Client Authentication **
    09:33:35.593 SessionMgr::run: ** Initialize Server Authentication **
    09:33:35.593 SessionMgr::run: ** Initialize DUM **
    09:33:35.437 SessionMgr::run: ** Adding transports **
     
  4. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,677
    Likes Received:
    17
    New build

    I am still looking into your log, but one thing i would like to suggest right away is to upgrade to the latest build, which we posted today (its not been announced yet, but you can download it from this link

    http://www.3cx.com/downloads/3cxphonesystem2.exe

    From the log you posted, it seems that the external IP was not resolved, and this is because of an error in our old version. It does not mean it will fix the issue but its likely to be at least one of the issues.

    Could you download, and try again? You can backup the configuration and restore it from the general page, so there is no need to recreate the configuration.
     
  5. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,677
    Likes Received:
    17
    Dialing

    In addition, i think you are entering a number and the domain

    827827@fonosip.com

    However, with our system you should just dial the prefix + the number, e.g

    9,827827

    In this case you would have to associate the prefix 9 with the provider fonosip

    Then the system will see the prefix, associate it with fonosip provider, delete the prefix and pass on the call to fonosip. And log this as:

    internal line number @ fonosip (name you have given to the provider)

    Hope this helps.....
     
  6. Anonymous

    Anonymous Guest

    I am still lost?

    Where do i associate the prefix 9?

    if i wanted to dial 393613 on fonsip i would enter on xlite 10000393613?

    With the following config on the 3CX

    Line Number Gateway Gateway/Provider Internal number

    827827 fonosip.com Provider 10000
    8133313 sipgate.co.uk Provider 10001



    Rule Name newtest

    Apply this rule to these calls
    Calls to Numbers starting with 10000 (internal Number)
    Calls from extension(s)

    Make outbound calls on
    VOIP Gateway Any gateway
    VOIP Provider fonosip.com
    Transform mask rrrrr
     
  7. Anonymous

    Anonymous Guest

    I installed the new software and still have logs showing that the destination is unresolved.

    19:47:48.671 Registrar::eek:nRequestRetry: Request retry for <sip:8133313@83.24.1.44>
    19:47:48.656 Registrar::eek:nRequestRetry: Request retry for <sip:8133313@83.24.1.44>
    19:47:48.640 Registrar::eek:nRequestRetry: Request retry for <sip:8133313@83.24.1.44>
    19:47:40.625 Terminated c18 "100"<sip:100@10.1.1.3> "10000363913"<sip:10000363913@10.1.1.3> Call ended
    19:47:40.625 Rejected c18 "100"<sip:100@10.1.1.3> "10000363913"<sip:10000363913@10.1.1.3> Call destination cannot be resolved
    19:47:40.625 CallConf::findDestination: Found destination Dummy for caller Ext:100
    19:47:40.609 Registrar::resolveAddress: Registrar can not resolve "10000363913"<sip:10000363913@10.1.1.3>
    19:47:40.593 Registrar::checkAor: Registrar resolved sip:100@10.1.1.3 as <sip:100@10.1.1.3:7128;rinstance=c909569b6f56d8b1>
    19:47:40.578 Incoming c18 "100"<sip:100@10.1.1.3> "10000363913"<sip:10000363913@10.1.1.3> Incoming call from 100
    19:47:40.578 AuthMgr::eek:nAuthSuccess: Extension "100"<sip:100@10.1.1.3>;tag=b47a8548 has been registered successfully
     
  8. archie

    archie Well-Known Member
    3CX Staff

    Joined:
    Aug 18, 2006
    Messages:
    1,309
    Likes Received:
    0
    There's also a prefix to reach outbound line. You can find it in the web interface, menu General settings, section Other, named 'Prefix for external calls'. This prefix should be dialled at the beginning of number. By default it is set to be '0'. It will be automatically removed, so you don't need to remove it in the outbound rule.

    It's seen from the logs that you've dialed '10000363913'. If you will dial '010000363913' instead - with the outbound rule you've described above - your call will be routed correctly, and dial number '363913' will be passed to your VoIP provider. But I doubt it's correct number anyway, since most providers require to get numbers in international format, like '0035796xxxxxx'. It looks like your number is too short.
    And, as advice, you don't need to make dial prefix (in your case - 10000) to be so long. It could be just 1-2 digits. Anyway, call is treated to be outbound if you preceede it with prefix digit specified in General settings, as I described above. Generally, you need this additional outbound rules only to reach specific line(s).
     
  9. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,677
    Likes Received:
    17
    Call Rules

    You need to create a call rule with settings as follows

    Apply the Rule to these calls
    Calls to Number starting with 9

    Make outbound calls on
    Select VOIP provider you want to use

    Transform mask
    r

    The last transform mask, r, removes the prefix 9

    Now you should be able to dial your number by entering

    9 + number to dial

    System will route call via VOIP provider and before doing so remove the leading 9 which is a prefix.

    let us know how it goes.

    I will review the chatper on outbound rules to make it clearer
     

Share This Page