Understanding Integrated Convergence Services SIP Trunk Support for Separate Registrar and Peer Proxy Server Components

This topic describes the Integrated Convergence Services SRX Series SIP trunk feature, which allows you to configure a SIP trunk to support separate registrar and peer proxy server components.

By default, the SIP trunk configuration for a peer proxy server is premised on the fact that the call server and the registrar are managed by the same entity. To support these functions as a single entity in a SIP network, the SRX Series media gateway (SRX Series MGW) sends both REGISTER and INVITE messages to the address configured for the peer proxy server.

For some SIP network environments, the registrar and the peer proxy server are separate entities. For this type of SIP network configuration, you can specify separate addresses for the registrar and the peer proxy server. In this case, INVITE messages are sent to the peer proxy server, and REGISTER messages are sent to the registrar. If you do not configure a registrar address, the default behavior takes effect.

This feature applies to both UDP and TCP networks.

Related Topics

• Example: Configuring Integrated Convergence Services Support for Separate Registrar and Peer Call Server Functions