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.

I can't seem to call out on a Broadvoice line in V5

Discussion in '3CX Phone System - General' started by Ralph, Dec 28, 2007.

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

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    Good morning,

    After much celebration I am able to recieve calls on a BroadVoice line fine on my 3CX V5 server. The line registers fine and most everything looks ok until I attempt to call out on it. When I attempt to call out I get a fast busy signal and the following logs appear:

    08:57:30.196 Call::Terminate [CM503008]: Call(3): Call is terminated
    08:57:30.176 Call::RouteFailed [CM503013]: Call(3): Attempt to reach [sip:xxxxxxx@xxx.xxx.xxx.xxx;user=phone] failed. Reason: Reason Unknown
    08:57:30.176 CallLeg::eek:nFailure [CM503003]: Call(3): Call to sip:xxxxxxx@sip.broadvoice.com has failed; Cause: 400 Bad Request; from IP:147.135.12.221
    08:57:30.066 MediaServerReporting::SetRemoteParty [MS210002] C:3.3:Offer provided. Connection(transcoding mode): xxx.xxx.xxx.xxx:52561(52562)
    08:57:30.006 CallLeg::eek:nFailure [CM503003]: Call(3): Call to sip:xxxxxxx@sip.broadvoice.com has failed; Cause: 400 Bad Request; from IP:147.135.12.221
    08:57:29.605 CallCtrl::eek:nSelectRouteReq [CM503014]: Call(3): Target is not registered: VoIPline:xxxxxxx dialed on (AnyLine@BV1)
    08:57:29.605 Line::Line [CM303003]: There are no available outbound lines on gateway BV1 at this time.
    08:57:29.605 CallCtrl::eek:nSelectRouteReq [CM503014]: Call(3): Target is not registered: VoIPline:xxxxxxx dialed on (AnyLine@BV1)
    08:57:29.605 Line::Line [CM303003]: There are no available outbound lines on gateway BV1 at this time.
    08:57:29.605 MediaServerReporting::SetRemoteParty [MS210002] C:3.2:Offer provided. Connection(transcoding mode): xxx.xxx.xxx.xxx:52559(52560)
    08:57:29.395 MediaServerReporting::SetRemoteParty [MS210000] C:3.1:Offer received. RTP connection: xxx.xxx.xxx.xxx:2224(2225)
    08:57:29.395 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(3): Calling: VoIPline:10000@[Dev:sip:xxxxxxx@sip.broadvoice.com:5060, Dev:sip:xxxxxxx@sip.broadvoice.com:5060]
    08:57:29.365 Extension::printEndpointInfo [CM505001]: Ext.101: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP 330;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [PolycomSoundPointIP-SPIP_330-UA/2.1.1.0037] Transport: [sip:xxx.xxx.xxx.xxx:5060]
    08:57:29.335 CallCtrl::eek:nIncomingCall [CM503001]: Call(3): Incoming call from Ext.101 to [sip:xxxxxxx@xxx.xxx.xxx.xxx;user=phone]
    08:57:10.725 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10000@BV1
    08:57:10.064 ClientRegs::Register [CM504003]: Sent registration request for 10000@BV1

    I noticed in one line for capabilities it has "recvonly". Is that the problem?
    Any ideas?

    Thanks again for all the patience and help.
     
  2. webguyz

    webguyz New Member

    Joined:
    Jul 19, 2007
    Messages:
    126
    Likes Received:
    0
    In your OUTBOUND RULES do you have your extensions listed? xxx-xxx

    Also do you have the proper prefix defined?
     
  3. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    Good morning

    Thanks again,

    I had the extensions set correctly but left the prefix blank.
    Once I added the prefix and then modified the strip digits to remove it later I could make a call. Before with V3.1 I didn't need a prefix. Does V5 require a prefix?

    Thanks again :D
     
  4. webguyz

    webguyz New Member

    Joined:
    Jul 19, 2007
    Messages:
    126
    Likes Received:
    0
    My prefix is blank but I have 0 for Strip Digits. I think the strip digits defaults to 1 which can of course problems if you don't use a prefix as I don't.

    Glad you finally got it working. I think you had inbound Vitelity as well if my memory serves correctly. Took me a while to get that working with DID but if you search the forum you'll find the solution posted under my userid.
     
  5. mccutchen

    Joined:
    Dec 29, 2007
    Messages:
    5
    Likes Received:
    0
    Broadvoice and Outbound Calls

    Can you post your other config items? I am getting the same error with Broadvoice on outbound calls.

    I am also getting the following. Any clues??

    [CM503003]: Call(4): Call to sip:xxxxxxxxxx@sip.broadvoice.com has failed; Cause: 403 Forbidden; from IP:147.135.12.221
     
  6. webguyz

    webguyz New Member

    Joined:
    Jul 19, 2007
    Messages:
    126
    Likes Received:
    0
    My Setting on V5 are:

    Single IP, no NAT, dedicated server
    Broadvoice template used and ALL default settings chosen except:

    registration settings >> Which IP to use in 'Contact' field for registration >> Specified IP: 147.135.12.221:5060 (worked ok with External(Stun resolved) as well)

    In Outbound rules I have my extensions listed xxx-xxx and and since I don't require dialing 9 to get out I have Broadvoice and Strip Digits set to 0 under Route 1

    Here is my call log info if you want to compare it to yours.

    11:07:12.877 Call::Terminate :[CM503008]: Call(15): Call is terminated
    11:06:49.213 CallLeg::eek:nConfirmed :Session 921 of leg C:15.1 is confirmed
    11:06:49.103 CallCtrl::eek:nLegConnected :[CM503007]: Call(15): Device joined: sip:97xxxx2972@sip.broadvoice.com:5060
    11:06:49.083 CallCtrl::eek:nLegConnected :[CM503007]: Call(15): Device joined: sip:505@76.184.178.165:13837
    11:06:49.083 MediaServerReporting::SetRemoteParty :[MS210003] C:15.1:Answer provided. Connection(transcoding mode):206.xxx.118.150:9008(9009)
    11:06:49.083 MediaServerReporting::SetRemoteParty :[MS210001] C:15.2:Answer received. RTP connection: 147.135.12.247:6730(6731)
    11:06:49.083 CallLeg::setRemoteSdp :Remote SDP is set for legC:15.2
    11:06:23.977 Line::printEndpointInfo :[CM505003]: Provider:[Broadvoice] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:206.xxx.118.150:5060]
    11:06:23.977 CallCtrl::eek:nAnsweredCall :[CM503002]: Call(15): Alerting sip:97xxxx2972@sip.broadvoice.com:5060
    11:06:21.784 MediaServerReporting::SetRemoteParty :[MS210002] C:15.2:Offer provided. Connection(transcoding mode): 206.xxx.118.150:9010(9011)
    11:06:21.734 MediaServerReporting::SetRemoteParty :[MS210000] C:15.1:Offer received. RTP connection: 76.184.178.165:16390(16391)
    11:06:21.734 CallCtrl::eek:nSelectRouteReq :[CM503004]: Call(15): Calling: VoIPline:10001@[Dev:sip:97xxxx2972@sip.broadvoice.com:5060, Dev:sip:97xxxx2972@sip.broadvoice.com:5060]
    11:06:21.704 CallCtrl::eek:nSelectRouteReq :[CM503010]: Making route(s) to [sip:170xxxxx256@206.xxx.118.150]
    11:06:21.704 CallLeg::setRemoteSdp :Remote SDP is set for legC:15.1
    11:06:21.704 Extension::printEndpointInfo :[CM505001]: Ext.505: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Linksys/PAP2T-3.1.15(LS)] Transport: [sip:206.xxx.118.150:5060]
    11:06:21.674 CallCtrl::eek:nIncomingCall :[CM503001]: Call(15): Incoming call from Ext.505 to [sip:170xxxxx256@206.xxx.118.150]
    11:06:21.634 CallLeg::eek:nNewCall :[CM500002]: Info on incoming INVITE:
    INVITE sip:170xxxxx256@206.xxx.118.150 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.5:5061;branch=z9hG4bK-fa437274;received=76.184.178.165;rport=13837
    Max-Forwards: 70
    Contact: "Home"[sip:505@76.184.178.165:13837]
    To: [sip:1708636xxxx@206.xxx.118.xxx]
    From: "Home"[sip:505@206.xxx.118.150];tag=35915c6f352f9410o1
    Call-ID: ded2df1b-cf561154@10.0.0.5
    CSeq: 102 INVITE
    Expires: 240
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
    Proxy-Authorization: Digest username="505",realm="3CXPhoneSystem",nonce="12843421581:508bc0f21a7077c86c44ef6ddd9fcc3f",uri="sip:170xxxxx256@206.xxx.118.150",algorithm=MD5,response="bfa999b1858ae07a19346938598e3369"
    Supported: x-sipura
    User-Agent: Linksys/PAP2T-3.1.15(LS)
    Content-Length: 0
     
Thread Status:
Not open for further replies.