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.

 

 

The information is transferred transparently through the network and does not have any effect on the call. The IMG supports UUI for multiple protocols. On the TDM side the IMG supports ISDN to ISDN, ISDN to SS7, SS7 to SS7. On the IP side the IMG supports and ISDN to SIP. In the ISDN to SIP scenario the IMG will interwork the UUI parameters into the SIP INFO message. Below one example of what UUI support could be used for.

 

Note: In software 10.5.1_ER3 and above, F-1629 expands the UUI Support feature to add in support for ISDN-H.323. Functionality and configuration of the UUI feature all remain the same. See below.

 

Example:    

A customer would call a 1-800 number and get a Interactive Voice Recognition system that will query the caller for information. The information collected would be validated and sent to an operator to assist the caller. Once the operator picks up the transferred call, the information that the caller had previously entered with the initial IVR system could be transferred to the operator with the UUI message. All the information gathered by the IVR system could be accessed by the operator and the information would not have to be entered twice.

 

General Knowledge:

 

 

Example:  

UUI =  7e0d046773677367736773

 

This will get converted to gsgsgsgs where

ascii g = Hex 67

ascii s = Hex 73

 

 

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:

 

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

  2. 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.

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

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

  5. In the ISDN Pane that appears enter any relevant information such as D channel etc. Commit This

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

  7. In the B Channel Pane that appears select the b channel information and Commit this.

  8. 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".

  9. The following pane will appear.

 

 

SC_CV_Parameter_Filter_Pane.png

 

  1. 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:

 

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

  2. 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.

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

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

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

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

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

  8. 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

 

 

SC_CV_Parameter_Filter_SS7_1050.png

 

 

  1. 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:

 

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

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

  3. 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.

  4. 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.

 

 

SC_CV_SIP_UUI_Pane.png

 

  1. The User to User Header Field is a drop down menu where you can enable and disable the UUI Support.

  2. The Prot. Discriminator Byte is disabled by default. If you would like to enable it there is a drop down menu that allows you to include the Prot. Discriminator byte in the SDP. See Example of Prot. Discriminator Byte below.

 

UUI =  7e0d046773677367736773 = (Prot. Discriminator Byte)

 

This will get converted to gsgsgsgs where

ascii g = Hex 67

ascii s = Hex 73

 

 

Basic Call Flows with UUI Enabled:

Below are Basic Call Flows when UUI Support is enabled.

 

SIP <  > ISDN:

User to User Data is sent in the ISDN CONNECT message is interworked into the SIP 200 OK message.

 

 

CF_SIP_ISDN_connected_UUI_Support.png

 

 

 

SIP <   > ISDN:

During the Active Call Phase the SIP INFO message with User to User Data is interworked in the ISDN INFO UUI message

 

 

CF_SIP_ISDN_ACTIVE_UUI_Support.png

 

 

SS7<   >SS7:

User to User data is initially sent in the IAM. The  User to User data is then propagated from the IAM to the received ANM message.

 

 

CF_SS7_SS7_UUI_Support.png

 

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 message is bolded 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: Cantata-SIP/10.5.0.148 ANSI_SIP_UUI 4\r\n

                       User-to-User: THE QUICK BROWN FOX JUMPS OVER THE LAZY DO

                       G\r\n

                       Contact: <sip:2125551212@10.129.44.171:5060>\r\n

                       Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBS

                       CRIBE, 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=Cantata_SDP 0 0 IN IP4 10.129.44.171\r\n

                       s=Cantata-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