IMG 1010 - SIP header indicating Multimedia call
As described in Feature F-5230, the H.223 and H.245 protocols are used between multimedia endpoints over a circuit switched network. These protocols are utilized after a successful call between two endpoints that indicates the call is for multimedia. Feature F-5698 gives the IMG the ability to detect an incoming SS7/ISDN multimedia call based on a specific octet contained in the SS7/ISDN setup message. If the call is considered an audio call, the message will be interworked as a normal ISDN/SS7 to SIP call. If however, the call is considered a multimedia call, a proprietary SIP Header can be added indicating it is a multimedia call and the added header will be interworked to the SIP side. The feature is enabled through a new header added to the SIP Headers object. Refer to the information below.
Call Flow Diagram
As displayed in Call Flow diagrams above, the following is true:
Both the audio call and the multimedia call are routed to the same endpoint.
A special SIP proprietary header is added to the INVITE message indicating the incoming SS7/ISDN setup message is for multimedia (H.223 and H.245 is set in the User Information Layer 1 Protocol codepoint).
The INVITE for the audio call has no special header, -or- it can contain a header indicating the call is not for multimedia.
Call Trace
CALL> 14:23:59.936 CALL(SS7) (00:00001:00)
RCVD: STK: 0 PRI: 00
DPC: 1-1-1 OPC: 2-2-2
SLS: 0x00 CIC: 00500 (0x01f4)
IAM [0021180a06020907031016979999990a07031313535521211d
04809882a303077c0518809882a600]
14:23:59.936 CALL(SS7) (00:00001:00) RCVD IAM from (0x1012:0x809:500)
14:23:59.936 CALL(SS7) (00:00001:00) Leg 0 associated with LTS(2)(span 28 chan 2)
14:23:59.936 CALL(SS7) (00:00001:00) SENT Setup Ind w/info (0x1012:0x809:500) to L4
14:23:59.936 CALL(L4) (00:00001:00) RCVD Setup Ind from SS7
14:23:59.936 CALL(L4) (00:00001:00) SENT RFS to GCL
14:23:59.936 CALL(GCL) (00:00001:00) RCVD RFS DN=[6179999999] ANI=[3135551212] from L4
14:23:59.936 CALL(GCL) (00:00001:00) ANI APRI=[0],SI=[3],Category=[10]
14:23:59.936 CALL(GCL) (00:00001:00) DN NOA=[3]
14:23:59.936 CALL(GCL) (00:00001:00) Incoming Channel Group = 1 [SS7CG]
14:23:59.936 CALL(GCL) (00:00001:00) SENT RADIUS ACCT START to RADIUS
14:23:59.936 CALL(L4) (00:00001:00) RCVD RFS response from GCL
14:23:59.986 CALL(GCL) (00:00001:00) RCVD ACCT START ACK from RADIUS
14:23:59.986 CALL(GCL) (00:00001:00) SENT Make Call Request to GCL
14:23:59.986 CALL(GCL) (00:00001:01) SENT Route Control to L4
14:23:59.986 CALL(L4) (00:00001:00) RCVD Route Control from GCL
14:23:59.986 CALL(L4) (00:00001:00) Accessing Route Table 5
14:23:59.986 CALL(L4) (00:00001:00) Accessing Route Table 5
14:23:59.986 CALL(GCL) (00:00001:01) RCVD Route Control Ack (Mid Stream Router)from L4
14:23:59.986 CALL(GCL) (00:00001:01) Outgoing Channel Group = 2 [SipCG2]
14:23:59.986 CALL(GCL) (00:00001:01) SENT Route Control to L4
14:23:59.986 CALL(L4) (00:00001:01) RCVD Route Control from GCL
14:23:59.986 CALL(L4) (00:00001:01) Accessing Resource Table 1
14:23:59.986 CALL(L4) (00:00001:01) Resource Group ID is 1
14:23:59.986 CALL(L4) (00:00001:01) Hunting Algorithm is Round Robin
14:23:59.996 CALL(L4) (00:00001:01) SENT Outseize Ctrl to SIP
14:23:59.996 CALL(GCL) (00:00001:01) RCVD CPE of ADDRESS INFO from L4
14:23:59.996 CALL(GCL) (00:00001:01) Leg 1 associated with LTS(1024)(span 4096 chan 0)
14:23:59.996 CALL(SIP) (00:00001:01) RCVD Outseize Ctrl from L4
14:23:59.996 CALL(SIP) (00:00001:01) SENT Route Control to L4
14:23:59.996 CALL(L4) (00:00001:01) RCVD Route Control from SIP
14:23:59.996 CALL(L4) (00:00001:01) Accessing GatewayId to IP Tables
14:23:59.996 CALL(L4) (00:00001:01) Gateway ID is 1026
14:23:59.996 CALL(L4) (00:00001:01) SENT Route Control Ack to SIP
14:23:59.996 CALL(SIP) (00:00001:01) RCVD Route Control Ack from L4
14:23:59.996 CALL(SIP) (00:00001:01) Session Group Profile ID is 1
14:23:59.996 CALL(SIP) (00:00001:01) SENT Route Control to L4
14:23:59.996 CALL(L4) (00:00001:01) RCVD Route Control from SIP
14:23:59.996 CALL(L4) (00:00001:01) Accessing IP Bearer Profiles
14:23:59.996 CALL(L4) (00:00001:01) Profile Id 1 (RG 769)
14:23:59.996 CALL(L4) (00:00001:01) SENT Route Control Ack to SIP
14:23:59.996 CALL(SIP) (00:00001:01) RCVD Route Control Ack from L4
14:23:59.996 CALL(SIP) (00:00001:01) REM TP port=5080 transport:0
14:23:59.996 CALL(SIP) (00:00001:01) SENT INVITE W/SDP to 10.130.1.54:5080 Cseq:1
14:23:59.996 CALL(SIP) (00:00001:01) with R-URI: 10.130.1.54:5080 UDP
14:23:59.996 CALL(SIP) (00:00001:01) and Call-id: 7e97-400-3202011142359-IMG1010_Mtl-0-10.130.5.72
14:23:59.996 CALL(SIP) (00:00001:01)
<--- [10.130.1.54, 5080 <- 10.130.5.72, 5060]
INVITE sip:6179999999@10.130.1.54:5080 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.130.5.72:5060;rport;branch=z9hG4bK-4
782-1303309439-4999-214\r\n
Call-ID: 7e97-400-3202011142359-IMG1010_Mtl-0-10.130.5.72\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
To: <sip:6179999999@10.130.1.54:5080>\r\n
From: "3135551212"<sip:3135551212@10.130.5.72>;tag=95ffc
d055e0f78f7d5d397020e89288dfc8f76e3\r\n
User-Agent: Dialogic-SIP/10.5.3.616 IMG1010_Mtl 0\r\n
P-Asserted-Identity: "3135551212"<sip:3135551212@10.130.5.72>\r\n
Contact: <sip:3135551212@10.130.5.72:5060>\r\n
Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBS
CRIBE, NOTIFY, INFO, REFER, UPDATE\r\n
Supported: path, replaces, tdialog\r\n
Expires: 300\r\n
Organization: Dialogic\r\n
X-DLGCMultimedia: yes\r\n
Content-Length: 424\r\n
Content-Type: multipart/mixed;boundary=ub-dialogic-sw-1\r\n
MIME-Version: 1.0\r\n
\r\n
--ub-dialogic-sw-1\r\n
Content-Type: application/sdp\r\n
\r\n
v=0\r\n
o=Dialogic_SDP 0 0 IN IP4 10.130.5.72\r\n
s=Dialogic-SIP\r\n
c=IN IP4 10.130.2.73\r\n
t=0 0\r\n
m=audio 8000 RTP/AVP 8 0\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=silenceSupp:off - - - -\r\n
\r\n
--ub-dialogic-sw-1\r\n
Content-Type: application/ISUP; version=ETSI-V3\r\n
Content-Disposition: signal;handling=optional\r\n
\r\n
01 00 21 18 0a 06 02 09 07 03 10 16 97 99 99 99 0a 07 03
13 13 53 55 21 21 1d 04 80 98 82 a3 03 07 7c 05 18 80 9
8 82 a6 00 \r\n
--ub-dialogic-sw-1--\r\n
14:24:00.006 CALL(SIP) (00:00001:01) RCVD 100 Trying from 10.130.1.54:5080 udp CSeq:1 Msg Size:460
14:24:00.006 CALL(SIP) (00:00001:01)
---> [10.130.1.54, 5080 -> 10.130.5.72, 5060]
SIP/2.0 100 Trying\r\n
From: "3135551212"<sip:3135551212@10.130.5.72>;tag=95ffc
d055e0f78f7d5d397020e89288dfc8f76e3\r\n
To: <sip:6179999999@10.130.1.54:5080>;tag=5156SIPpTag011
\r\n
Call-ID: 7e97-400-3202011142359-IMG1010_Mtl-0-10.130.5.7
2\r\n
CSeq: 1 INVITE\r\n
Via: SIP/2.0/UDP 10.130.5.72:5060;rport;branch=z9hG4bK-4
782-1303309439-4999-214\r\n
Contact: <sip:10.130.1.54:5080;transport=UDP>\r\n
Content-Length: 0\r\n
Organization: 10.65.3.40\r\n
Server: Avaya SIP Enablement Services\r\n
\r\n
14:24:00.006 CALL(SIP) (00:00001:01) RCVD 180 Ringing W/SDP from 10.130.1.54:5080 udp CSeq:1 Msg Size:683
14:24:00.006 CALL(SIP) (00:00001:01)
---> [10.130.1.54, 5080 -> 10.130.5.72, 5060]
SIP/2.0 180 Ringing\r\n
From: "3135551212"<sip:3135551212@10.130.5.72>;tag=95ffc
d055e0f78f7d5d397020e89288dfc8f76e3\r\n
To: <sip:6179999999@10.130.1.54:5080>;tag=5156SIPpTag011
\r\n
Call-ID: 7e97-400-3202011142359-IMG1010_Mtl-0-10.130.5.7
2\r\n
CSeq: 1 INVITE\r\n
Via: SIP/2.0/UDP 10.130.5.72:5060;rport;branch=z9hG4bK-4
782-1303309439-4999-214\r\n
Contact: <sip:10.130.1.54:5080;transport=UDP>\r\n
Supported: timer,replaces,join,histinfo\r\n
Allow: INVITE,CANCEL,BYE,ACK,PRACK,SUBSCRIBE,NOTIFY,REFE
R,OPTIONS,INFO,PUBLISH\r\n
Content-Type: application/sdp\r\n
Content-Length: 131\r\n
\r\n
v=0\r\n
o=user1 53655765 2353687637 IN IP4 10.130.1.54\r\n
s=-\r\n
c=IN IP4 10.130.1.54\r\n
t=0 0\r\n
m=audio 6000 RTP/AVP 0\r\n
a=rtpmap:0 PCMU/8000
14:24:00.006 CALL(SIP) (00:00001:01) SENT Outseize Ack to L4
14:24:00.006 CALL(SIP) (00:00001:01) SENT Cut-Thru to L4
14:24:00.006 CALL(SIP) (00:00001:01) m line (audio) codec list: 0
14:24:00.006 CALL(SIP) (00:00001:01) RTP Type: 0, name: PCMU, clk: 8000
14:24:00.006 CALL(SIP) (00:00001:01) SENT CDR Msg Event to L4
14:24:00.006 CALL(SIP) (00:00001:01) Set media src IP 10.130.2.73:8000
14:24:00.006 CALL(SIP) (00:00001:01) Set media dst IP 10.130.1.54:6000
14:24:00.006 CALL(SIP) (00:00001:01) CODEC Negotiation Priority LOCAL
14:24:00.006 CALL(SIP) (00:00001:01) Set media PLD ID 2
14:24:00.006 CALL(SIP) (00:00001:01) Set media PLD Size 20, Multiplier:4
14:24:00.006 CALL(SIP) (00:00001:01) RFC 2833 DTMF Relay Disabled,method=0
14:24:00.006 CALL(SIP) (00:00001:01) Set Fax Type to Relay T.38
14:24:00.006 CALL(SIP) (00:00001:01) Source Port Validation : Enabled
14:24:00.006 CALL(SIP) (00:00001:01) SENT L3-L3 Outseize Ctrl to VPPL
14:24:00.006 CALL(SIP) (00:00001:01) RCVD 200 OK INVITE W/SDP from 10.130.1.54:5080 udp CSeq:1 Msg Size:731
14:24:00.006 CALL(SIP) (00:00001:01)
---> [10.130.1.54, 5080 -> 10.130.5.72, 5060]
SIP/2.0 200 OK\r\n
From: "3135551212"<sip:3135551212@10.130.5.72>;tag=95ffc
d055e0f78f7d5d397020e89288dfc8f76e3\r\n
To: <sip:6179999999@10.130.1.54:5080>;tag=5156SIPpTag011\r\n
Call-ID: 7e97-400-3202011142359-IMG1010_Mtl-0-10.130.5.72\r\n
CSeq: 1 INVITE\r\n
Via: SIP/2.0/UDP 10.130.5.72:5060;rport;branch=z9hG4bK-4782-1303309439-4999-214\r\n
Contact: <sip:10.130.1.54:5080;transport=UDP>\r\n
Supported: timer,replaces,join,histinfo\r\n
Allow: INVITE,CANCEL,BYE,ACK,PRACK,SUBSCRIBE,NOTIFY,REFE
R,OPTIONS,INFO,PUBLISH\r\n
Session-Expires: 1800;refresher=uas\r\n
Require: timer\r\n
Content-Type: application/sdp\r\n
Content-Length: 131\r\n
\r\n
v=0\r\n
o=user1 53655765 2353687637 IN IP4 10.130.1.54\r\n
s=-\r\n
c=IN IP4 10.130.1.54\r\n
t=0 0\r\n
m=audio 6000 RTP/AVP 0\r\n
a=rtpmap:0 PCMU/8000
14:24:00.006 CALL(IP) (00:00001:01) RCVD Outseize ([vts 0] [m0.0.0]) from L3P (span 4096 chan 0)
14:24:00.006 CALL(IP) (00:00001:01) RTP: (Src) 10.130.2.73:8000
14:24:00.006 CALL(IP) (00:00001:01) RTP: (Dst) 10.130.1.54:6000
14:24:00.006 CALL(L4) (00:00001:01) RCVD Outseize ACK from SIP
14:24:00.006 CALL(L4) (00:00001:01) RCVD Cut Thru from SIP
14:24:00.006 CALL(L4) (00:00001:01) SENT CDR Msg Event to GCL
14:24:00.006 CALL(IP) (00:00001:01) Security on RTP(SRTP) Disabled mod: 0 vts 0
14:24:00.006 CALL(GCL) (00:00001:01) RCVD CDR Msg Event from L4
14:24:00.006 CALL(GCL) (00:00001:00) SENT Connect w/Pad Response to L4
14:24:00.006 CALL(L4) (00:00001:01) SENT CutThru to L4
14:24:00.006 CALL(L4) (00:00001:00) SENT Alerting to SS7
14:24:00.006 CALL(L4) (00:00001:00) SENT connect_1way: r_ts=0x400 l_ts=0x2 to TSI
14:24:00.006 CALL(L4) (00:00001:01) SENT connect_1way: r_ts=0x2 l_ts=0x400 to TSI
14:24:00.006 CALL(SIP) (00:00001:01) RCVD Host Connect from L4
14:24:00.006 CALL(SS7) (00:00001:00) RCVD Alerting (0x809:0x1012:500) from L4
14:24:00.006 CALL(SS7) (00:00001:00)
SENT: STK: 0 PRI: 00
DPC: 2-2-2 OPC: 1-1-1
SLS: 0x1f4 CIC: 00500 (0x01f4)
ACM [040100]
14:24:00.006 CALL(SS7) (00:00001:00) SENT ACM to (0x809:0x1012:500)
14:24:00.016 CALL(IP) (00:00001:01) SrcPortValidation: Enabled
14:24:00.016 CALL(IP) (00:00001:01) VoIP Codec is G711Mulaw; Payload Size is 20 ms
14:24:00.016 CALL(IP) (00:00001:01) Fax Mode is T.38 Relay, Modem Mode is Disabled
14:24:00.016 CALL(IP) (00:00001:01) MID enabled, 30.0 sec
14:24:00.016 CALL(IP) (00:00001:01) Initial MID enabled, 181.0 sec
14:24:00.026 CALL(IP) (00:00001:01) SENT Outseize ACK (toPvid: x66) to L3P
14:24:00.026 CALL(SIP) (00:00001:01) RCVD Outseize Ack from VPPL
14:24:00.026 CALL(SIP) (00:00001:01) SENT ACK WO/SDP to 10.130.1.54:5080 Cseq:1
14:24:00.026 CALL(SIP) (00:00001:01) with R-URI: 10.130.1.54:5080 UDP
14:24:00.026 CALL(SIP) (00:00001:01)
<--- [10.130.1.54, 5080 <- 10.130.5.72, 5060]
ACK sip:10.130.1.54:5080 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.130.5.72:5060;rport;branch=z9hG4bK-6
f3a-1303309440-4999-214\r\n
Call-ID: 7e97-400-3202011142359-IMG1010_Mtl-0-10.130.5.72\r\n
CSeq: 1 ACK\r\n
Max-Forwards: 70\r\n
To: <sip:6179999999@10.130.1.54:5080>;tag=5156SIPpTag011\r\n
From: <sip:3135551212@10.130.5.72>;tag=95ffcd055e0f78f7d
5d397020e89288dfc8f76e3\r\n
User-Agent: Dialogic-SIP/10.5.3.616 IMG1010_Mtl 0\r\n
Content-Length: 0\r\n
\r\n
14:24:00.026 CALL(SIP) (00:00001:01) SENT Connect to L4
14:24:00.026 CALL(SIP) (00:00001:01) RCVD Cut Thru from VPPL
14:24:00.026 CALL(SIP) (00:00001:01) RCVD Connect from VPPL
14:24:00.026 CALL(L4) (00:00001:01) RCVD Connect from SIP
14:24:00.026 CALL(L4) (00:00001:01) SENT CPE of ANSWER to GCL
14:24:00.026 CALL(GCL) (00:00001:01) RCVD CPE of ANSWER from L4
14:24:00.026 CALL(GCL) (00:00001:01) SENT RADIUS ACCT START to RADIUS
14:24:00.076 CALL(GCL) (00:00001:01) RCVD ACCT START ACK from RADIUS
14:24:00.076 CALL(GCL) (00:00001:01) SENT Call Answered to GCL
14:24:00.076 CALL(GCL) (00:00001:00) SENT CPE of ANSWER to L4
14:24:00.076 CALL(L4) (00:00001:00) RCVD CPE of ANSWER from GCL
14:24:00.076 CALL(L4) (00:00001:00) SENT Connect to SS7
14:24:00.076 CALL(SS7) (00:00001:00) RCVD Connect (0x809:0x1012:500) from L4
14:24:00.076 CALL(SS7) (00:00001:00)
SENT: STK: 0 PRI: 00
DPC: 2-2-2 OPC: 1-1-1
SLS: 0x1f4 CIC: 00500 (0x01f4)
ANM [00]
14:24:00.076 CALL(SS7) (00:00001:00) SENT ANM to (0x809:0x1012:500)
Configuration
Before being able to configure the IMG to interwork the SIP Proprietary header between SS7 or ISDN and SIP, the following objects must first be configured. Configure these initial objects before proceeding to the procedure below.
IMG 1010 - Configuring SS7 Signaling - 10.5.1 (for SS7 to SIP call flow)
The procedure below describes how to configure the IMG . In the procedure below the incoming side is ISDN and the outgoing side will be SIP since the feature supports a call going from ISDN to SIP. If call flow is SS7 to SIP, the procedure would be modified for SS7 signaling, but the basic configuration will all be the same.
Create ISDN Signaling and ISDN Channel Group (Incoming Channel Group)
Right click on the IMG Name object (Physical Node) and select New Signaling. The Signaling object is a container object for all signaling on the IMG. No more configuration is needed within this object. Refer to IMG 1010 - Signaling Object topic for more information on this object
Right click on the Signaling object and select New ISDN. A ISDN D-Channels object will get created. This is a container object and no configuration is needed here. Refer to the IMG 1010 - ISDN Signaling Pane topic for more information on this object.
Right click on the ISDN D-Channels object and select New ISDN D-Channel. Configure the D-Channel in this object. Refer to the IMG 1010 - ISDN D Channel topic for more information on configuring this object.
Right click on IMG EMS and select New Routing Configuration. A Routing Configuration Pane will appear. Refer to the IMG 1010 - Routing Configuration Object topic for more information on this object.
Right click on Routing Configuration and select New Channel Groups. A Channel groups container object is created. This object will allow multiple channel groups to be created beneath it. Refer to the IMG 1010 - Channel Groups topic for more information on this object.
Right click on the Channel Groups Object and select New Channel Group. A Channel Group Object will appear. Enter a name for this channel group and set the Signaling Type to ISDN. In this example, the channel group was labeled ChGrp_ISDN. Refer to the IMG 1010 - Channel Group topic for more information on configuring this object.
Right click on the ISDN Channel group just created and select New ISDN Group. Select a D-Channel from drop down menu in the ISDN D channel field. Refer to the IMG 1010 - ISDN Group topic for more information on configuring this object.
Right click on the ISDN Group object just created and select New ISDN Circuits. Select which spans/channel will be utilized in this ISDN circuits group. Refer to the IMG 1010 - ISDN Circuits topic for more information on configuring this object.
Create SIP SGP and SIP Headers objects
Configure SIP Header object to enable X-DialogicMultimedia:yes/no data field. Once configured, and depending on the selections made, the IMG will add a SIP Proprietary Header to the outgoing SIP network.
Right Click on the Profiles object and select New SIP SGP. Once SIP SGP pane is created, change the SIP Profile ID field to something other than 0 by selecting a different ID from the drop down menu. This will allow user to edit the SIP SGP Profile. Refer to topic for more information on configuring this object.
Right Click on the SIP SGP Profile object and select New SIP Headers. In the SIP Headers object that appears select one of the choices in the drop down menu of the field X-Dialogic Multimedia Call. In this procedure, Multimedia call and Audio call was selected from drop down menu. See screen capture below. Refer to topic for more information.
Create SIP Signaling Stack
Configure the SIP signaling stack on the IMG.
Right click on the Signaling object and select New SIP. Refer to the IMG 1010 - SIP Signaling Object topic for more information on configuring this object.
Create SIP Channel Group
Right click on Channel Groups object created earlier and select New Channel Group. Set the Signaling Type field to SIP and enter a name for this channel group. Refer to IMG 1010 - Channel Group topic for more information on configuring a SIP Channel Group.
Create External SIP Gateway
The gateway being created is the SIP endpoint on the SIP network that the IMG will be communicating with. Follow procedure below.
Right click on IMG EMS and select New External Network Elements. No configuration is accomplished here. The External Network Element pane is a container object to multiple external entities in the network. Refer to IMG 1010 - External Network Elements topic for more information.
Right click on the External Network Elements object and select New External Gateways. Again, no configuration is accomplished here. Refer to IMG 1010 - External Gateways object for more information.
Right click on External Gateways object and select New External Gateway. Enter a name to identify this gateway, modify the Gateway Signaling Protocol field to display SIP, and enter an IP address in the Gateway IP Address field.
Within the SIP Profile field of the External Gateway object, select the SIP SGP created above for the X-DLGCMultimedia: Data feature. See screen capture below. Refer to the IMG 1010 - External Gateway topic for more information.
Point SIP Channel group to gateway created
The SIP Channel group created above must point to the external gateway just created.
Right Click on the SIP Channel group created above and select New IP Network Element. In the IP Network Element field, select from drop down menu the gateway created above. Refer to the IMG 1010 - IP Network Element topic for more information on this object. See screen capture below
Route SIP Channel group to ISDN Channel group
At this point the feature has been configured and both the ISDN and SIP channel groups have been configured. Using routing information, configure the routing so the ISDN channel group and SIP channel group created route to each other.
Additional Information
This feature is supported from SS7 to SIP -or- ISDN to SIP.
The feature in NOT supported in SIP to SS7 nor is it supported from SIP to ISDN. If the IMG receives the proprietary SIP header, it will not be recognized and not interworked.
For ISDN, the User Information Layer 1 Protocol codepoint can be found in the Low Layer Compatibility IE and/or in the Bearer Capability IE. Both IE's are present in the SETUP message.
For SS7, the Low Layer Compatibility IE can be found in the Access Transport parameter. The Bearer Capability IE is equivalent to the User Service Information parameter. Thus, the User Information Layer 1 Protocol codepoint can be found in the Low Layer Compatibility IE in the Access Transport parameter, and it can be found in the User Service Information parameter. These two parameters are present in the SS7 IAM message.
The feature is disabled by default and can be configured under the SIP Headers object in ClientView. The field is labeled X-Dialogic Multimedia Call.