3CX VER 3.1.2434 Vonage works, Broadvoice works sometimes

Discussion in '3CX Phone System - General' started by George.Gyles, Dec 9, 2007.

  1. George.Gyles

    Joined:
    Dec 9, 2007
    Messages:
    3
    Likes Received:
    0
    Hello, this is my first post.

    Here is my setup, DSL modem >Watchguard Firebox III 1000> Cisco 2611XM router> Dell poweredge 1550. Using dynmic NAT. Watchguard connects to DSL via PPOE.

    Vonage works great in and out.
    Broad Voice works some times. when it dosent log shows this
    14:11:23.031 CallConf::Rejected [CM103005] Call(128) is rejected: Bad Request
    14:11:23.031 StratInOut::eek:nCancel [CM104008] Call(128): Call from Ext.1000 to 011390815683974 terminated; cause: 400 Bad Request; from IP:147.135.20.221
    14:11:22.140 CallConf::eek:nIncoming [CM103002] Call(128): Incoming call from 1000 (Ext.1000) to sip:011390815683974@192.168.3.19
    14:11:13.593 CallConf::Rejected [CM103005] Call(127) is rejected: Bad Request
    14:11:13.593 StratInOut::eek:nCancel [CM104008] Call(127): Call from Ext.1001 to 011390815684545 terminated; cause: 400 Bad Request; from IP:147.135.20.221
    14:11:12.734 CallConf::eek:nIncoming [CM103002] Call(127): Incoming call from 1001 (Ext.1001) to sip:011390815684545@192.168.3.19
    14:11:01.921 CallConf::Rejected [CM103005] Call(126) is rejected: Bad Request
    14:11:01.921 StratInOut::eek:nCancel [CM104008] Call(126): Call from Ext.1001 to 011390815684545 terminated; cause: 400 Bad Request; from IP:147.135.20.221
    14:11:01.046 CallConf::eek:nIncoming [CM103002] Call(126): Incoming call from 1001 (Ext.1001) to sip:011390815684545@192.168.3.19
    14:10:56.171 CallConf::Rejected [CM103005] Call(125) is rejected: Bad Request
    14:10:56.171 StratInOut::eek:nCancel [CM104008] Call(125): Call from Ext.1001 to 011390815684545 terminated; cause: 400 Bad Request; from IP:147.135.20.221
    14:10:55.296 CallConf::eek:nIncoming [CM103002] Call(125): Incoming call from 1001 (Ext.1001) to sip:011390815684545@192.168.3.19
    14:10:51.421 CallConf::Rejected [CM103005] Call(124) is rejected: Bad Request
    14:10:51.421 StratInOut::eek:nCancel [CM104008] Call(124): Call from Ext.1001 to 011390815684545 terminated; cause: 400 Bad Request; from IP:147.135.20.221
    14:10:50.656 CallConf::eek:nIncoming [CM103002] Call(124): Incoming call from 1001 (Ext.1001) to sip:011390815684545@192.168.3.19
    14:10:26.156 StratInOut::eek:nHangUp [CM104007] Call(123): Call from Ext.1001 to 011390815684545 has been terminated by Ext.1001; cause: CANCEL; from IP:192.168.3.3
    14:10:23.031 CallConf::eek:nProvisional [CM103003] Call(123): Ln:10001@Broadvoice is ringing
    14:10:18.296 CallConf::eek:nIncoming [CM103002] Call(123): Incoming call from 1001 (Ext.1001) to sip:011390815684545@192.168.3.19

    Thanks for anyhelp.
     
  2. George.Gyles

    Joined:
    Dec 9, 2007
    Messages:
    3
    Likes Received:
    0
    Configured X-lite Ver 3 works great

    Configured X-lite Ver 3 to connecto to Broadvoice account. Works without issue. Softphone is on same network as 3CX server.

    Seems to be a issue with Broadvoice VOIP provider setting in 3CX.

    I have tried lastest release of version Five, same issue with Broadvoice, but Vonage doesnt work. This is why I switched back to version 3.
    Thanks again
     
  3. George.Gyles

    Joined:
    Dec 9, 2007
    Messages:
    3
    Likes Received:
    0
    No replies on this?

    Well I guess it's a good thing this product is free. By the number of issues posted on these fourms, people might want thier money back.
    I guess I will have delete this crap ware and install a BPX solution that works.
     
  4. Mori

    Mori New Member

    Joined:
    Mar 23, 2007
    Messages:
    223
    Likes Received:
    0
    First of all, im sorry to hear you think this is crap.
    Almost everybody else in here finds it to be a genious little piece of software, but still in development though.
    I guess thats why there is so many posts.. People care about it and want to be a part in making it better.

    Please remember that this is a user to user forum with guestapperance by 3cx staff, and not the official 3cx support channel.

    Regarding your problem the log does not tell me that much.
    When you say Broadvoice works sometimes. Does that mean in and outgoing calls with great sound?

    How is your 3cx system otherwise set up. Im thinking about outbound rules, DR and so on..
     
  5. critech

    Joined:
    Dec 19, 2007
    Messages:
    4
    Likes Received:
    0
    Error on outbound calls with Broadvoice: "400 Bad Reque

    I have had the same problem since I installed the 3CX system. I have tried in version 3.1 and version 5 RC2, with the default settings for Broadvoice, and while reconfiguring basically every setting in the system in an effort to get it working. Every outbound call results in the "400 Bad Request" error being returned from Broadvoice's Proxy server. I've also installed an X-Lite phone on the 3CX server and connected it directly to Broadvoice and am able to send/receive calls fine.

    I have an Asterisk PBX connected to the same network, behind the same firewall (Sonicwall TZ170), and my SIP phones (Polycom IP 501, and X-Lite soft phone) work flawlessly when connected to the Asterisk system, which is connected to Broadvoice.

    I've contacted Broadvoice and 3CX support and haven't made any progress as of yet (3 weeks since first contact with them).

    Incoming calls through Broadvoice to the 3CX system work fine, but haven't been able to complete a single outbound call since I've been working with this system for a month now.

    My conclusion is there is some setting in 3CX that has to be configured outside the scope of any of the technical documentation that is provided, in order to get it working with Broadvoice. However, I've re-configured every setting available in the system with no luck at this point.

    Any assistance would be GREATLY appreciated!
     
  6. mccutchen

    Joined:
    Dec 29, 2007
    Messages:
    5
    Likes Received:
    0
    I am getting the same issue with Broadvoice on outbound calls. It works fine sometimes (I placed 3 calls in a row last night with no issues) and then without changing a single config setting, it fails and I get the 400 Bad Request message in the log.

    Anyone been able to resolve this??
     
  7. critech

    Joined:
    Dec 19, 2007
    Messages:
    4
    Likes Received:
    0
    3CX and Broadvoice Error on outbound calls "400 bad req

    Discovered the problem boils down to our Internet firewall, which is a Sonicwall TZ170. I would imagine others experiencing similar problems have higher-end firewalls like ours that have to have some special configuration to make it work properly. It is doing something to the packets between the 3CX system and Broadvoice which is causing the outbound calling problem, and a couple other problems related to inbound calls not being connected and disconnected properly.

    We've analyzed packets on the LAN and WAN side of the firewall and it looks like there may be some packet coming from Broadvoice in the initial setup of an outbound call which is requesting authentication from 3CX, but the packet doesn't make it back through the firewall to the 3CX system, so the 3CX system doesn't know to authenticate first and tries to dial out without authenticating.

    I replaced the Sonicwall with a basic Linksys residential router and all the problems went away.The 3CX system works GREAT now! The odd thing is, the Asterisk system I’ve been using is also behind the Sonicwall firewall and it hasn’t had any problems when using it with Broadvoice. There is obviously something different about the packets being transmitted from 3CX that is not getting translated properly through the Sonicwall, which doesn’t seem to be a problem with Asterisk.

    It looks like Asterisk just sends the authentication credentials up front during the initial setup of the outbound call, and doesn't need Broadvoice to request authentication first; so Asterisk isn't hindered by the firewall.

    We are replacing our Sonicwall with another router/firewall for now, but will continue to try to figure out what the actual problem is and how to resolve it with the Sonicwall router. We have used Sonicwall routers for years, and many of our clients use them as well because we have had great success with them…so hopefully we can figure out how to make it work with 3CX.

    I intend to find a solution (at least for Sonicwall devices) and Will post as I have time to examine it further...but for now I'm enjoying our 3CX PBX working FLAWLESSLY connected to Broadvoice through a $50 Linksys router.

    What firewalls/routers are everyone else's 3CX systems behind who are connecting to Broadvoice???
     

Share This Page