<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
CIPC can choose to receive audio on only those ports but the phone will
choose the port number for the other side.<br>
<br>
CM sends SCCP OpenReceiveChannel to CIPC<br>
CIPC sends OpenReceiveChannelAck to CM stating IP and port where it is
waiting to receive audio<br>
<br>
the same happens for the other physical phone side.<br>
<br>
The CIPC setting will not affect the port numbers chosen by the
physical phone.<br>
<br>
/Wes<br>
<br>
On Tuesday, September 29, 2009 3:26:33 PM, STEVEN CASPER
<a class="moz-txt-link-rfc2396E" href="mailto:SCASPER@mtb.com"><SCASPER@mtb.com></a> wrote:<br>
<blockquote cite="mid:4AC22728.9874.0039.0@mtb.com" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2900.3562" name="GENERATOR">
<div>We are testing using IP Communicator 7.03 through a new VPN
security appliance and limiting the audio port range for RTP ports. The
security device is set to pass only these RTP ports. When calling an IP
Telephone audio is not passing in either direction. If we open the RTP
port range up all is well. Is there no negotiation of these ports for
source and destination during call setup? For instance if I specify
ports 32764-32767 should the IP Communicator and the IP Phone negotiate
the use of these ports only during call setup?</div>
<div> </div>
<div>Steve</div>
<pre>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>