Is there a way on SipX to strictly define the UDP port range that is
used for RTP packets coming off the SipX server, such as for; MOH,
Voicemail audio, auto-attendant audio, or conferencing audio etc.?

 

I am looking to use the UDP port range detail for an ingress ACL on the
Servers own data switch port, and that coupled with class map and policy
map will hopefully allow me to set QOS bits on the packets coming off
the server. I have the IOS aspect figured out. I would like to make the
UDP port selection on RTP packets restricted to something like 20000 to
40000, but I don't see a way to do it - even hacking up some xml file.

 

Has anyone implemented QOS packet/frame marking using the servers data
switch - successfully?

 

 

Regards,

 

Don McIlvin

Waltham, MA 02451

 


"The information in this electronic mail message is the sender's confidential 
business and may be legally privileged. It is intended solely for the 
addressee(s). Access to this internet electronic mail message by anyone else is 
unauthorized. If you are not the intended recipient, any disclosure, copying, 
distribution or any action taken or omitted to be taken in reliance on it is 
prohibited and may be unlawful."
"The sender believes that this E-mail and any attachments were free of any 
virus, worm, Trojan horse, and/or malicious code when sent. This message and 
its attachments could have been infected during transmission. By reading the 
message and opening any attachments, the recipient accepts full responsibility 
for taking protective and remedial action about viruses and other defects. The 
sender's employer is not liable for any loss or damage arising in any way from 
this message or its attachments."
"In connection with representing sellers and/or buyers in real estate 
transactions, Coldwell Banker Residential Brokerage real estate sales 
associates have absolutely no authority to create binding contractual 
obligations on behalf of a seller or on behalf of a buyer via any written or 
verbal communications including, but not limited to email communications." 
[v1.0.07.109]
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to