You are here: CSP Developer’s Guide: Internet Protocol > 7 Interworking > Tunneling UPDF TLVs

Tunneling UPDF TLVs

Two Methods for Tunneling

Two methods are available to tunnel the underlying UPDF TLVs from one CSP to another:

• Configure the SIP stack to tunnel all outbound INVITE(s) to include the TLVs.

• Request the UPDF TLV to be included on a per-outbound-call basis.

The first method involves using the VoIP Configure message. The second method involves adding the SIP Tunnel Type TLV (0x2936) to the Route Control message.

All Calls Contain UPDF TLVs

This example shows how to form a VoIP Configure message to enable tunneling of UPDF data for all SIP calls.

VoIP Configure message:

H->X

[00 27 00 ee 00 0f ff 00 00 00 00 05 01 c8 00 01 04 02 6a 00 01 04 02 6b 00 01 02 02 64 00 04 0a 0a 0c 21 02 70 00 02 00 02]

Example: SIP message from the SIP stack:

INVITE sip:10.10.12.33:5060 SIP/2.0

Via: SIP/2.0/UDP 10.10.12.32

To: 3600<sip:3600@10.10.12.33:5060>

From: 3300<sip:3300@10.10.12.32:5060>;tag=5186492ec

Contact: 3300<sip:3300@10.10.12.32:5060>

User-Agent: Excel/8.0.76

Call-ID: EXCEL-CSP255.206.236.250@10.10.12.32

CSeq: 1 INVITE

Content-Type: Application/Multipart

Content-Length: 435

Content-Type: multipart/mixed; boundary="ec=_10e=_1fa"

--"ec=_10e=_1fa"

Content-Type: application/SDP

v=0

o=sip 482 482 IN IP4 10.10.12.32

s=SIP_Call

c=IN IP4 10.10.12.36

t=2208989036 0

m=audio 10072 RTP/AVP 0

a=rtpmap:0 PCMU/8000

--"ec=_10e=_1fa"

Content-Type: application/SS7 ISUP; version:EXCEL-UPDF

Content-Transfer-Encoding: binary

03 00 33 00 39 00 07 27 17 00 05 10 00 04 36 00 27 18 00 07 10 00 04 37 04 33 00 27 92 00 04 0a 0a 0c 24 27 93 00 04 00 00 27 58 27 b0 00 02 01 02 27 b1 00 02 01 01 27 7e 00 03 08 00 00

Important! In the above MIME encoded message, the Hex ASCII data that appears after the Content-Transfer-Encoding: binary line is actually transmitted in binary, but is listed here as hex ASCII so you can read it.

Route Control message sent from the host:

The following is the actual call being placed with a Route Control message, and received with the RFS.

H->X

00 4c 00 e8 00 00 ff 00 01 29 02 ff fe 02 03 00 1e 00 19 00 04 00 13 00 02 00 08 00 08 00 02 00 65 00 0f 00 01 0b 00 65 00 02 00 00 03 00 33 00 1d 00 03 27 7e 00 03 08 00 01 27 17 00 05 10 00 04 36 00 27 18 00 07 10 00 04 37 04 33 00

Example: SIP message from the SIP stack:

INVITE sip:10.10.12.33:5060 SIP/2.0

Via: SIP/2.0/UDP 10.10.12.32

To: 3600<sip:3600@10.10.12.33:5060>

From: 3300<sip:3300@10.10.12.32:5060>;tag=5188342109d

Contact: 3300<sip:3300@10.10.12.32:5060>

User-Agent: Excel/8.0.76

Call-ID: EXCEL-CSP255.206.4253.370@10.10.12.32

CSeq: 1 INVITE

Content-Type: Application/Multipart

Content-Length: 455

Content-Type: multipart/mixed; boundary="109d=_186=_1223"

--"109d=_186=_1223"

Content-Type: application/SDP

v=0

o=sip 4379 4379 IN IP4 10.10.12.32

s=SIP_Call

c=IN IP4 10.10.12.36

t=2208993053 0

m=audio 10072 RTP/AVP 0

a=rtpmap:0 PCMU/8000

--"109d=_186=_1223"

Content-Type: application/SS7 ISUP; version:EXCEL-UPDF

Content-Transfer-Encoding: binary

03 00 33 00 3f 00 08 27 17 00 05 10 00 04 36 00 27 18 00 07

10 00 04 37 04 33 00 29 36 00 02 00 02 27 92 00 04 0a 0a 0c 24 27 93 00 04 00 00 27 58 27 b0 00 02 01 02 27 b1 00 02 01 01 27 7e 00 03 08 00 00

Important! In the above MIME encoded message the Hex ASCII data that appears after the "Content-Transfer-Encoding: binary" line is actually transmitted in binary, but listed here as Hex ASCII so you can read it.

Received RFS message with UPDF encoded data

All TLVs are in UPDF format.

X->H

00 a5 00 2d 00 04 ff 00 01 0d 03 00 01 02 00 33 01 03

00 33

00 91 00 10 27 4e 00 02 00 05 27 7e 00 03 08 0000 29

19 00 05 33 36 30 30 00 29 1b 00 0c 31 30 2e 31 30 2e

31 32 2e 33 33 00 29 1c 00 04 00 00 13 c4 29 23 00 05

33 33 30 30 00 29 25 00 0c 31 30 2e 31 30 2e 31 32 2e

33 32 00 29 26 00 04 00 00 13 c4 27 18 00 07 10 00 04

37 04 33 00 27 17 00 05 10 00 04 36 00 27 94 00 04 0a

0a 0c 24 27 95 00 04 00 00 27 58 27 b0 00 02 01 02 27

b1 00 02 01 01 27 92 00 04 0a 0a 0c 24 27 93 00 04 00

00 27 58

Enabling UPDF TLVs per Call

The following is an example of a Per Call request of a UPDF encoded message.

VoIP Configure message

This message does not configure the UPDF tunnel mode.

H->X

00 21 00 ee 00 0f ff 00 00 00 00 04 01 c8 00 01 04 02

6a 00 01 04 02 6b 00 01 02 02 64 00 04 0a 0a 0c 21

Route Control message from the host

At the end of the sample Route Control message below the TLV to enable UPDF is 0x2936 and value is 0x02.

H->X

00 52 00 e8 00 00 ff 00 01 29 02 ff fe 02 03 00 1e 00

19 00 04 00 13 00 02 00 08 00 08 00 02 00 65 00 0f 00

01 0b 00 65 00 02 00 00 03 00 33 00 23 00 04 27 7e 00

03 08 00 01 27 17 00 05 10 00 04 36 00 27 18 00 07 10

00 04 37 04 33 00 29 36 00 02 00 02

This message results in the following SIP message sent from the SIP stack with MIME encoded Session Description Protocol (SDP).

INVITE sip:10.10.12.33:5060 SIP/2.0

Via: SIP/2.0/UDP 10.10.12.32

To: 3600<sip:3600@10.10.12.33:5060>

From: 3300<sip:3300@10.10.12.32:5060>;tag=5188342109d

Contact: 3300<sip:3300@10.10.12.32:5060>

User-Agent: Excel/8.0.76

Call-ID: EXCEL-CSP255.206.4253.370@10.10.12.32

CSeq: 1 INVITE

Content-Type: Application/Multipart

Content-Length: 455

Content-Type: multipart/mixed; boundary="109d=_186=_1223"

--"109d=_186=_1223"

Content-Type: application/SDP

v=0

o=sip 4379 4379 IN IP4 10.10.12.32

s=SIP_Call

c=IN IP4 10.10.12.36

t=2208993053 0

m=audio 10072 RTP/AVP 0

a=rtpmap:0 PCMU/8000

--"109d=_186=_1223"

Content-Type: application/SS7 ISUP; version:EXCEL-UPDF

Content-Transfer-Encoding: binary

03 00 33 00 3f 00 08 27 17 00 05 10 00 04 36 00 27 18 00 07

10 00 04 37 04 33 00 29 36 00 02 00 02 27 92 00 04 0a 0a 0c

24 27 93 00 04 00 00 27 58 27 b0 00 02 01 02 27 b1 00 02 01

01 27 7e 00 03 08 00 00

--"109d=_186=_1223"--

Important! In the above MIME encoded message the Hex ASCII data which appears after the "Content-Transfer-Encoding: binary" line is actually transmitted in binary but listed here as Hex ASCII so you can read it.

Received RFS message with UPDF encoded data.

X->H

00 ab 00 2d 00 00 ff 00 01 0d 03 00 01 00 00 33 01 03

00 33

00 97 00 11 27 4e 00 02 00 05 27 7e 00 03 08 00 00 29

19 00 05 33 36 30 30 00 29 1b 00 0c 31 30 2e 31 30 2e

31 32 2e 33 33 00 29 1c 00 04 00 00 13 c4 29 23 00 05

33 33 30 30 00 29 25 00 0c 31 30 2e 31 30 2e 31 32 2e

33 32 00 29 26 00 04 00 00 13 c4 27 18 00 07 10 00 04

37 04 33 00 27 17 00 05 10 00 04 36 00 27 94 00 04 0a

0a 0c 24 27 95 00 04 00 00 27 58 27 b0 00 02 01 02 27

b1 00 02 01 01 29 36 00 02 00 02 27 92 00 04 0a 0a 0c

24 27 93 00 04 00 00 27 58

See Universal Protocol Data Format.
Session-Initiation Protocol. A signaling protocol used for establishing sessions in an IP network. A session could be a simple, two-way telephone call, or it could be a collaborative multi-media conference session.
Tag-Length-Value block. A standardized block that allows data to inserted in a standard way into API messages.
Voice over Internet Protocol. The delivery of voice information in digital form in discrete packets rather than in the traditional circuit-committed protocols of the public-switched telephone network (PSTN).
Real-Time Transport Protocol. Supports transport of real-time data like interactive voice and video over packet-switched networks.
See Signaling System Number Seven.
See Integrated Services Digital Network User Part.
American Standard Code for Information Interchange
See Request For Service.