Broadvoice - Has anyone gotten outbound calls working on it?

Discussion in '3CX Phone System - General' started by dvs4man, Nov 23, 2009.

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

    Joined:
    Oct 5, 2009
    Messages:
    50
    Likes Received:
    0
    I have Broadvoice with my A580IP Siemens phone. All works well for incoming calls, but outgoing calls I get the 403 Forbidden error from the sip.broadvoice.com. I have ports 69-30000 open through my router, and I do have GREEN for the Trunks status. It is only calling out that I have this issue.

    I do see though that my STUN Server I am using ALWAYS times out. Not sure if that is part and parcel of the problem. I had left it set to the stu2 3cx STUN server, and tried others though, with the same results, always timing out.

    The logs, I have uploaded into another message, but I will cut/paste below.

    Any help is appreciated. Please feel free to PM me or reply back here.

    Thanks.

    21:20:04.201 [CM503008]: Call(6): Call is terminated
    21:19:59.145 Session 4619 of leg C:6.1 is confirmed
    21:19:59.059 [CM503007]: Call(6): Device joined: sip:EndCall@127.0.0.1:40600;rinstance=a2b37f4c796f0b1b
    21:19:59.052 [CM503007]: Call(6): Device joined: sip:10@192.168.0.198:5060
    21:19:59.048 [MS210005] C:6.1:Answer provided. Connection(proxy mode):192.168.0.168:7018(7019)
    21:19:59.045 [MS210001] C:6.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40618(40619)
    21:19:59.042 Remote SDP is set for legC:6.2
    21:19:59.032 [CM503002]: Call(6): Alerting sip:EndCall@127.0.0.1:40600;rinstance=a2b37f4c796f0b1b
    21:19:58.894 [CM503025]: Call(6): Calling Unknown:Ext.EndCall@[Dev:sip:EndCall@127.0.0.1:40600;rinstance=a2b37f4c796f0b1b]
    21:19:58.891 [MS210004] C:6.2:Offer provided. Connection(proxy mode): 127.0.0.1:7020(7021)
    21:19:58.844 [CM503016]: Call(6): Attempt to reach <sip:nnnnnnnnnnn@192.168.0.168> failed. Reason: Not Found
    21:19:58.843 [CM503014]: Call(6): No known route to target: <sip:nnnnnnnnnnn@192.168.0.168>
    21:19:58.834 [CM503010]: Making route(s) to <sip:nnnnnnnnnnn@192.168.0.168>
    21:19:58.833 [MS210000] C:6.1:Offer received. RTP connection: 192.168.0.199:5016(5017)
    21:19:58.832 Remote SDP is set for legC:6.1
    21:19:58.831 [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Aastra MBU/01.30 (MAC=00087B0753C8; HW=7)] PBX contact: [sip:10@192.168.0.168:5060]
    21:19:58.820 [CM503001]: Call(6): Incoming call from Ext.10 to <sip:nnnnnnnnnnn@192.168.0.168>
    21:19:58.813 [CM500002]: Info on incoming INVITE:
    INVITE sip:nnnnnnnnnnn@192.168.0.168 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.198;branch=z9hG4bKci51geef7;received=192.168.0.199
    Max-Forwards: 70
    Contact: <sip:10@192.168.0.198>
    21:19:32.875 [CM504004]: Registration succeeded for: 10001@broadvoice
    21:19:32.346 [CM504003]: Sent registration request for 10001@broadvoice
     
  2. dvs4man

    Joined:
    Oct 5, 2009
    Messages:
    50
    Likes Received:
    0
    I have setup a 'callcentric' provider test, and they work flawlessly.
    Curious what is different with Broadvoice?

    If anyone can help, it is much appreciated, since Broadvoice is the only one who can port our phone number. All the other supported providers cannot.

    Below is a copy of the log of callcentric successful calls, and even the STUN server failing issues.

    Thanks.

    06:35:13.242 [CM503008]: Call(4): Call is terminated
    06:34:48.707 [CM503007]: Call(4): Device joined: sip:{mycallcentricnumber}@callcentric.com:5060
    06:34:48.683 [CM503007]: Call(4): Device joined: sip:10@192.168.0.188:5060
    06:34:33.648 [CM505003]: Provider:[callcentric] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:{mycallcentricnumber}@71.193.85.142:5060]
    06:34:33.647 [CM503002]: Call(4): Alerting sip:{mycallcentricnumber}@callcentric.com:5060
    06:34:31.569 [CM503025]: Call(4): Calling VoIPline:{callingtothatnumber}@(Ln.10001@callcentric)@[Dev:sip:{mycallcentricnumber}@callcentric.com:5060]
    06:34:31.411 [CM503004]: Call(4): Route 1: VoIPline:{callingtothatnumber}@(Ln.10001@callcentric)@[Dev:sip:{mycallcentricnumber}@callcentric.com:5060]
    06:34:31.408 [CM503010]: Making route(s) to <sip:{callingtothatnumber}@192.168.0.198;user=phone>
    06:34:31.406 [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [A580 IP022140000000] PBX contact: [sip:10@192.168.0.198:5060]
    06:34:31.393 [CM503001]: Call(4): Incoming call from Ext.10 to <sip:{callingtothatnumber}@192.168.0.198;user=phone>
    06:34:17.162 [CM503003]: Call(3): Call to sip:{callingtothatnumber}@66.193.176.35 has failed; Cause: 487 Request Terminated; from IP:204.11.192.38:5060
    06:34:16.995 [CM503008]: Call(3): Call is terminated
    06:34:16.070 [CM505003]: Provider:[callcentric] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:{mycallcentricnumber}@71.193.85.142:5060]
    06:34:16.070 [CM503002]: Call(3): Alerting sip:{mycallcentricnumber}@callcentric.com:5060
    06:34:12.364 [CM503025]: Call(3): Calling VoIPline:{callingtothatnumber}@(Ln.10001@callcentric)@[Dev:sip:{mycallcentricnumber}@callcentric.com:5060]
    06:34:12.139 [CM503004]: Call(3): Route 1: VoIPline:{callingtothatnumber}@(Ln.10001@callcentric)@[Dev:sip:{mycallcentricnumber}@callcentric.com:5060]
    06:34:12.136 [CM503010]: Making route(s) to <sip:{callingtothatnumber}@192.168.0.198;user=phone>
    06:34:12.131 [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [A580 IP022140000000] PBX contact: [sip:10@192.168.0.198:5060]
    06:34:12.115 [CM503001]: Call(3): Incoming call from Ext.10 to <sip:{callingtothatnumber}@192.168.0.198;user=phone>
    06:33:20.792 [CM503003]: Call(2): Call to sip:{callingtothatnumber}@66.193.176.35 has failed; Cause: 487 Request Terminated; from IP:204.11.192.38:5060
    06:33:20.625 [CM503008]: Call(2): Call is terminated
    06:33:13.776 [CM505003]: Provider:[callcentric] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:{mycallcentricnumber}@71.193.85.142:5060]
    06:33:13.775 [CM503002]: Call(2): Alerting sip:{mycallcentricnumber}@callcentric.com:5060
    06:33:09.648 [CM503025]: Call(2): Calling VoIPline:{callingtothatnumber}@(Ln.10001@callcentric)@[Dev:sip:{mycallcentricnumber}@callcentric.com:5060]
    06:33:09.382 [CM503004]: Call(2): Route 1: VoIPline:{callingtothatnumber}@(Ln.10001@callcentric)@[Dev:sip:{mycallcentricnumber}@callcentric.com:5060]
    06:33:09.380 [CM503010]: Making route(s) to <sip:{callingtothatnumber}@192.168.0.198;user=phone>
    06:33:09.378 [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [A580 IP022140000000] PBX contact: [sip:10@192.168.0.198:5060]
    06:33:09.361 [CM503001]: Call(2): Incoming call from Ext.10 to <sip:{callingtothatnumber}@192.168.0.198;user=phone>
    05:12:04.279 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.198:5060
    01:52:01.785 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.198:5060
    22:31:59.221 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.198:5060
     
  3. dvs4man

    Joined:
    Oct 5, 2009
    Messages:
    50
    Likes Received:
    0
    Broadvoice had issues on their end. I was on with a technician, and now it is working fine.
    Thanks.
     
  4. yadac123

    Joined:
    Jan 19, 2008
    Messages:
    24
    Likes Received:
    0
    Re: Broadvoice - Has anyone gotten outbound calls working on

    can you share with me what he did?

    John Ma
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,365
    Likes Received:
    227
    Re: Broadvoice - Has anyone gotten outbound calls working on

    This would seem to indicate that your outbound rules don't know how to handle the digits that you are dialling.
     
  6. yadac123

    Joined:
    Jan 19, 2008
    Messages:
    24
    Likes Received:
    0
    Re: Broadvoice - Has anyone gotten outbound calls working on

    I really need help solving the 403 forbidden error. If anyone know please post it. Many thanks.

    John Ma
     
Thread Status:
Not open for further replies.