UUI Support
The IMG 2020 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 2020 supports UUI for multiple protocols. Below is a list of the supported scenarios:
Protocols | Additional Information |
Between ISDN and ISDN | The UUI parameter will be passed transparently. The UUI information on the incoming side will be transferred to the outgoing side in the same message. |
Between SS7 and SS7 | The UUI parameter will be passed transparently. The UUI information on the incoming side will be transferred to the outgoing side in the same message. |
Between ISDN and SS7 | In the ISDN to SS7 scenario, the IMG 2020will interwork the UUI information received on the incoming side and will propagate it to the outgoing side. Refer to the Call Flow diagrams below. |
Between ISDN and SIP | In the ISDN to SIP scenario, the UUI parameters will be interworked into the SIP INFO message. Below is an Example of what UUI support is used for. 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. |
Between SS7 and SIP | The UUI information will be passed between SS7 and SIP. Refer to the SS7 to SIP call flows below. |
Note: The Variants supported in ISDN are EURO, JATE, and NI2.
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 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 SS7 RELEASE message. It is then propagated to the outbound SIP network using the SIP BYE message.  | UUI in USR Message- The User to User information is received in the SS7 USR message. It is then propagated to the outbound SIP INFO message and vice versa.  |
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 (see the "User-to-User:" header).
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=95ffcd055e0f78f7d5d397020e89288d96b52669\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
Support needs to be configured in both SS7 and/or 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.
Initial Configuration
The procedure below explains how to configure the IMG 2020 for UUI Feature. Before configuring the UUI feature, the IMG 2020 must have an initial configuration created on it. Follow the procedure before proceeding onto configuring the UUI feature.
ISDN Configuration
Configure D-Channel
Right click on the IMG 2020 physical node object and select New Signaling. The Signaling object is a parent or container object and nop configuration is needed here. Refer to the Signaling topic for more information.
Right click on the Signaling object and select New ISDN. The ISDN object is a parent or container object. Under the ISDN object multiple D-Channels can be configured. Refer to the ISDN - Signaling topic for more information.
Right click on the ISDN object and select New ISDN D-Channel. Select a DS-1 from the Primary Span field. This field is a drop down menu that contains all the TDM DS-1's created. DS-1's 0 through 3 are on the four RJ48 interfaces located on the rear of the IMG 2020 and DS-1's 0 through 27(T1) or 0 through 31(E1) refer to either the DS-3 or Optical Interface. Select from the drop down menus, the DS-1 and DS-0 that the D-Channel will get created on.
Select Yes from drop down list in the NFAS Supported field if NFAS (Non-Facility Associated Signaling) is being configured. Select No if configuring FAS (Facility Associated Signaling). Refer to isdn d topic for more information on configuring the D-Channel object.
Configure ISDN Circuits and UUI Support
Under the ISDN D-Channel object, the B-Channels will be configured. Follow the procedure below to create an ISDN Group and then the B-Channels that will be controlled by the D-Channel configured above. Once the B-Channels are configured, any attributes or parameters that need to be created for the B-Channels can then be configured. Follow procedure below.
Right click on the ISDN D-Channel object and select New ISDN Group. The ISDN Group assigns information such as the capabilities of the DS-1 the D-Channel will be configured on and the Network the D-Channel will be used in. Refer to the ISDN Group topic for more information on configuring this object.
Right click on the ISDN BDN object just created and select New ISDN Circuit Group. The Circuit Group are the B-Channels that are being controlled by the D-Channel configured above. Select a starting DS-1 from the Start Span field. This field is a drop down menu that contains all the TDM DS-1's created. Spans 0 through 3 are on the four RJ48 interfaces located on the rear of the IMG 2020 and DS-1's 0 through 27(T1) or 0 through 31(E1) refer to either the DS-3 or Optical Interface. Select from the drop down menus, the starting and ending DS-1's/DS-0's that will make up the ISDN Circuit Group. The Circuit Group being created will be controlled by the D-Channel configured above. Refer to the ISDN Circuit Group topic for more information on configuring this object.
Right click on the ISDN BDN object again and select New ISDN Parameter Filter. Select Pass from the drop down menu of the UUI field.
Configure an ISDN Channel Group along with the ISDN Circuits
Right click on the IMG 2020 object and select New Routing Configuration. The Routing Configuration object is container object and no configuration is needed. Refer to Routing Configuration topic for more information on this object.
Right click on the Routing Configuration object and select New Channel Groups. The Channel Groups object is a container object for multiple channel groups. No configuration is needed here. For more information refer to Channel Groups topic.
Right click on the Channel Groups object and select New Channel Group. In the Name field, either accept the default name entered or enter a name that will identify this specific Channel Group.
Select ISDN from the drop down menu in the Signaling Type field. For more information on configuring the ISDN Channel Group refer to Channel Group topic.
Right Click on the ISDN Channel Group created and select New Circuit Group. As described in the Configure the Configure ISDN circuits and UUI support section above, select the node and DS-1's/DS-0's that will be used for this circuit group. The selections made should mimic the selections made in the section above. Refer to the ISDN Circuit Group topic for more information on this object.
Click on the Channel Groups object which will now have a yellow exclamation point displayed. Click on the Download Resource Tables button and the SS7 Channel Group configuration just created will be sent to the 2020 IMG.
SS7 Configuration
Configure SS7 Network, SS7 Stack, SS7 Linkset, Links, Destinations, and Routes
To configure the SS7 Network along with stacks, linksets, links, destinations and routes, refer to the Configure SS7 topic. Once the functionality above has been configured, follow the steps described below to configure the SS7 Channel Group, SS7 ISUP Group, SS7 Parameter Filter and then enable UUI.
Configure the SS7 Parameter Filter to Pass UUI Info
After the basic SS7 Network has been configured, The SS7 Parameter Filter can be configured into this SS7 Network to either pass or not pass the UUI information. Follow instructions below.
Right click the SS7 ISUP Group object that was created under the Destination object in the SS7 Network and select New SS7 Parameter Filter.
Configure SS7 Channel Groups and a Second SS7 Circuit Group
Configure an SS7 Channel Group to communicate with the local SS7 network.
Right click on the IMG 2020 object and select New Routing Configuration. The Routing Configuration object is container object and no configuration is needed. Refer to Routing Configuration topic for more information on this object.
Right Click on the Routing Configuration object and select New Channel Groups. The Channel Groups object is a container object for multiple channel groups. No configuration is needed here. For more information refer to Channel Groups topic.
Right click on the Channel Groups object and select New Channel Group. In the Name field, either accept the default name entered or enter a name that will identify this specific Channel Group.
Select SS7_ISUP from the drop down menu in the Signaling Type field. For more information on configuring the SS7 Channel Group refer to Channel Group topic.
Right Click on the SS7 Channel Group created and select New Circuit Group. As described in the Configure the SS7 ISUP Group and Circuit Group (CICs) section above, select the node and the DS-1's/DS-0's that will be used for this circuit group. The selections made should mimic the selections made in the section above. Refer to the SS7 - Circuit Group under Signaling topic for more information on this object.
Click on the Channel Groups object which will now have a yellow exclamation point displayed. Click on the Download Resource Tables button and the SS7 Channel Group configuration just created will be sent to the 2020 IMG.
SIP Configuration
Create a SIP Profile (SGP) and then SIP Headers Page
Right click on the Profiles object and select New SIP Profiles. The SIP Profiles object is a parent or container object. No configuration is needed here. Refer to the SIP Profiles topic for more information on this object.
Right click on the SIP 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 SIP Profiles object and select New SIP Profile again. In the SIP Profile object that appears, either enter a name that identifies this SIP Profile or accept the default name already entered. In this example the SIP Profile was labeled UUI_Profile. Refer to the SIP Profile - SGP topic for more information on this object.
Right click on the SIP Profile object just created and select New SIP Headers. Select Enabled from the drop down menu of the User to User Header field. Refer to the SIP Profile - Headers topic for more information.
The Prot. Discriminator Byte is set to Not Included by default. If User to User is enabled, then decide whether the Protocol Discriminator Byte is to be set to Not Included or Included.
Example below displays the conversion of the Prot. Discriminator Byte:
UUI = 7e0d046773677367736773 = (Prot. Discriminator Byte)
This will get converted to gsgsgsgs where
ascii g = Hex 67
ascii s = Hex 73The SIP Profile can now be associated with an External Remote Gateway and the gateway can be linked to a SIP channel group. Refer to the Configure SIP (Single SIP IP) topic for information on configuring this.
UUI Format
The UUI Format field is supported when interworking SS7 to SIP or SIP to SS7. Prior to software Release 2.2 SP4.1, the UUI message was always interworked using the binary format. With the introduction of FR6550 UUI Enhancement feature, the UUI message can now be interworked using the hexadecimal format as well. The hexadecimal format is the specified format for UUI data within SIP per RFC 7433.
Binary (Default)- When binary is selected, the User to User Information is displayed as it has always been displayed. The binary stream is interworked and relayed to the opposite side.
Hexadecimal- When Hexadecimal is selected, the User to User Information is interworked as follows:
SS7 to SIP |
If User to User information is received in a binary stream, on the SIP side each binary character received will be converted to its hex equivalent for the uui-data field. Each binary character received will be converted to its hex equivalent. Refer to example below. Example: 00 D2 34 will be relayed to SIP side as 30 30 44 32 33 34 |
SIP to SS7 |
An ASCII stream received on SIP side will be converted to hexadecimal. Each ASCII character received on the SIP side will be presented as a hexadecimal byte on the SS7 side. Example: The ASCII stream 00A3B5 will be converted to the ASCII equivalent 00 00 41 33 42 35 |
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 73The IMG 2020 supports inclusion of parameters: encoding, content, and purpose on the SIP side. See rules below.
Rule 1- Call is going from PSTN to SIP and the SIP UUI is enabled, the parameters encoding, purpose, and content will be added to the SIP UUI information within the SIP messaging.
Rule 2- 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 2020 will accept the parameters but will not interwork them to the PSTN side. There is no support for these parameters on the PSTN side.