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.

Broadvoice outbound proxy?

Discussion in '3CX Phone System - General' started by mutti_wilson, May 9, 2008.

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

    May 2, 2008
    Likes Received:
    I talked to Broadvoice and they said that 3CX does not work with anything other than the default server "sip.broadvoice.com". I did a traceroute on sip.broadvoice.com and proxy.lax.broadvoice.com (which does register) and the number of hops is less than half. 10 vs. 21. My ping to lax is 70ms and to boston is 150ms.

    The problem is i cannot make outgoing calls if i select the lax proxy. Is there a way around this so i dont have to bounce all the way across the country and pick up latency along the way.

    With a ping of 150ms should i be encountering much latency or delay in conversation? I notice some now and im wondering if thats because of so many hops.

    Here is my log when i try to make a phone call.

    15:29:43.371 StunClient::eek:nInitTests [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server over Transport
    15:29:42.633 Call::Terminate [CM503008]: Call(18): Call is terminated
    15:29:42.614 Call::RouteFailed [CM503014]: Call(18): Attempt to reach "6357421"[sip:6357421@] failed. Reason: Forbidden
    15:29:42.613 CallLeg::eek:nFailure [CM503003]: Call(18): Call to sip:3606357421@sip.broadvoice.com has failed; Cause: 403 Forbidden; from IP:
    15:29:41.860 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(18): Calling: VoIPline:10001@[Dev:sip:3608431066@sip.broadvoice.com:5060]
    15:29:41.832 CallCtrl::eek:nIncomingCall [CM503001]: Call(18): Incoming call from Ext.100 to "6357421"[sip:6357421@]
Thread Status:
Not open for further replies.