Developer Program - OpenScape First Response ESInet/NGCS Solution
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
The components in the OpenScape First Response ESInet/NGCS Solution are implement to be compliant to both the North American (NENA) and European (ETSI/EENA) standards. Projects outside North America and Europe will tend to use the ETSI/EENA standards, so the solution can be deployed anywhere in the world.
All external interfaces provided by the solution will be compliant to the applicable standards. This page will enumerate these interfaces and describe which standards apply. Internal interfaces between solution components provide by Unify/Atos will not be described here.
Contents
- 1 Incoming Emergency Call SIP Interface
- 2 Incoming Emergency Call RTP Interface
- 3 Outgoing Call to PSAP SIP Interface
- 4 Outgoing Call to PSAP RTP Interface
- 5 SIP Event Package Interface
- 6 SIP Location Update Interface
- 7 Dequeue Registration Service Interface
- 8 Bad Actor Service SIP Interface
- 9 Location De-Reference SIP Interface
- 10 Location to Service Translation Interface
- 11 Additional Data Repository Query Interface
Incoming Emergency Call SIP Interface
All emergency calls arriving at the BCF interface to the ESInet are signaled via the Session Initiation Protocol (SIP). In North America, per the NENA standards, calls on this interface are expected to provide links to additional data structures in Call-Info headers, but the solution can handle calls without these links. Per ETSI/EENA standards the inclusion of links to additional data are optional and are only of interest to the PSAP.
The SIP interface to the NGCS solution is compliant with RFC 3261 and to the relevant sections of the NENA i3 document and ETSI TS 103 479.
There have been no changes to this interface in recent versions of the NGCS solution.
