RE: TUP\IUP over M3UA.

"Haresign Lincoln" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <849535E338E99741B7F7413F73253EDB06A2E11E@us-nj-mail1.comverse.com>
TUP is still being used in France.

Regards,
Lincoln 

-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]] 
Sent: Monday, June 25, 2007 9:48 AM
To: Igor Fedotov
Cc: [email protected]
Subject: Re: [Sigtran] TUP\IUP over M3UA.

Igor,

First, can you point to somewhere in the world where TUP is still used?

Next, can you indicate who in that part of the world will be running TUP
over M3UA?

Then, move the 4 bits of the CIC that normally overlap into the SLS
field of the SS7 routing label into the SLS field in the Protocol Data
parameter of M3UA and leave the other 8 bits of the CIC in the User
Protocol Data field of M3UA, just as is done in SS7 between the routing
label and the SIF.

--brian

Igor Fedotov wrote:                               (Mon, 25 Jun 2007
17:09:47)
> 
> Can anyone explain how SS7 TUP messages are transported over M3UA?
> The problem is in the mapping TUP Routing Label to M3UA message. Am I 
> right that OPC\DPC from it are mapped to Origination Point Code and 
> Destination Point Code fields of Protocol Data parameter of M3UA Data
message? But where should I put CIC?
> Is it mapped to some fields of Protocol Data parameter or is it 
> encoded right before the TUP message?
> If the second case is correct - how CIC padding to integral number of 
> octets ( as it is 12 bit long ) is performed?
> Thanks in advance.
> 
> --
> Best regards,
>  Igor                          mailto:[email protected]
> 
> 
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/sigtran

--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/

_______________________________________________
Sigtran mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/sigtran
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.