I think UDP 69 for TFTP is what u have to open, cause in SRST the Phone pushes the Config to the SRST GW<div><br></div><div>cheers<br><br><div class="gmail_quote">2011/7/30 Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">UDP 2000 for SCCP you mean?<br>
<br>
Sent from my iPhone<br>
<br>
On Jul 30, 2011, at 11:22 AM, Nick Matthews <<a href="mailto:matthnick@gmail.com">matthnick@gmail.com</a>> wrote:<br>
<br>
> I think you also want the TFTP UDP port open. Although SRST may<br>
> bypass TFTP configs all together, so it could just be port 2000. If<br>
> you've got any SIP phones 5060 as well. CME/SRST will use UDP by<br>
> default rather than TCP like CUCM.<br>
><br>
> -nick<br>
><br>
> On Fri, Jul 29, 2011 at 3:11 PM, AbdusSaboor Khan <<a href="mailto:saboor.khan@gmail.com">saboor.khan@gmail.com</a>> wrote:<br>
>> Yes we use 2000<br>
>><br>
>> call-manager-fallback<br>
>> max-conferences 8 gain -6<br>
>> transfer-system full-consult<br>
>> limit-dn 7942 4<br>
>> limit-dn 7962 22<br>
>> limit-dn CIPC 5<br>
>> timeouts interdigit 5<br>
>> ip source-address 10.224.xx.xx port 2000<br>
>> max-ephones 40<br>
>> max-dn 120 preference 2<br>
>> system message primary SRST mode<br>
>> system message secondary SRST mode<br>
>> transfer-pattern 2....<br>
>> default-destination 22550<br>
>> voicemail 9xxxxxxxxxx<br>
>> no huntstop<br>
>> alias 1 22550 to 22550 preference 1<br>
>> call-forward pattern .T<br>
>> call-forward busy 9xxxxxxxxxx<br>
>> call-forward noan 9xxxxxxxxxx timeout 20<br>
>> time-zone 5<br>
>><br>
>><br>
>><br>
>> On Fri, Jul 29, 2011 at 2:58 PM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<br>
>>><br>
>>> Just curious, I can't find a TCP/UDP port utilization document for SRST.<br>
>>> I'm guessing all I need is TCP port 2000 open from the phones to the SRST<br>
>>> router. I already have the udp range 16384 32767 open from phones to the<br>
>>> routers to communicate to the gateway as well as some others for DHCP, etc.<br>
>>><br>
>>> Thoughts?<br>
>>><br>
>>> ---<br>
>>> Lelio Fulgenzi, B.A.<br>
>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
>>> Cooking with unix is easy. You just sed it and forget it.<br>
>>> - LFJ (with apologies to Mr. Popeil)<br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> cisco-voip mailing list<br>
>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> cisco-voip mailing list<br>
>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>><br>
>><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>gmail: <a href="mailto:florian.kroessbacher@gmail.com" target="_blank">florian.kroessbacher@gmail.com</a><br><br>
</div>