Host Notification of Selective SIP Header Information
With this feature, the CSP can send selective SIP header data to the host application in the Request For Service with Data message and, if required, in the PPL Event Indication message. The Call-ID header information allows the host application to uniquely identify the call with other elements in the SIP network.
Important! You should disable all additional SIP header notification if calls are being internally routed without host application intervention.
The process works as follows:
1. The host application specifies what additional fields from the SIP message header that it wants to see in the Request For Service with Data message.
2. You specify the fields in the 0x027F SIP Message Information Mask in the VoIP Protocol Configure message.
3. If the CSP can fit all of the data in the Request For Service with Data message, it does so. (The data is formatted in the NPDI TLVs listed below these steps.)
4. If the size exceeds the maximum size that the CSP allows (320 bytes of NPDI data), the CSP sends the following:
• the Request For Service with Data message with NPDI data (not to exceed 320 bytes) including the Subsequent Info Status 0x2953 TLV indicating that there is more data to follow.
• The CSP sends "n number" of PPL Event Indications messages where each indication would carry NPDI data (not to exceed 320 bytes) including the Subsequent Info Status 0x2953 TLV
5. If the CSP sends the data in multiple messages (Request for Service and subsequent PPL Event Indication) the CSP adds the Subsequent Info Status 0x2953 TLV. This TLV indicates the sequence number of the message and whether it is the last message in the sequence.
6. If the data has to go into an API message, and not into TLVs, the call is rejected with the "500 Internal Server Error" response.
API Messages Used
• Request For Service with Data (0x002D)
• PPL Event Indications (0x0043)