Introduction

This article describes how an extension or a gateway line registers itself with the PBX Server to make itself available for making and receiving calls, and how the PBX Server will register itself with a VoIP Provider to make itself available for making and receiving calls.

We trace through these steps by reading the server status log. The Server status log can be accessed by going to the 3CX management console and clicking on 3CX Phone System > Server status log.

Scenario 1 – Extension Registration

Log message 1 [CM504001] (all logging levels)

Ext.100: new contact is registered. Contact(s): [sip:[email protected]:50386;rinstance=aa14540e328cb432]

3CX Phone System has received a registration request from a device as Ext.100, and has accepted the request because the credentials match. Ext.100 has IP address 172.18.130.27, and will be listening for incoming calls from the PBX Server on port 50386.

Log message 2 [CM504002] (all logging levels)

Ext.100: a contact is unregistered. Contact(s): []

3CX Phone System has accepted a removal request from a device previously registered as Ext.100.

Log message 3 [CM102001] (all logging levels)

Authentication failed for SipReq: REGISTER 172.18.130.28 tid=917d3a45e8403958 cseq=REGISTER [email protected]:42464 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

3CX Phone System has received a registration request with invalid credentials. This may happen for one (or more) of the following reasons:

  1. The Extension Number submitted by the registering entity is invalid
  2. The Authentication ID submitted by the registering entity is invalid
  3. The Authentication Password submitted by the registering entity is invalid

Scenario 2 – VoIP Provider Registration

Log message 1 [XXyyyyyy] (all logging levels)

Registered line: L:10004(InPhonex)

3CX Phone System has received confirmation from the VoIP Provider that the registration was successful.

Log message 2 [CM504003] (logging levels medium and verbose)

Sent registration request for 10004@InPhonex

3CX Phone System has sent a registration request to VoIP Provider named “InPhonex” and is awaiting a response.

Log message 3 [CM504004] (logging levels medium and verbose)

Registration succeeded for: 10004@InPhonex

3CX Phone System has received a registration confirmation from the VoIP Provider named “InPhonex”.

Log messages 4 [CM504004] and 5 [CM504007] (all logging levels)

Registration failed for: 10004@InPhonex

Next attempt to register 10004@InPhonex is scheduled in 1 minute

3CX Phone System has received a registration denial from the VoIP Provider named “InPhonex”, and will reattempt registration after 1 minute. This may happen for one (or more) of the following reasons:

  1. The Authentication ID supplied was invalid.
  2. The Authentication Password supplied was invalid.
  3. The VoIP Provider is temporarily unable to satisfy registration requests (possibly because of load or other technical reasons related to the VoIP Providers’ infrastructure)
  4. The account with the Provider has expired
  5. The account with the Provider has insufficient credit

Scenario 3 – Bridge (Slave) Registration

Log message 1 [XXyyyyyy] (all logging levels)

Registered line: L:11000(HeadOffice)

3CX Phone System has received confirmation from the Bridge Master that the registration was successful.

Log message 2 [CM504003] (logging levels medium and verbose)

Sent registration request for 11000@HeadOffice

3CX Phone System has sent a registration request to the Bridge Master named “HeadOffice” and is awaiting a response.

Log message 3 [CM504004] (logging levels medium and verbose)

Registration succeeded for: 11000@HeadOffice

3CX Phone System has received a registration confirmation from the Bridge Master named “HeadOffice”.

Log messages 4 [CM504004] and 5 [CM504007] (all logging levels)

Registration failed for: 11000@HeadOffice

Next attempt to register 11000@HeadOffice is scheduled in 1 minute

3CX Phone System has received a registration denial from the Bridge Master named “HeadOffice”, and will reattempt registration after 1 minute. This may happen for one (or more) of the following reasons:

  1. The Authentication ID supplied was invalid.
  2. The Authentication Password supplied was invalid.
  3. The Bridge Master is temporarily unable to satisfy registration requests (possibly because of load or other technical reasons related to the Bridge Master’s infrastructure.