[cisco-voip] UDP 2000 from SRST router to IP phone?

[Matt Slaga (US)]

If you only open 2000, then your secondary and tertiary callmanager
servers will not have heartbeat to the phones.  In some cases, you may
end up with lots of transient connection errors in your event log.



-----Original Message-----
From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca] 
Sent: Thursday, July 05, 2007 10:52 PM
To: Matt Slaga (US); Paul Choi; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] UDP 2000 from SRST router to IP phone?

That's was our understanding, TCP 2000.

I don't think we've ever heard about the sequential ports though. We've
only 
opened up TCP 2000.

----- Original Message ----- 
From: "Matt Slaga (US)" <Matt.Slaga at us.didata.com>
To: "Paul Choi" <asobihoudai at yahoo.com>; "Lelio Fulgenzi" 
<lelio at uoguelph.ca>; <cisco-voip at puck.nether.net>
Sent: Thursday, July 05, 2007 9:09 PM
Subject: RE: [cisco-voip] UDP 2000 from SRST router to IP phone?


> Cisco contends that SCCP uses TCP 2000 - 2002 (one port for each
> CallManager in it's failover list).  Not sure about UDP 2000.
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Paul Choi
> Sent: Thursday, July 05, 2007 9:01 PM
> To: Lelio Fulgenzi; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] UDP 2000 from SRST router to IP phone?
>
> I could be full of shit but I'm pretty sure that SCCP
> uses UDP 2000 to communicate with CCM.
>
>
> --- Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
>> We're just setting up some ACLs and found that while
>> in SRST mode, the SRST router (or at least the
>> loopback address that we bind MGCP to) tried to
>> communicate to the IP phone that was registered. We
>> had not allowed for this and as a result, the call
>> out the gateway was one way audio. But we didn't see
>> any other denies come out of the logs.
>>
>> I see that in the SRST config, it asks for a port,
>> and it is 2000. But it's still wierd to see UDP 2000
>> being used.
>>
>> Can anyone comment?
>>
>> 2d08h: %SEC-6-IPACCESSLOGP: list voice_in_kc denied
>> udp 10.104.122.141(17624) -> 10.104.34.48(2000), 1
>> packet
>>
>>    ^- IP phone              ^- SRST router
>>
>>
>>
>
------------------------------------------------------------------------
> --------
>> Lelio Fulgenzi, B.A.
>> Senior Analyst (CCS) * University of Guelph *
>> Guelph, Ontario N1G 2W1
>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> "Buffalo buffalo Buffalo buffalo buffalo buffalo
>> Buffalo buffalo."      WJR
>> > _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
>
>
>
>
________________________________________________________________________
> ____________
> Yahoo! oneSearch: Finally, mobile search
> that gives answers, not web links.
> http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> -----------------------------------------
> Disclaimer:
>
> This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the
> designated addressee(s) named above only.  If you are not the
> intended addressee, you are hereby notified that you have received
> this communication in error and that any use or reproduction of
> this email or its contents is strictly prohibited and may be
> unlawful.  If you have received this communication in error, please
> notify us immediately by replying to this message and deleting it
> from your computer. Thank you.
>
> 


-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.