Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Originating Line Info Support

The Originating Line Information parameter (also know as II digits) conveys information about the originator of a call. This information gets lost over SIP networks if not inter-worked properly. The OLI feature allows carrying the ANSI ISUP OLI Parameter from traditional TDM networks into SIP and vice versa.

Call Flow Diagrams

SS7 to SIP

The call flow below displays the IMG 2020 receiving a call setup IAM request from the PSTN/SS7 with the Originating Line Information Parameter = 0. With the ISUP-OLI feature enabled, the ISUP-OLI parameter will appear in the From: header of the INVITE request.

SIP to SS7

The call flow below displays the IMG 2020 receiving an INVITE with the From Header containing the ‘ISUP-OLI’ tag. With the ISUP-OLI feature, the IMG 2020 will send a call setup request to the PSTN/SS7 with the OLI parameter.

SIP to ISDN (ISUP-OLI Enabled)

A SIP INVITE message with ISUP-OLI parameters in the From: Header is received. The IMG 2020 will inter-work the parameter into the ISDN SETUP message with 'lock shift codeset6' IE followed by the ISUP-OLI parameter. See Call Flow diagram below.

ISDN to SIP (ISUP-OLI Enabled)

An ISDN SETUP message which contains 'lock shift codeset6' IE followed by ISUP-OLI information is received. The message is inter-worked and inserted into the From: Header in the SIP INVITE message. See Call Flow diagram below.

SIP to ISDN (ISUP-OLI Disabled)

When ISUP-OLI is set to disabled the IMG 2020 will follow its current behavior. See Call Flow diagrams below.

ISDN to SIP (ISUP-OLI Disabled)

When ISUP-OLI is set to disabled the IMG 2020 will follow its current behavior. See Call Flow diagrams below.

Call Trace Examples

From: “Anonymous”<sip:+18182625511@10.10.10.10;isup-oli=00>;tag=95ffcd055e0f78f7d5d397020e89288d63d4

Click on links below to display Call Trace

 Call Trace - OLI SIP-ISDN

Call Trace - OLI ISDN-SIP

Sample OLI Values

OLI Value

OLI Description

 

OLI Value

OLI Description

 

OLI Value

OLI Description

00

pots

 

25

800 service call from a pay station

 

61

wireless/cellular PCS (type 1)

01

multiparty line

 

27

payphone using coin control signaling

 

62

wireless/cellular PCS (type 2)

02

ANI failure

 

29

prison/inmate service

 

63

wireless/cellular PCS (roaming)

06

Station Level Rating

 

30

intercept (blank)

 

66

TRS call from hotel

07

special operator handling required

 

31

intercept (trouble)

 

67

TRS call from restricted line

08

inter-LATA restricted

 

32

intercept (regular)

 

68

inter-LATA restricted hotel

10

test call

 

34

telco operator handled call

 

70

inter-LATA restricted coin-less

20

AIOD-listed DN sent

 

36

CPE

 

78

private pay-stations

23

coin or non-coin on calls using database access

 

52

OUTWATS

 

93

private virtual network

24

800 service call

 

60

TRS call from unrestricted line

 

 

 


Configuration

Initial Configuration

The OLI parameter is configured in the SIP Profile object and is then inserted into a external network element object. Below are instructions on how to configure the OLI parameter. The procedure below explains how to configure the IMG 2020 to insert/map the OLI value between ISDN and SIP. Before configuring, the IMG 2020 must have an initial configuration created on it. Follow the Basic Configurations procedure before proceeding. 

Create SIP Profile (SGP) and enable OLI

Configure a SIP Profile that allows a Notify message to be sent without a Subscribe message.

  • Create a SIP Profile. Right click on the Dialogic object and select New Profiles. The Profiles object is a parent or container object and no configuration is needed here.

  • Right click on the Profiles object and select New SIP Profile. The first profile that gets created is a Default SIP Profile and cannot be modified. Disregard this profile.

  • Right click on the Profiles object just created again and select New SIP Profile. Either enter a Name into the name field that identifies this profile or accept the default entry. Refer to the  SIP Profile - SGP topic for more information on configuring each of the individual fields.

  • Right click on the SIP Profile object just created and select New SIP from Header Tags. Enable the SIP OLI feature by selecting Enable from the drop down menu in the ISUP OLI field. Refer to the topic for more information on configuring each of the individual fields.SIP Profile - From Header Tags

Create SIP signaling stack

  • Right click on the IMG 2020 physical node and select New Signaling.  The Signaling object is a parent or container object and no configuration is needed here. Refer to the Signaling topic for more information on this object.

  • Right click on the Signaling object created and select New SIP. In the IP Address field, select from the drop down menu which IP address will be used for SIP signaling. Refer to IMG 1010 - SIP Signaling Object topic for more information.

Create SIP Channel Groups

  • Right click on the Dialogic object and select New Routing Configuration. The Routing Configuration object is a parent or container object and no configuration is needed here. Refer to the Routing Configuration topic for more information.

  • Right click on Routing Configuration and select New Channel Groups. The Channel Groups object is a container object also and no configuration is needed. Refer to the Channel Groups topic for more information.

  • Right click on Channel Groups object and select New Channel Group. Either enter a name that identifies this channel group or accept the default entry. In this example the Channel Group was labeled SIP_OLI_ChGrp.

  • Select SIP from the drop down menu of the Signaling Type field. Refer to the Channel Group topic for more information on configuring this object.

Create an External Gateway

The SIP Channel group needs to communicate with an external SIP entity. Create an external network element and then an external gateway that the SIP channel group will transmit messages to. Follow procedure below to communicate with a remote gateway.

  • Right click on the Dialogic object and select New External Network Elements. The External Network Elements object is a parent or container object and no configuration is needed here. Refer to External Network Elements topic for more information.

  • Right click on External Network Elements and select New External Gateways. The External Gateways object is a parent or container object also and no configuration is needed here. Refer to External Gateways for more information.

  • Right click on External Gateways and select New External Gateway. Enter a name that identifies the gateway being configured. In this example the gateway was labeled SIP_OLI_GW

 

  • Select SIP from drop down menu in the Protocol field.

  • Enter IP Address of the Gateway the IMG 2020 will communicate with.

  • Select the SIP Profile that was created earlier. This profile has the ISUP-OLI configured in it.

For more information refer to the External Gateway topic. 

Insert SIP External Network Element into SIP Channel Group

  • Right Click on the SIP Channel group created and select New IP Network Element. Within the IP Network Element field, select from drop down menu, the gateway created. See screen capture below.

  • Click on the Channel Groups object again. The Channel Groups object will have a yellow exclamation point in place of the icon indicating the configuration has not been sent to the IMG 2020. Click on the Download Resource Tables button and the new configuration will be sent to the IMG 2020.

  • At this point, the SIP OLI feature has been configured.

  • No labels

Return to Documentation Home I Return to Sangoma Support