Manual Registration

From Pbxnsip Wiki

When a SIP user agent registers itself on the PBX, the PBX adds a contact to the list for that extension. Whenever it needs to call the extension or perform other tasks like sending out messages, it will use that list to send out SIP packets in parallel.

The term "static registration" and "manual registration" are used for the same form of registration.

Types

There are three types of contacts.

• The first type is the regular registration from a SIP user agent that is registering from an address that can be reached directly from the PBX. These addresses are typically addresses in the same LAN or addresses on public Internet. Most IPv6 addresses are routable.

• If the phone is using an address that is not routable, the PBX uses the second type of registration. It will still keep the presented address in the registration database, but it will remember where the request came from and then send the request to that location.

• The third type is a static registration that has been added manually. The address must be routable according to the rules of RFC3262. Static registrations do not expire - you must delete them manually by removing all contacts for the extension.

HTTP Registrations

The PBX also supports different schemes that "sip". If you enter a HTTP URL and the type is "dialog", then the PBX will send out dialog state notifications by SOAP requests (see Dialog State Notifications for more information on that topic). When you add a new http static registration, the PBX will automatically assign the type "dialog" to it (starting in version 3.1).

Examples

The following examples how you can use the static registration.

• If you want to include a PSTN number in every call to a specific extension, you can include a contact like "sip:19781234567@192.168.1.2;user=phone" (19781234567 would be the telephone number and 192.168.1.2 would be the IP address of the PSTN gateway). This method would not only include calls that go directly to an extension, but also calls where the extension is part of a hunt or agent group.

• You can use DNS names to specify the destination, for example "sip:19781234567@pstngw.domain.com;user=phone". According to the RFC, the PBX will try to resolve the transport layer using DNS SRV records. If you don’t want that, you can specify the port number behind the DNS name, in this case the PBX will use UDP transport layer.

• You can also specify the transport layer explicitly like in "sip: sip:19781234567@192.168.1.2;user=phone;transport=tls". The PBX supports the trasnsport layers udp, tcp and tls.

You can include any parameters in the contact as you like. For example, the parameter "line" is sometimes used as a security mechanism to protect denial of service attacks to the user agent.