outbound call gets fast busy with Voxitas

Discussion in '3CX Phone System - General' started by rjtx667, Jun 10, 2009.

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

    Joined:
    Nov 14, 2007
    Messages:
    3
    Likes Received:
    0
    I have configured a new 3cx install to use a VoIP Provider (Voxitas)

    Inbound calls work fine, as well as extension to extension, but I am unable to get outbound calls to work.

    I do not think it is a problem with out outbound rule as it appears to be sending a call to Voxitas, but appears to get an error after that.

    Any help is greatly appreciated.

    Ryan

    Here is a copy of some logs:


    23:49:23.807 [CM503008]: Call(46): Call is terminated

    23:49:20.557 [CM505003]: Provider:[Voxitas] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [NetLogic Switch v3.2.3] Transport: [sip:xx.xx.xx.xx:5060]

    23:49:20.557 [CM503002]: Call(46): Alerting sip:sipuser@dal02a.netlogic.net:5060

    23:49:19.135 [CM503024]: Call(46): Calling VoIPline:817xxxxxxx@(Ln.10000@Voxitas)@[Dev:sip:sipuser@dal02a.netlogic.net:5060]

    23:49:18.979 [CM503004]: Call(46): Route 1: VoIPline:817xxxxxxx@(Ln.10000@Voxitas)@[Dev:sip:sipuser@dal02a.netlogic.net:5060]

    23:49:18.979 [CM503010]: Making route(s) to "9817xxxxxxx"<sip:9817xxxxxxx@xx.xx.xx.xx>

    23:49:18.963 [CM505001]: Ext.101: Device info: Device Identified: [Man: Counterpath;Mod: X-Lite;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [X-Lite release 1014k stamp 47051] Transport: [sip:xx.xx.xx.xx:5060]

    23:49:18.947 [CM503001]: Call(46): Incoming call from Ext.101 to "9817xxxxxxx"<sip:9817xxxxxxx@xx.xx.xx.xx>

    23:43:35.868 [CM503008]: Call(45): Call is terminated

    23:43:33.071 [CM505003]: Provider:[Voxitas] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [NetLogic Switch v3.2.3] Transport: [sip:xx.xx.xx.xx:5060]

    23:43:33.071 [CM503002]: Call(45): Alerting sip:sipuser@dal02a.netlogic.net:5060

    23:43:31.665 [CM503024]: Call(45): Calling VoIPline:817xxxxxxx@(Ln.10000@Voxitas)@[Dev:sip:sipuser@dal02a.netlogic.net:5060]

    23:43:31.400 [CM503004]: Call(45): Route 1: VoIPline:817xxxxxxx@(Ln.10000@Voxitas)@[Dev:sip:sipuser@dal02a.netlogic.net:5060]

    23:43:31.384 [CM503010]: Making route(s) to "9817xxxxxxx"<sip:9817xxxxxxx@xx.xx.xx.xx>

    23:43:31.384 [CM505001]: Ext.101: Device info: Device Identified: [Man: Counterpath;Mod: X-Lite;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [X-Lite release 1014k stamp 47051] Transport: [sip:xx.xx.xx.xx:5060]

    23:43:31.368 [CM503001]: Call(45): Incoming call from Ext.101 to "9817xxxxxxx"<sip:9817xxxxxxx@xx.xx.xx.xx>

    23:41:11.931 [CM503008]: Call(44): Call is terminated

    23:41:10.212 [CM505003]: Provider:[Voxitas] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [NetLogic Switch v3.2.3] Transport: [sip:xx.xx.xx.xx:5060]

    23:41:10.212 [CM503002]: Call(44): Alerting sip:sipuser@dal02a.netlogic.net:5060

    23:41:08.697 [CM503024]: Call(44): Calling VoIPline:817xxxxxxx@(Ln.10000@Voxitas)@[Dev:sip:sipname@dal02a.netlogic.net:5060]

    23:41:08.603 [CM503004]: Call(44): Route 1: VoIPline:817xxxxxxx@(Ln.10000@Voxitas)@[Dev:sip:sipnames@dal02a.netlogic.net:5060]

    23:41:08.587 [CM503010]: Making route(s) to "9817xxxxxxx"<sip:9817xxxxxxx2@xx.xx.xx.xx>

    23:41:08.587 [CM505001]: Ext.101: Device info: Device Identified: [Man: Counterpath;Mod: X-Lite;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [X-Lite release 1014k stamp 47051] Transport: [sip:xx.xx.xx.xx:5060]

    23:41:08.572 [CM503001]: Call(44): Incoming call from Ext.101 to "9817xxxxxxx"<sip:9817xxxxxxx@xx.xx.xx.xx>

    23:40:00.197 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:104@xx.xx.xx.xx:52808;user=phone;transport=udp/104]
     
  2. bluetel2

    bluetel2 Member

    Joined:
    Oct 16, 2008
    Messages:
    377
    Likes Received:
    5
    hello.

    do you trie your voip provider with only voip client like xlite.

    test this and if it's don't work, you that a provider problem, if not can you explain your 3cx installation please

    have good day
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    Not sure what the dialing plan is in your area. You are sending an "8" as the first digit. Do they require a "1" or a "0" perhaps?

    Just had a look, it seems Voxitas is in the US so i suspect you have to add a "1' in front of your outgoing digits.
    You can have 3CX do that automatically for you in the outgoing dial rules.
     
  4. rjtx667

    Joined:
    Nov 14, 2007
    Messages:
    3
    Likes Received:
    0
    After trying to login with just the x-lite client I found it could not make an outbound call from that.

    After doing several variations and some googleing I found out that Voxitas uses E.124 numbering which sound be +1xxx-xxx-xxxx

    this did not work, however +11xxx-xxx-xxxx did work.

    So I modified the dial plan to strip the 9 out and prepend a +11.

    I just have to remember to never add a 1 to a long distance number, but otherwise I would have to add a 1 to all outbound calls.

    Thanks for all your help,

    Ryan
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    You could set up a second outgoing rule that would handle calls dialled with a "1" (91XXXXXXXXXX) then you wouldn't have to worry.

    After thinking about that...you'd have to create a rule for each of the other 9 combinations, 92,93,94,95...etc to only strip the 9 and prepend +11. then a rule for 91 to strip 2 digits and prepend with +11. Or you might be able to base it on the length of digits dialled.

    Or, require 91 for any non-local area code, if you are required to dial 10 digits locally, and have a rule for all local numbers beginning with 9+ the first digit of the local area code. Or, 1+ for long distance and 9+ for local.
     
Thread Status:
Not open for further replies.