From: Devi Mallampalli (Devi.Mallampalli@chubb.com.au)
Date: Thu Sep 09 2004 - 00:00:41 GMT-3
Hi James,
Just to be safe side , it is a good idea to match both RTP as well as
RTCP traffic in your MQC.
Because I think in real life, RTP stream will find it very difficult to
survive with out some sort of signaling , even
the CTI ports such as Soft phones on laptops do need some kind of
signaling back to the CM , before a call get established.
But only scenario, I could think of is a "tail IPTEl site's telephones
turning in to SRST mode in case if they loose their
WAN connectivity to Call Manager at Hub site. In that scenario tail site
phones will continue to work on RTP streams to their local gateway even
if they loose signaling (because WAN to CM is down). But even then it is
important to note that, you are not establishing any new calls , all
SRST mode will be doing is "continuing" the current calls.
Hopefully some one will correct me if I am wrong :-)
Cheers
Devi.
-----Original Message-----
From: James [mailto:james@towardex.com]
Sent: Wednesday, 8 September 2004 6:27 PM
To: ccielab@groupstudy.com
Subject: Popular method of matching voice traffic (qos)
Hi group,
When asked to perform QoS on voice traffic, but without any specifics of
what kind of voice traffic it is (i.e. whether it is sip, h323, etc),
what is the most popular way used in spirit of getting the points in the
lab, to match voice traffic within the MQC syntax?
Is it 'match ip rtp 16384 16383' by the most? Any other popular choices?
Thanks!
-J
-- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net
This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:40 GMT-3