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.

Mobile Number issue

Discussion in '3CX Phone System - General' started by jsadan, Aug 25, 2010.

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

    Joined:
    May 3, 2010
    Messages:
    91
    Likes Received:
    0
    I am currently using 3CX 9 Demo version on a XP Pro machine.

    Whenever I try to set my extension to 'Out of Office' and the rules are set to forward my calls to my cell. The external callers are getting a "Call transfer failed, number is busy" notification. Now when I call from a internal extension it works just fine. I think the issue is with my outbound rule or DTMF per Service Logs I will post at the bottom.

    What I have done:
    I setup the mobile number (including area code) in the extension status page.

    Set Out of Office rules to forward both internal and external calls to My Mobile Number.

    Set my Status to Out of Office.

    -------------------------------------------------------------------------------------

    Here are the logs

    Code:
    09:46:13.917  [CM503008]: Call(255): Call is terminated
    09:46:03.964  [CM503016]: Call(255): Attempt to reach <sip:14@127.0.0.1:5060> failed. Reason: Busy
    09:46:03.964  [CM303006]: There's no outbound rule for external number '**********' defined
    09:46:03.964  [CM303006]: There's no outbound rule for external number '**********' defined
    09:46:03.964  [CM503010]: Making route(s) to <sip:14@127.0.0.1:5060>
    09:46:03.964  [CM505003]: Provider:[lax.teliax.com] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [TELIAX GEAR v4.1.0x] PBX contact: [sip:(Username)@192.168.XX.XXX:5060]
    09:46:00.167  [MS211000] C:255.1: 63.211.239.153:18864 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
    09:45:49.886  [CM503007]: Call(255): Device joined: sip:80@127.0.0.1:40600;rinstance=be52aac15800b9a7
    09:45:49.870  [CM503007]: Call(255): Device joined: sip:(Username)@voip-co4.teliax.com:5060
    09:45:49.855  [CM505001]: Ext.80: 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:80@127.0.0.1:5060]
    09:45:49.855  [CM503002]: Call(255): Alerting sip:80@127.0.0.1:40600;rinstance=be52aac15800b9a7
    09:45:49.698  [CM503025]: Call(255): Calling Ext:Ext.80@[Dev:sip:80@127.0.0.1:40600;rinstance=be52aac15800b9a7]
    09:45:49.683  [CM503004]: Call(255): Route 1: Ext:Ext.80@[Dev:sip:80@127.0.0.1:40600;rinstance=be52aac15800b9a7]
    09:45:49.683  [CM503010]: Making route(s) to <sip:80@192.168.XX.XXX:5060>
    09:45:49.667  [CM505003]: Provider:[lax.teliax.com] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [TELIAX GEAR v4.1.0x] PBX contact: [sip:(Username)@192.168.XX.XXX:5060]
    09:45:49.667  [CM503001]: Call(255): Incoming call from **********@(Ln.10001@lax.teliax.com) to <sip:80@192.168.100.202:5060>
    
    Key errors

    09:46:03.964 [CM303006]: There's no outbound rule for external number '**********' defined
    09:46:03.964 [CM303006]: There's no outbound rule for external number '**********' defined

    09:46:00.167 [MS211000] C:255.1: 63.211.239.153:18864 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,113
    Likes Received:
    329
    Did you also include any prefix that you would normally dial from an extension to reach an outside line?

    Do you have the ability to make two outside calls with your VoIP provider, one incoming and one back out to your mobile? Is the trunk set in 3CX to allow more than one call?
     
  3. jsadan

    Joined:
    May 3, 2010
    Messages:
    91
    Likes Received:
    0
    Yes I have.

    I do have 2 outside calls with my VoIP provider and I set 3CX to 5 but since I have the Demo version I have 2.
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,113
    Likes Received:
    329
    Since you've hidden the outbound number that 3CX can't find a route for, you will have to compare a working outbound call (compare the digits) and a non working forwarded call. Are you actually able to place two outgoing calls from two extensions, at the same time?
     
  5. jsadan

    Joined:
    May 3, 2010
    Messages:
    91
    Likes Received:
    0
    Alright will do, I will have the service logs up shortly.

    P.S. Appreciate the help.
     
  6. jsadan

    Joined:
    May 3, 2010
    Messages:
    91
    Likes Received:
    0
    Yes I can have 2 outgoing calls from 2 extensions at the same time.

    Successful outgoing call.

    Code:
    11:09:38.339  [CM503008]: Call(263): Call is terminated
    11:09:31.089  Currently active calls - 1: [263]
    11:09:26.589  [CM505003]: Provider:[lax.teliax.com] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [TELIAX GEAR v4.1.0x] PBX contact: [sip:(Username)@192.168.XX.XXX:5060]
    11:09:26.573  [CM503002]: Call(263): Alerting sip:(Username)@voip-co4.teliax.com:5060
    11:09:22.761  [CM503025]: Call(263): Calling VoIPline:(***)***-****@(Ln.10001@lax.teliax.com)@[Dev:sip:(Username)@voip-co4.teliax.com:5060]
    11:09:22.714  [CM503004]: Call(263): Route 2: VoIPline:***-****@(Ln.10001@lax.teliax.com)@[Dev:sip:(Username)@voip-co4.teliax.com:5060]
    11:09:22.714  [CM503004]: Call(263): Route 1: VoIPline:(***)***-****@(Ln.10001@lax.teliax.com)@[Dev:sip:(Username)@voip-co4.teliax.com:5060]
    11:09:22.714  [CM503010]: Making route(s) to <sip:***-****@192.168.XX.XX>
    11:09:22.714  [CM505001]: Ext.14: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA942-5.1.15(a)] PBX contact: [sip:14@192.168.XX.XXX:5060]
    11:09:22.698  [CM503001]: Call(263): Incoming call from Ext.14 to <sip:***-****@192.168.XX.XX>
    
    Unsuccessful forwarding of extension to Mobile Number

    Code:
    09:46:13.917  [CM503008]: Call(255): Call is terminated
    09:46:03.964  [CM503016]: Call(255): Attempt to reach <sip:14@127.0.0.1:5060> failed. Reason: Busy
    09:46:03.964  [CM303006]: There's no outbound rule for external number '(***)***-****' defined
    09:46:03.964  [CM303006]: There's no outbound rule for external number '(***)***-****' defined
    09:46:03.964  [CM503010]: Making route(s) to <sip:14@127.0.0.1:5060>
    09:46:03.964  [CM505003]: Provider:[lax.teliax.com] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [TELIAX GEAR v4.1.0x] PBX contact: [sip:(Username)@192.168.XX.XXX:5060]
    09:46:00.167  [MS211000] C:255.1: 63.211.239.153:18864 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
    09:45:49.886  [CM503007]: Call(255): Device joined: sip:80@127.0.0.1:40600;rinstance=be52aac15800b9a7
    09:45:49.870  [CM503007]: Call(255): Device joined: sip:(Username)@voip-co4.teliax.com:5060
    09:45:49.855  [CM505001]: Ext.80: 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:80@127.0.0.1:5060]
    09:45:49.855  [CM503002]: Call(255): Alerting sip:80@127.0.0.1:40600;rinstance=be52aac15800b9a7
    09:45:49.698  [CM503025]: Call(255): Calling Ext:Ext.80@[Dev:sip:80@127.0.0.1:40600;rinstance=be52aac15800b9a7]
    09:45:49.683  [CM503004]: Call(255): Route 1: Ext:Ext.80@[Dev:sip:80@127.0.0.1:40600;rinstance=be52aac15800b9a7]
    09:45:49.683  [CM503010]: Making route(s) to <sip:80@192.168.XX.XXX:5060>
    09:45:49.667  [CM505003]: Provider:[lax.teliax.com] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [TELIAX GEAR v4.1.0x] PBX contact: [sip:(Username)@192.168.XX.XXX:5060]
    09:45:49.667  [CM503001]: Call(255): Incoming call from (***)***-****@(Ln.10001@lax.teliax.com) to <sip:80@192.168.XXX.XXX:5060>
    
    I added () for the numbers with area codes and - to recognize the numbers easier.
     
  7. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,113
    Likes Received:
    329
    In the working call you are dialling a seven digit number from Ext 14.
    the routing (outbound rule) is then based on that seven digits.

    The outbound rule then, I assume, adds the area code and sends 10 digits to your provider.

    In the failed call, you are trying to route the call based on a 10 digit number.

    So unless you have a second outbound rule(s) to handle 10 digit numbers, you will need to put the seven digit number in the call forward field, just as you are dialling it from ext 14. Or... create additional outbound rules to handle 10 digit dialling, or 11 digit dialling if you use an access digit like a "9".
     
Thread Status:
Not open for further replies.