many thanks for ur reply there few more

Dear Brian

I am a student and doing a project related to SS7oIP

Then I assume that you might actually want to learn something instead

of just being told.

Correct

 To  accomplish  my project I have to achieve the task that What is

 the SS7oIP  rate  generated by each of the following protocols for a

 given VoIP traffic.

 Then I also assume that you do not simply want to be told the answer.

correct

>    M3UA

 M3UA carries in it MTP3 messages (see the DATA message description in

 section 3 of RFC 4666).  MTP3 messages correspond to regular PSTN (not VoIP)

 telephone calls(i totally agree and it should be the case that SS7 messages will be wrap up in the M3UA packets to move from IP network and nothing to do with VoIP except that SIGTRAN (eg M3UA) over head is added in signaling gateway (whether the complete ss7 message is encapsulated or break up into chunks in M3UA??????) ) and are either ISUP messages (call control) or TCAP/SCCP messages

 (INAP queries, LNP(local number portability) dips, location services).  To understand ISUP messaging

 requires understanding how telephone switches communicate with each other for

making telephone calls in the network.  From purely a protocol perspecfic,

 examples can be found in any good book written on telecommunications that has at

 least a section on SS7 (its done once again.

 You will see three books (that are old enough they should be at a

 library) mentioned here:

 http://www.openss7.org/faq13.html

(i have just arranged SS7 by travis Russel 4/ed) 

There is a tutorial on SS7 that many people recommend here:

 http://www.pt.com/tutorials/ss7/  (good one)

 There are better web resources: Google is your friend (I opened ITU-T’s Q.763 but it don’t give the exact value (in bytes) of any of the ISUP message (as there are optional parameters so how you calculate 35 or it used to be 45 when u were studying??) and one more thing that there are 39 messages to be used in different occasion).

 What you need to do is to take the message format for a typical ISUP

call flow IAM, ACM, ANM/CPG, REL, and RLC message and count up the number of

bytes for each and then add(each one separately or individually as IAM will come first and this data will pass on to IP via M3UA and after ,say, 10 minutes when call is finished then the REL will be generated by ss7 and then go to SG and converted in IP via M3UA and go across so if we add 175 altogether in one M3UA header we will miss the over head added by M3UA each time isup message is generated ) in the overhead of the M3UA DATA message (what after that as I have to know about the rate (and rate is a quantity with respect to time and please tell that what effect does the length of call will put on isup message and on M3UA message)).  The IAM is

difficult as it can contain many optional parameters that depend upon

 the specific country of operation, the features associated with the call,

 and the position in the switching hierarchy.  IAM message use to be about 45

 bytes in Canada back when I used to do network engineering, but LNP and other

 things have probably raised that to about 60 bytes.  The other mesages do no

 normally carry many optional parameters except the REL.  Note that unsuccessful

 calls also use almost as many messages (but there are still isup messages flowing between nodes during ANM and REL what about them??).  All in all the order-of-manitude

 rule of thumb (please do tell me where you got this rule of thumb from although I agree that typical ISUP messages(for a typical call) are 5 so I can use this as the basis of taking 5 messages) used to be to estimate that a call takes 5 messages and that the

 average length of the messages is 35 bytes(is this a rule of thumb as well and if so where you get this as well????) (I can't remember whether that

 included the FSN/BSN and RL, I'm pretty sure it did (but fsn/bsn are part of every signaling unit and MSU???)) so about 175 bytes per call ( so u are saying that if call is ,let say, for 10 minutes so it has the same number of bytes generating as for the one which last for ,say, 20 minutes).

 

If you need refined numbers you would have to actually capture SS7 or

 M3UA

traffic from a real network and analyze it statistically or using a

 traffic

model.  Modelling of traffic in a telephone network is an entire field

 of

study.

 

>    M2UA

 

M2UA carries a little more of the SS7 message in the MAUP data (it

 includes

FSN/BSN whereas M3UA does not (are these fsn/bsn form SIGTRAN protocols or the one with the Signaling Units of SS7 because SU have fsn/bsn as fixed part of it???  And above you have written that in 35 bytes fsn/bsn are included for isup messages so if they do then how come after reaching at M3UA they are detached from it)).  FSN/BSN are 2 bytes for each message.

See section 3 in RFC 3331.

 

 

>    M2PA

 

M2PA does not carry FSN/BSN from the SS7 message, but adds its own in

 the User

Data message whose format is given in section 2.3.1 of RFC 4165.

 

>    Need your help and guidance

>    hope to get reply soon

 

If you need more guidance, I suggest that you consult with the people

 at

your learning institution that assigned the project to you (the project is assigned to me by my institution but those people has told me straight that they have very little or no knowledge of this and I took it as a challenge moreover the time given to me for this is very short but I am still very much confident that I will be able to do this in time) 

 

 

 

I would like to thank you for your sincere help as this mail helps me a lot in making my concepts clearer 

and also for not telling the answer straight away.

 Hope you will keep on helping me during this project.

KR

ALI

       
---------------------------------
Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when.

_______________________________________________
Sigtran mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/sigtran