IMG 1010 - UUI Support - Overview

The IMG supports sending UUI (User to User Information) between called and calling parties. The purpose of the User to User Information support is to pass specific information not pertaining to the call from one user to another. The information can be passed during the following phases of a call.

• Setup and Clearing Phase- UUI message is embedded in the ISUP call control message.

• Setup Phase of the Call- UUI message transferred independently of Call Control Messages and sent through the ISUP Information message.

• Active Phase of the Call- UUI message sent through ISUP User Info message during the call

The information is transferred transparently through the network and does not have any effect on the call. The IMG supports UUI for multiple protocols and variants. Below is a list of the supported protocols:

• Between ISDN and ISDN    (ISDN supports EURO, JATE, and NI2)

• Between ISDN and SS7

• Between ISDN and SIP

• Between ISDN and H.323

• Between SS7 and SS7

• Between SS7 and SIP

Basic Call Flows with UUI Enabled

Below are Basic Call Flows when UUI Support is enabled. Not all scenarios are displayed below. Typically any message that is propagated from end to end is supported. Below are a few scenarios.

Between SS7 and SS7

IAM to IAM- The User to User data is initially received in the incoming SS7 IAM message. It is then propagated to the outbound SS7 network using the SS7 IAM message.

ANM to ANM- The User to User data is initially received in the incoming ANM message. It is then propagated to the SS7 side and transmitted out using the SS7 IAM message.

SAM to IAM- The User to User data is initially received in the incoming SS7 SAM message. It is then propagated to the outbound SS7 network using the SS7 IAM message.

REL to REL- The User to User data is initially received in the incoming SS7 REL message. It is then propagated to the outbound SS7 network using the SS7 REL message.

Between ISDN and SS7

IAM to IAM- The User to User data is initially received in the incoming SS7 IAM message. It is then propagated to the outbound SS7 network using the SS7 IAM message.

ACM to ALERTING- The User to User data is initially received in the incoming SS7 ACM message. It is then propagated to the outbound ISDN network using the ALERTING message.

ANM to CONNECT- The User to User data is initially received in the incoming SS7 ANM message. It is then propagated to the outbound ISDN network using the CONNECT message.

Between ISDN and SIP

SETUP to INVITE- The User to User Data is received in the ISDN SETUP message. It is then propagated to the outbound SIP network using the SIP INVITE.

ALERTING to 1xx- The User to User Data is received in the ISDN ALERTING message. It is then propagated to the SIP network using the 1xx informational Response message.

CONNECT to 200 OK- The User to User Data is received in the ISDN CONNECT message. It is then propagated to the outbound SIP network using the 200 OK Successful response.

DISCONNECT to BYE- The User to User Data is received in the ISDN DISCONNECT message. It is then propagated to the SIP network using the BYE message.

RELEASE to BYE- The User to User Data is received in the ISDN RELEASE message. It is then propagated to the outbound SIP network using the SIP BYE message.

RELEASE to 4xx, 5xx Response- The User to User Data is received in the ISDN RELEASE message. It is then propagated to the outbound SIP 4xx, 5xx Responses.

UUI in INFO Message- The User to User information is received in the ISDN INFO message. It is then propagated to the outbound SIP INFO message.

Between ISDN and H323

SETUP to SETUP- The User to User Data is received in the ISDN SETUP message. It is then propagated to the outbound H.323 network using the SETUP message in H.323. The interworking of the UUI information in the SETUP message is supported from H.323 to ISDN as well.

ALERTING to ALERTING- The User to User Data is received in the ISDN ALERTING message. It is then propagated to the outbound H.323 network using the ALERTING message in H.323. The interworking of the UUI information in the ALERTING message is supported from H.323 to ISDN as well.

RELEASE to RELEASE COMPLETE- The User to User Data is received in the ISDN RELEASE message. It is then propagated to the outbound H.323 network using the RELEASE COMPLETE message in H.323.

DISCONNECT to RELEASE COMPLETE- The User to User Data is received in the ISDN DISCONNECT message. It is then propagated to the outbound H.323 network using the RELEASE COMPLETE message in H.323.

SETUP to SETUP- The User to User Data is received in the H.323 SETUP message. It is then propagated to the outbound ISDN network using the SETUP message in H.323.

RELEASE COMPLETE to  DISCONNECT   - The User to User Data is received in the H.323 RELEASE COMPLETE message. It is then propagated to the outbound ISDN network using the DISCONNECT message in ISDN.

UUI in INFO Message- The User to User information is received in the ISDN INFO message. It is then propagated to the outbound H.323 INFO message.

Between SS7 and SIP

IAM to INVITE- The User to User data is initially received in the incoming SS7 IAM message. It is then propagated to the outbound SIP network using the INVITE message.

200 OK to ANM- The User to User data is initially received in the incoming SIP 200 OK message. It is then propagated to the outbound SS7 network using the ANM message.

RELEASE to BYE- The User to User Data is received in the ISDN RELEASE message. It is then propagated to the outbound SIP network using the SIP BYE message.

Call Trace:

Below is screen capture of what a Call Trace of the UUI data would look like. The call is SIP to SIP and the User to User Information is passed along in the SIP INVITE message. The UUI message is displayed in red below.

18:51:53.893 CALL(SIP) (04:00003:01)
                        <--- [10.129.47.147, 5060 <- 10.129.44.171, 5060]
                       INVITE sip:2145551212@10.129.47.147:5060 SIP/2.0\r\n
                       Via: SIP/2.0/UDP 10.129.44.171:5060;rport;branch=z9hG4bK
                       -5d5a-1196967113-19997-373\r\n
                       Call-ID: 1b0b-402-1162007185153-ANSI_SIP_UUI-4@10.129.44
                       .171\r\n
                       CSeq: 1 INVITE\r\n
                       Max-Forwards: 70\r\n
                       To: <sip:2145551212@10.129.47.147:5060>\r\n
                       From: <sip:2125551212@10.129.44.171>;tag=95ffcd055e0f78f
                       7d5d397020e89288d96b52669\r\n
                       User-Agent: Dialogic-SIP/10.5.0.148 ANSI_SIP_UUI 4\r\n
                       User-to-User: THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG\r\n
                       Contact: <sip:2125551212@10.129.44.171:5060>\r\n
                       Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, INFO, UPDATE\r\n
                       Supported: path, timer\r\n
                       Session-Expires: 1800\r\n
                       Expires: 300\r\n
                       Organization: Dialogic Inc\r\n
                       Content-Type: application/sdp\r\n
                       Content-Length: 164\r\n
                       \r\n
                       v=0\r\n
                       o=Dialogic_SDP 0 0 IN IP4 10.129.44.171\r\n
                       s=Dialogic-SIP\r\n
                       c=IN IP4 10.129.44.166\r\n
                       t=0 0\r\n
                       m=audio 8008 RTP/AVP 0\r\n
                       a=rtpmap:0 PCMU/8000\r\n
                       a=silenceSupp:off - - - -\r\n

Configuration

UUI Support needs to be configured in SS7 and ISDN to either "Pass" or "Not Pass" the User to User information. UUI is configured on a Channel Group by Channel Group basis. See below on configuration.

ISDN

• The UUI support is configured on each Channel Group. Under each Channel Group Object in ClientView right click and select New Channel Group.

• In the Channel Group pane that appears enter a name for the Channel Group and select ISDN from the drop down menu in the Signaling Type field:
  

  

• Enter all other network relevant information in this pane and commit this information.

• Right click on the Channel Group just created and select "New ISDN Group"

• In the ISDN Group pane that appears enter any relevant information such as D channel etc. Commit This:
  
  

  

• Right click on the ISDN pane and select "New ISDN Circuits".

• In the B Channel Pane that appears select the b channel information and Commit this:
  

  

• The ISDN Channel group is now configured. In order to configure the UUI support, right click on ISDN Pane and select "New ISDN Parameter Filter".

• The following pane will appear.
  

  

• In this pane you can select whether the User to User information will be passed along by selecting the drop down menu and choosing either Pass or Don't Pass 

SS7

• The UUI support is configured on each Channel Group. Under each Channel Group Object in ClientView right click and select New Channel Group.

• In the Channel Group Pane that appears enter a name for the Channel Group and select SS7 from the drop down menu in the Signaling Type field.

• Enter all other network relevant information in this pane and commit this information.

• Right click on the Channel Group just created and select "New ISUP Group"

• In the ISUP Pane that appears enter any relevant information such as D channel etc. Commit This:
  

  

• Right click on the ISUP Pane and select "New Circuits".

• In the Circuits Pane that appears configure the CIC information using the drop down menus and Commit this.

• The SS7 Channel group is now configured. In order to configure the UUI support, right click on ISUP Pane and select "New ISDN Parameter Filter". The following Pane will appear
  

  

• In this pane you can select whether the User to User information will be passed along by selecting the drop down menu and choosing either Pass or Don't Pass 

SIP

• UUI Support in SIP is configured under the SIP SGP Object in ClientView. Right click on Dialogic IMG EMS and select New Profiles and Commit this

• The SIP SGP object needs to be created now. Right click on Profiles object and select New SIP SGP

• The default SIP SGP object will be displayed if you would like to make any changes to this screen then change the first field which is the SIP Profile ID field to something other than ID = 0. Once this is accomplished then the rest of the fields can now be changed.

• In order to configure the SIP UUI support, right click on the SIP SGP object and select New SIP UUI Support. A screen like below will be displayed.
  

  

• The User to User Header Field is a drop down menu where UUI Support can be set to either Enable or Disable. If UUI Support is Enabled, a UUI Format field will open up below it and the user can decide whether UUI is transferred using Binary or Hexadecimal. Refer to screen capture below.
  

  

• The Prot. Discriminator Byte is set to Not Included by default.  If User to User is enabled, then decide whether Protocol Discriminator Byte is set to Not Included or Included. Refer to the IMG 1010 - SIP UUI Support topic for more information. Refer to the example in the next section.

Additional Information

• Maximum supported length for the User to User data is 131 bytes

• The User to User protocol discriminator supported will be 0x4 (IA5 characters -- ASCII) when interworked to and from SIP

Example:

UUI =  7e0d046773677367736773

This will get converted to gsgsgsgs where

ascii g = Hex 67

ascii s = Hex 73

• In software 10.5.3 SP3 support for the inclusion of parameters:- encoding, content, and purpose on the SIP side was added. See rules below.

  • Call is going from PSTN to SIP and SIP UUI is enabled, the parameters encoding, purpose, and content will be added to the SIP UUI information within the SIP messaging.

  • Call is going from SIP to PSTN, SIP UUI is enabled, and the parameters encoding, purpose, and content are included in the UUI information received. The IMG will accept the parameters but will not interwork them to the PSTN side. There is no support for these parameters on the PSTN side.