Re: ´ð¸´: Re: [Sigtran] TUP\IUP over M3UA.
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
fan.dongming, [email protected] wrote: (Tue, 26 Jun 2007 09:52:05) > > Brian£¬ > I have a question, thanks. > the tup code: > |cic| opc| dpc| > so I think all the bits of cic should be put into the User Protocol > Data field of M3UA and at the same time, 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? > That would be wrong. See RFC 4666 3.3.1: ... User Protocol Data: variable-length octet string The User Protocol Data field contains an octet string of MTP-User information from the original SS7 message, starting with the first octet of the original SS7 message following the Routing Label [7][8][26]. ... The SLS field that CIC shares is part of the routing label. The first octet past the SLS (following the Routing Label) is the first octet of the User Protocol Data. Please don't bring this up again: it is a waste of time. --brian -- Brian F. G. Bidulock [email protected] http://www.openss7.org/