User`s guide

78 Dialogic
®
1000 and 2000 Media Gateway Series User’s Guide
Parameter Reference
3.3.10 ISUP Using Multipart MIME Group
The ISUP Using Multipart MIME parameters control the propagation of ISDN information
elements to SIP messages. The information elements are, typically, proprietary to a telephony
vendor and do not map to any defined SIP header. The DMG2000 uses multipart MIME bodies to
encapsulate the information element’s data. Various header fields allow the SIP endpoint to decode
the MIME body.
The following is an example of using multipart MIME to send an ISDN information element. The
line numbers are not part of the message; they are used in the discussion following the example.
1 INVITE sip:4700@10.10.11.47 SIP/2.0
2 From:<sip:2042@10.10.11.114:5060;user=phone>;vnd.pimg.port=23;tag=5A533246
3 To:<sip:4700@10.10.11.47>
4 Contact:<sip:2042@10.10.11.114:5060>
5 Mime-Version: 1.0
6 Content-Type:multipart/mixed ;boundary=”?(boundary)*”
7 Supported:replaces,early-session,100rel
8 Allow:INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,REFER,NOTIFY
9 Expires:120
10 Call-ID:[e-mail]
11 CSeq:1 INVITE
12 Max-Forwards:70
13 User-Agent:PBX-IP Media Gateway
14 Via:SIP/2.0/UDP 10.10.11.114:5060;branch=z9hG4bKE194EDF
15 Content-Length:291
16
17 --?(boundary)*
18 Content-Type: application/SDP
19 v=0
20 o=phone [phone] IN IP4 10.10.11.114
21 s=-
22 c=IN IP4 10.10.11.114
23 t=0 0
24 m=audio 49030 RTP/AVP 0 13
25 a=rtpmap:0 PCMU/8000/1
26 a=ptime:30
27 a=rtpmap:13 CN/8000
28
29 --?(boundary)*
30 Content-Type: application/ISUP; version=Dialogic-DMG2000-v1
31 Content-Disposition: signal ; handling=optional
32 Content-Description: ISDN IE 77h
33
34 37 31 36 35 35 35 36 35 35 32
35
36 --?(boundary)*--