<br><font size=2 face="sans-serif">The biggest one is keep a very close eye on CPU and memory. We had this working in our lab and once we got more than about 12 calls over the trunk it started having memory leak and CPU issues.</font>
<br>
<br><font size=2 face="sans-serif">Craig<br>
<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Leetun, Rob" <rleetun@co.boulder.co.us></b></font>
<br><font size=1 face="sans-serif">Sent by: cisco-voip-bounces@puck.nether.net</font>
<p><font size=1 face="sans-serif">03/23/2006 11:59 AM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: <cisco-voip@puck.nether.net></font>
<br><font size=1 face="sans-serif"> cc: </font>
<br><font size=1 face="sans-serif"> Subject: [cisco-voip] SIP Trunking in CM 4.1.3 (sr2) Gotchyas to watch out for...</font></table>
<br>
<br>
<br><font size=2 face="Arial">We are getting ready to roll out our first SIP trunk. What are the gotchyas that I should be watching out for?</font><font size=3 face="Times New Roman"> </font>
<p><font size=2 face="Arial">Thanks for the insight!</font><font size=3 face="Times New Roman"> </font>
<p><font size=2 face="Arial">Rob</font><font size=3 face="Times New Roman"> </font><font size=2 face="Courier New">_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</font>
<p>
<p>