SIP Header Indicates Multimedia Call

1 Call Flow Diagrams
2 Call Trace
3 Configuration
4 Additional Information

The H.223 and H.245 protocols are used between multimedia endpoints over a circuit switched network. These protocols are utilized after a call is connected between two endpoints indicating the call is a multimedia call. The IMG 2020 can 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 Diagrams

As displayed in the call flow diagram 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

ALL> 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-SBC2020_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-SBC2020_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 SBC2020_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-SBC2020_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-SBC2020_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-SBC2020_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-SBC2020_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 SBC2020_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

Below are instructions on how to configure the functionality for this feature. Before configuring, an initial configuration must be created on it. Refer to the Basic Configurations procedure and verify the required basic functionality has been configured prior to configuring this feature. Also, the feature is supported when going from an SS7 or ISDN network to an SIP network which requires both SS7 and SIP signaling to be configured. Refer to the Configure SS7, Configure SIP (Multiple SIP IP), or Configure SIP (Single SIP IP) topics as required.

The procedure below describes how to configure the IMG 2020. 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.

Configure Incoming Channel Group

The incoming channel group can be either ISDN or SS7. Refer to the Configure ISDN or Configure SS7 topics for ISDN or SS7 signaling and channel group configuration information.

Configure SIP Profile SGP and SIP Headers object

Configure SIP Header object to enable X-DialogicMultimedia:yes/no data field. Once configured, and depending on the selections made, the IMG 2020 will add a SIP Proprietary Header to the outgoing SIP network.

Right click on the Profiles object and select New SIP Profile. The first SIP Profile created is a default profile and cannot be modified. Disregard this profile.Right click on the Profiles object again and select New SIP Profile again. This SIP Profile can now be modified. In the Name field, enter a name that describes the SIP Profile being created. In this procedure the SIP Profile was labeled SIP_Prof_Multimedia. Refer to topic for more information on configuring the remaining fields in this object.
Right click on the SIP 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. Refer to screen capture below.

Refer to SIP Profile - Headers topic for more information on configuring the X-DialogicMultimedia Call field as well as information on any of the remaining fields.

Configure SIP Channel Group

The call is going from TDM to SIP. Follow the instruction below to create and configure a SIP channel group.

Right click on the Routing Configuration object and select New Channel Groups. The Channel Groups object is a parent or container object and no configuration is required here. Refer to the Channel Groups object for more information.
Right click on Channel Groups object created earlier and select New Channel Group. Set the Signaling Type field to SIP.
Enter a name in the Name field that will describe this channel group. In this procedure, the channel group was labeled ChGrp_SIP_Multimedia. Refer to Channel Group topic for more information on configuring the remaining fields within the SIP Channel Group object.

Configure SIP External Gateway

Configure the External Gateway object. The External Gateway object configures the information required to communicate with the external gateway in the SIP network.

Right click on dialogic object and select New External Network Elements. No configuration is needed here. The External Network Element object is a container object and no configuration is required. Refer to External Network Elements topic for information on this object.
Right click on the External Network Elements object and select New External Gateways. Again, the external gateway object is a container or parent object and no configuration is required here. Refer to External Gateways object for more information.
Right click on External Gateways object and select New External Gateway. Enter a name that describes the gateway being created. In this procedure, the name Multimedia_GW was entered.

Field Descriptions

Modify the Protocol field to display SIP.
Enter an IP address in the Gateway IP Address field.
Within the SIP Profile field of the External Gateway object, select the SIP Profile SGP configured above. This profile configures the X-DLGCMultimedia: Data feature. Refer to the External Gateway topic for more information on configuring the remaining fields.

Configure IP Network Element

The SIP Channel Group just created must be associated with the External Gateway. Follow procedure below to link the two objects.

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 IP Network Element topic for more information on this object. Refer to the screen capture below.

The Channel Groups object will now have a yellow exclamation point for an Icon in the configuration tree. This icon indicates that the configuration has not been sent to the IMG 2020. Click on the Channel Groups object and then click on the Download Resource Tables button. This will send the configuration to the IMG 2020 and the icon will change to a green check mark indicating the system was configured with the channel group information.

Route SIP Channel group to the TDM 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

The feature is supported from SS7 to SIP -or- ISDN to SIP.
The feature is NOT supported from SIP to SS7 nor is it supported from SIP to ISDN. If the IMG 2020 receives the proprietary SIP header, it will not be recognized nor will it be 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 using the Web UI. The field is labeled X-Dialogic Multimedia Call.

Dialogic Integrated Media Gateways