<br><font size=2 face="sans-serif">Here is a couple of scenarios that I
need help with.</font>
<br>
<br><font size=2 face="sans-serif">Scenario 1:</font>
<br><font size=2 face="sans-serif">Cisco IP Phones and Avaya phones mixed
at the same location. MGCP router is the go-between. If an
extension is dialed and doesn't live on one system, it forwards the call
to the other system. This works great. What if the extension
doesn't live on either system? I was taking a trace from Call Manager,
on a different issue, and noticed a problem that looks like a call is doing
the above. Without adding specific route patterns and continuing
to use a large 1XXXX pattern to send calls across to Avaya when they don't
exist on Call Manager, can I limit this route loop or stop it from happening
somehow?</font>
<br>
<br><font size=2 face="sans-serif">Scenario 2:</font>
<br><font size=2 face="sans-serif">This one has me perplexed because I'm
not sure why I didn't notice this long ago or how it continues to loop.
The call comes into a remote H.323 gateway and the DNIS is translated
into a DN that lives on Call Manager. The dial-peer looks up the
DN on Call Manager but it doesn't exist. *sigh* We have a route pattern
configured to point all those extensions towards the remote H.323 gateway.
I believe the first office was setup this way and its been copied
for each additional remote office install. We now have 20 offices
that have a route pattern pointing the Internal DN range back out to the
remote H.323 gateway where the phones live physically. I believe
the resolution to this is to remove these internal DN range route patterns.
Call Manager already knows them and doesn't need this route pattern.
Correct? I still don't understand how this could be looping
but it must be looping within the Call Managers. I turned on ISDN
Q931 and VOIP DIALPEER debugs on the router and saw the call come in and
hit the dial-peer to Call Manager. Thats all I saw on the router
but yet the Call Manager had 250 trace files, each 1 meg in size and rolled
after 9 minutes. Digit analysis shows the called number and the extension,
that doesn't exist, over and over and over in just under 1 second intervals.
I'm pretty sure removing this internal DN range route pattern will
resolve this but I'd like to know how its looping.</font>
<br>
<br><font size=2 face="sans-serif">Any suggestions or you've seen this
before would be appreciated. Thanks!</font>
<br><font size=2 face="sans-serif"><br>
Steve Siltman<br>
Assurant Corporate Technology<br>
steve.siltman@assurant.com</font>
<P>
<HR>
This e-mail message and all attachments transmitted with it may contain legally
privileged and/or confidential information intended solely for the use of the
addressee(s). If the reader of this message is not the intended recipient, you
are hereby notified that any reading, dissemination, distribution, copying,
forwarding or other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please notify the sender
immediately and delete this message and all copies and backups thereof.</P>
<P>Thank you.<BR>
<HR>
<P></P>