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 and variants. Below is a list of the supported protocols:
Note: If the SIP profile ID field in the SIP SGP object is set to ID:0 which is a default configuration, then the SIP UUI Support object is by default set to disabled. To allow the user to change the fields, the SIP SGP object ID must be changed from the default ID of 0 to something other than 0. Once this is changed then all fields in the SIP UUI Support object can be manipulated.
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.
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.
|
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.
|
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. |
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.
|
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.
|
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)
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.
Example:
UUI = 7e0d046773677367736773 = (Prot. Discriminator Byte)
This will get converted to gsgsgsgs where
ascii g = Hex 67
ascii s = Hex 73
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.