Feature F-5307 Interworking Diversion and RPID Headers from SIP to SS7 REL gives a user the ability to control and direct SS7 calls through the use of a SIP Application. When configured, the feature interworks the Diversion and Remote-Party-Id (RPID) Headers received from the SIP 4xx-Request/Client Failure, 5xx-Server Failure, or 6xx-Global Failure responses into Redirection Information and Generic Number Information in the SS7 REL message. This feature is supported in the ETSI V2 Variant only. See links below for more information.
When feature is enabled, IMG will map the Diversion Header in SIP failure response message (4xx, 5xx, 6xx) into the SS7 ISUP Redirection Number parameter in the REL message with the following parameter values.
Parameter | Value |
Nature of Address Indicator |
0000100 (International Number) |
Internal Network Number Indicator |
0 (routing to internal network number allowed) |
Numbering Plan Indicator |
001 (ISDN (Telephony) numbering plan (ITU-T Recommendation E.164)) |
Address Signal |
from Diversion Header |
The SIP Remote-Party-ID (RPID) is mapped to the Generic Number as follows
Parameter | Value |
Number Qualifier Indicator |
000001100 (additional calling party number) |
Nature of Address Indicator |
0000100 (international number) |
Number Complete Indicator |
0 (number complete) |
Numbering Plan Indicator |
001 - ISDN (telephony) numbering plan (ITU-T Recommendation E.164) |
Address Presentation Restricted Indicator |
from Remote Party ID header Privacy token. See APRI mapping table below |
Screening Indicator |
from Remote Party ID header Screen token. See Screening Indicator mapping table below |
Address Signal |
from Remote Party ID Header |
APRI |
Privacy |
00 (presentation allowed) |
off, or not present |
01 (presentation restricted) |
full |
Screening Indicator |
Screen |
00 (user provided, not verified) |
no, or not present |
01 (user provided, verified and passed) |
yes |
Note: The APRI and SI in the Generic number are derived from tokens in the Remote-Party-ID Header. The other fields in the Redirection Number and Generic Number are hard-coded and are not configurable
The SIP Diversion Header to Redirection Number interworking is enabled in the 'SIP Headers' object which is configured under the SIP SGP object. The Diversion Header Support field must be set to 'Diversion' for the interworking of the SIP Diversion Header to Redirection Number to function as described above.
The SIP Remote Party ID header to Generic Number interworking is by default always enabled. Any incoming sip 4xx, 5xx, or 6xx responses with the Remote Party ID Header embedded will be interworked into the Generic Number in outgoing REL message.
Verify the following entities are configured before proceeding:
Configure these initial objects before proceeding to the procedure below.
Right click on Profiles object created earlier and select New SIP SGP. A SIP object will appear. Change the ID from the first field to something other than ID:0. ID:0 is the default SIP profile and the SIP isub encoding field cannot be configured within this default object. See SIP Profile 10.5.3 for more information on configuring this object.
Right click on the SIP SGP object just created and select New SIP Headers. A SIP Headers object
will appear. Select 'Diversion'
from Diversion Header Support field drop down menu. See below.
Create an external gateway through the external network element object. This will be the gateway that the IMG will communicate with.
Right click on Dialogic IMG EMS and select New External Network Elements. An External Network Elements pane will appear. No configuration is accomplished in this pane. This pane is a placeholder for multiple Network Elements to be created beneath it. See External Network Elements object for more information.
Right Click on External Network Elements object created and select New External Gateways. An External Gateways pane will appear. again this pane is a placeholder from multiple External Gateways. No configuration is needed. See External Gateways for more information.
Right Click on the External Gateways object and select New External Gateway. A screen like
below will appear.
- Enter a name to identify the gateway that IMG will communicate with.
This is the gateway that has SIP application set up to reject incoming
INVITE with Diversion and Remote-Part-ID Headers.
- Select SIP under the Gateway Signaling Protocol field
- Enter IP Address of the Gateway the IMG will communicate with
- Select the SIP SGP Profile that was created earlier. This profile
has the SIP Headers object configured under it with Diversion Header
Support set to 'Diversion'.
At this point the SIP to SS7 interworking of the Diversion and the RPID headers is configured on the IMG. The next step will be to set up the routing so that the specific channel groups are configured to route to the External Network element configured above. See any of the multiple topics that describe the routing process. The following two links below are a good starting point.
An Overview of Routing on the IMG
A Summary of Routing Configuration Tasks