[cisco-voip] IP Communicator RTP Port Negotiation

[Wes Sisk]

CIPC can choose to receive audio on only those ports but the phone will 
choose the port number for the other side.

CM sends SCCP OpenReceiveChannel to CIPC
CIPC sends OpenReceiveChannelAck to CM stating IP and port where it is 
waiting to receive audio

the same happens for the other physical phone side.

The CIPC setting will not affect the port numbers chosen by the physical 
phone.

/Wes

On Tuesday, September 29, 2009 3:26:33 PM, STEVEN CASPER 
<SCASPER at mtb.com> wrote:
> 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?
>  
> Steve
> ************************************
> 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.
> ************************************
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090929/279c1bf3/attachment.html>