The ISDN calling party subaddress parameters convey address information of each device in ISDN network. The ISDN Calling Party subaddress can now be interworked into the SIP protocol using the isub and isub encoding parameters. By interworking these two parameters, the ISDN calling Party Subaddresses as well as its encoding type can be passed between ISDN and SIP as well as SIP and ISDN. Below is more information pertaining to the interworking of these parameters.
The interworking of the Calling Party subaddress was introduced in software 10.5.3_ER1. Starting in software version 10.5.3 SP4 the ISDN Called Party subaddress information will also be interworked between the SIP and ISDN protocols. Refer to the Call Flow diagrams below.
SIP |
ISDN |
||
isub= |
isub-encoding= |
type of subaddress |
subaddress info |
12345 |
nsap-ia5 |
nsap |
0x [50 31 32 33 34 35] |
12345 |
nsap-bcd |
nsap |
0x [48 12 34 50] (oei=1) |
123450 |
nsap-bcd |
nsap |
0x [48 12 34 50] (oei=0) |
3132333435 |
nsap |
nsap |
0x[31 32 33 34 35] |
12345 |
|
nsap |
0x[50 31 32 33 34 35] |
1a2b3c4d5e6f |
user |
user specified |
0x[1a 2b 3c 4d 5e 6f] |
12345 |
anything else |
*N/A |
*N/A |
*N/A - ISDN will not send calling party address.
nsap-ia5 - Indication that the “isub” parameter value needs to be encoded using IA5 (AFI = 0x50) when translated to an ISUP message
nsap-bcd - Indication that the “isub” parameter value needs to be encoded using Binary Coded Decimal (BCD) (AFI=0x48)
nsap - Indication that the “isub” parameter value needs to be encoded using the encoding type defined in ISO 8328 other than IA5 (AFI = 0x50) or BCD (AFI=0x48).
ISDN |
SIP |
||
type of subaddress |
subaddress info |
isub= |
isub-encoding= |
nsap |
0x[50 31 32 33 34 35] |
12345 |
nsap-ia5 |
nsap |
0x [48 12 34 50] (oei=1) |
12345 |
nsap-bcd |
nsap |
0x [48 12 34 50] (oei=0) |
123450 |
nsap-bcd |
nsap |
0x[31 32 33 34 35] |
3132333435 |
nsap |
user specified |
0x[1a 2b 3c 4d 5e 6f] |
1a2b3c4d5e6f |
user |
anything else |
12345 |
**N/A |
**N/A |
**N/A - Outgoing SIP will not include 'isub' and 'isub encoding' parameters.
SIP to ISDN Calling Party (isub enabled)
ISDN to SIP Calling Party (isub enabled)
SIP to ISDN Called Party (isub enabled)
ISDN to SIP Called Party (isub enabled)
The isub encoding parameter is a field added to the SIP From Header Tags object. The From Header Tags object is configured under the SIP SGP object and is eventually inserted into a external network element object. Below are instructions on how to configure the isub encoding parameter for interworking between ISDN and SIP. Verify the following entities are configured before proceeding:
Configure these initial objects before proceeding to the procedure below.
When configuring the IMG to interwork the Calling and Called Party Subaddresses the configuration of the SIP SGP object differs when configuring the Called Party Subaddress as opposed to the Calling Party Subaddress. The next two sections below describe the process for each subaddress.
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.2 or SIP Profile 10.5.3 for more information on configuring this object.
The ISUB encoding field will now be populated with the isub/isub-encoding selection.
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
using ISUB Encoding
- 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 ISUB Encoding configured in it.
At this point the Isub Encoding interworking 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 from ISDN 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