cant get 3cx to fully register broadvoce

Discussion in '3CX Phone System - General' started by mtaks09, Jan 16, 2010.

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

    Joined:
    Dec 7, 2009
    Messages:
    22
    Likes Received:
    0
    I had the pbx working flawlessly then several days ago the whole thing stopped. it says lines are registered how ever digital receptionist never answers its like its not realy registered. called broadvoice they show it isnt registered. can any one tell me is it my settings got changed some how or was there a new release with bugs. please help
     
  2. mylove4life

    mylove4life New Member

    Joined:
    Jan 7, 2010
    Messages:
    165
    Likes Received:
    0
    I don't think it's your system, I bet it with Broadvoice. Have you checked the logs?
     
  3. mtaks09

    Joined:
    Dec 7, 2009
    Messages:
    22
    Likes Received:
    0
    Broadvoice says must be 3cx
     
  4. yadac123

    Joined:
    Jan 19, 2008
    Messages:
    24
    Likes Received:
    0
    It is broadvoice my friend as it happened to me. They make some changes. All incoming calls that press their number key will generate a tone, it's call DTMF tone. Broadvoice is not sending that tone to your 3cx therefore your digital receptionist time out. To solve this issue you have to add one of their outbound proxy server to your outbound server under sip setting. Once you add that it will solve the problem but doing this will introduce another problem, which I've yet to resolved. See my other post and see if anyone will shed some light on it. :) Keep trying!

    John Ma
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,368
    Likes Received:
    229
    What do the 3CX logs show... A. When 3cx registers with Broadvoice? and.... B. When you receive an incoming call from them?
     
  6. yadac123

    Joined:
    Jan 19, 2008
    Messages:
    24
    Likes Received:
    0
    Thanks

    17:59:24.730 [CM503020]: Normal call termination. Reason: Forbidden
    17:59:24.730 [CM503016]: Call(1): Attempt to reach <sip:93184250@66.209.xxx.xx:5060> failed. Reason: Forbidden
    17:59:24.729 [CM503003]: Call(1): Call to sip:1626318xxxx@sip.broadvoice.com has failed; Cause: 403 Forbidden; from IP:206.15.156.221:5060
    17:59:24.713 [CM503025]: Call(1): Calling VoIPline:1626318xxxx@(Ln.10001@Broadvoice 626478xxxx)@[Dev:sip:626478xxxx@sip.broadvoice.com:5060]
    17:59:24.618 [CM503003]: Call(1): Call to sip:1626318xxxx@sip.broadvoice.com has failed; Cause: 403 Forbidden; from IP:206.15.156.221:5060
    17:59:24.557 [CM503025]: Call(1): Calling VoIPline:1626318xxxx@(Ln.10000@Broadvoice 626478xxxx)@[Dev:sip:626478xxxx@sip.broadvoice.com:5060]
    17:59:24.412 [CM503004]: Call(1): Route 2: VoIPline:1626318xxxx@(Ln.10001@Broadvoice 626478xxxx)@[Dev:sip:626478xxxx@sip.broadvoice.com:5060]
    17:59:24.412 [CM503004]: Call(1): Route 1: VoIPline:1626318xxxx@(Ln.10000@Broadvoice 626478xxxx)@[Dev:sip:626478xxxx@sip.broadvoice.com:5060]
    17:59:24.409 [CM503010]: Making route(s) to <sip:93184250@66.209.xxx.xx:5060>
    17:59:24.408 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 5.0.14439.0] PBX contact: [sip:101@66.209.xxx.xx:5060]
    17:59:24.406 [CM503001]: Call(1): Incoming call from Ext.101 to <sip:93184250@66.209.xxx.xx:5060>
     
Thread Status:
Not open for further replies.