Alok,

Call setup messages go over "a reliable protocol". If you want to interoperate with anyone else, this is likely to be TPKT/TCP/IP. The philosophy is that call setup needs to work (i.e. better a packet arrives late than never), whereas audio & video data are time critical (i.e. late packets are worse than dropped packets).

Why does call setup info require prioritisation?

Regards, Chris

Alok Dubey (OCS-BLRAKS-AVS) wrote:

hi

im sorry for posing this query out here but i needed this answer asap..

Im basically more of an implementor than a protocol developer and all my job is above the layer 3.. ie socket programming etc.

Right now while going thru the specs, I could not find any reasonable explanation on how u prioritise traffic for call setup?

for eg are u sending callsetup info over RTP ports too..? if yes, i still have to figure out how to use Voice Activity Detection to conserve bandwidth a feature which lets us drop voice packets below a certain db level .., if no this basically means that setting up a call could take a long time and the traffic associated with it cannot be controlled/prioritised..

can anyone refer me to any good specs

Sorry to be wasting ur time on such a query.. but i couldnt think of a better place to pose this question.

Rgds Alok

For help on this mail list, send "HELP ITU-SG16" in a message to
listserv@mailbag.intel.com

-- Dr Chris Purvis -- Development Manager ISDN Communications Ltd, The Stable Block, Ronans, Chavey Down Road Winkfield Row, Berkshire. RG42 6LY ENGLAND Phone: +44 1344 899 007 Fax: +44 1344 899 001

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com