If the phone is hanging off the CME, you would just configure it on CME.<br><br>You then have a route pattern that points all calls with 43XX (or whatever) to a trunk that goes to CME. <br><br>Easy peesy.<br><br>Unless you are trying to accomplish something else with the phone?
<br><br><br><br><br>Jonathan<br><br><div><span class="gmail_quote">On 12/11/06, <b class="gmail_sendername">Robert Kulagowski</b> <<a href="mailto:bob@smalltime.com">bob@smalltime.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In our deployment, we use SRST for when the WAN link goes out. SRST is<br>kind of feature-limited, but the good part is that it doesn't need a<br>whole lot of configuration.<br><br>I'm just starting to go through the docs for CME, but as I understand
<br>it, there's a whole lot more configuration that has to be done to get<br>phones working in CME mode. If I create a phone in Call Manager, is<br>there anything that will allow me to create the same phone in CME, or am
<br>I going to be performing administration on two separate devices in that<br>instance?<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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br>