I would dedicate my resources to getting the service provider to fix the WAN problem<br><br><div><span class="gmail_quote">On 3/28/07, <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;">Kris Seraphine wrote:<br>> Exactly what problems are you having with MGCP and FXS? I have the same
<br>> type of thing (MGCP FXS for night bells) deployed a few places and never<br>> had a nyproblem.<br><br>MGCP ports on remote site routers unregistering with CM thereby breaking<br>faxing. MGCP process as a whole dying, and having to do a no mgcp /
<br>mgcp on the router to restore functionality.<br><br>The routers are already configured for H.323 for call preservation into<br>and out of SRST mode, so having a solution to the call pickup group was<br>the only thing keeping us with MGCP. And since I had an ATA-188 handy,
<br>it took about 3 minutes to confirm that it worked, and it did.<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>