BroadVoice line won't register

Discussion in '3CX Phone System - General' started by Ralph, Jun 30, 2007.

  1. Ralph

    Ralph Member

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

    I followed the instructions in the manual to set up a VOIP line with BroadVoice. The BroadVoice line will not register.

    I have a BroadVoice account and can log into it ok etc.
    I have another linethrough Vitelity that works fine.
    I set up the line using the BroadVoice template.
    I have deleted that line and set up the line using the generic template with the same results.
    I have also restarted the server.

    Here are some of the log entries:

    18:49:25.000 ClientRegs::eek:nFailure [CM113010] Next registration will be attempted in 10 minutes
    18:49:25.000 ClientRegs::eek:nFailure [CM113006] Registration of sip:5092410197@sip.broadvoice.com has failed; reason=Service Unavailable
    18:49:24.875 ExtLine::Register [CM110004] Send registration for <sip:5092410197@sip.broadvoice.com>
    18:49:24.875 ExtLine::Register [CM110001] Use External IP for device line registration DN='10001' device='BroadVoice 1'
    18:39:24.718 ClientRegs::eek:nFailure [CM113010] Next registration will be attempted in 10 minutes
    18:39:24.718 ClientRegs::eek:nFailure [CM113006] Registration of sip:5092410197@sip.broadvoice.com has failed; reason=Service Unavailable
    18:39:24.328 ExtLine::Register [CM110004] Send registration for <sip:5092410197@sip.broadvoice.com>

    I'm sure it is probably somthing basic that I am overlooking. Any help would be greatly apprciated.

    Thanks again,
     
  2. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,677
    Likes Received:
    18
    Have you checked that the server name details apply for your account, i.e maybe they gave you a different SIP server/registrar name? Did you check authentication details? Did you retry an hour later or so? Since the error says that the provider did not respond. Could it be it was temporarily down?
     

Share This Page