OXE Duplication

In case of OXE duplication, the SIPMOTOR is completely started on the Stand-By CPU, but acting as Stand-By(cannot handle the SIP requests). The Main CPU puts the Stand-By CPU up to date about the SIP contexts (Calls,registrations, subscriptions, etc...). In case of CPU switchover, the SIP calls are maintained and the registration andsubscriptions are kept.

In Case of spatial redundancy with dual subnetworks (2 main IP addresses), the SIP uses the FQDN of the OXE(nodename + DNS local domain name) for the SIP messages and also for the responses of the SIP messages. In thatcase, the remote SIP equipment must use it. The use of external DNS server is recommended to resolve this FQDN

The OXE contains the following compoments:

Registrar

Registers the SIP terminals addresses (“Location Service”)

·       The REGISTRAR is contained in the “localize.sip” file under /tmpd. If for any reasons you need to clear allentries in the registrar database, remove this file and then restart the SIPMOTOR:

(1)OXE> rm /tmpd/localize.sip

(1)OXE> dhs3_init -R SIPMOTOR

Proxy

Entity between the Client and the Server, the proxy is used to route the SIP requests.

·       The call can be routed between 2 SIP terminals. For instance, if Alice calls Bob (both are SIP), Alice sends a SIP request to the proxy, and the proxy sends this request to Bob.

·       The proxy can be used only for the authentication of the SIP equipment for Registration or SIP request.

o   The proxy can modify the request by adding information like a Via, Record-route, etc...

The INVITE is the same on each proxy sides, to get this behavior, and the UAC manages the IP address of the OXE SIP  proxy as the “Outbound proxy”

Here is an example:

·              UAC IP address: 172.27.143.184

·              proxy IP address: 172.27.143.186

·             UAS FQDN: oxe-ov.alcatel.fr (IP address: 172.27.141.151)