Steve,<br><br>Your configuration is correct, and it's the way I'd recommend doing it. With only a single server in the CMG you lose redundancy.<br><br>If you do <br><br>show gatekeeper endpoints<br><br>you can see the port that the CCM uses to register that GK Trunk. For each cluster you should see three devices with three different ports. It sounds like you see that just fine. If you send an H225 Setup to any of those ports then the call should work (regardless of the source of the H.225 setup).<br>
<br>Can you try resetting the GK Trunk? Maybe disable and enable the GK. The last resort would be to restart the CCM service on the three nodes in question.<br><br>When you add the Trunks to CCM there should be an H225 process started on each of the appropriate nodes that handles the inbound call. It sounds like for some reason this isn't working on your servers. This could be broken for a number of reasons, but the resetting and restarting should take care of it.<br>
<br>If not, then you might need to dig deeper into the traces or open a TAC case.<br><br>-Jason<br><br><div class="gmail_quote">On Tue, Apr 28, 2009 at 5:14 PM, <span dir="ltr"><<a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><font size="2" face="sans-serif">You've all been very helpful in the
past and I'm thinking this should be another fun one to answer.</font>
<br>
<br><font size="2" face="sans-serif">Three clusters consisting of 8, 8 and
6 servers. They all use the same pair of gatekeepers. I created
a gatekeeper device pool with a CMG containing 3 servers from each cluster.
I assigned this device pool to the gatekeeper trunk that I built
to each of the gatekeepers. This was fun and exciting as I saw each
of the 3 servers in the CMG register to each of the gatekeepers. Now
I have 9 registered endpoints on each of the gatekeepers.</font>
<br>
<br><font size="2" face="sans-serif">My problem is that the calls work around
33% of the time when routing between clusters. I took a few traces
and found that only when a request hits the publisher server does it succeed
in connecting. When it hits the other 2 registered endpoints, the
call fails(reorder tone).</font>
<br>
<br><font size="2" face="sans-serif">My questions are: </font>
<br>
<br><font size="2" face="sans-serif">Should I rethink my design and register
1 server to the gatekeepers from each cluster?</font>
<br><font size="2" face="sans-serif">What am I missing that would make the
calls fail when hitting the subsequent nodes registered endpoints?</font>
<br>
<br><font size="2" face="sans-serif">My guess is that I'm not going to like
the answer because its right in front of my nose. :)</font>
<br>
<br><font size="2" face="sans-serif">Thanks,</font>
<br><font size="2" face="sans-serif"><br>
Steve Siltman<br>
Assurant Corporate Technology<br>
Network Engineer - Cisco CCVP<br>
Work: 651-361-4752<br>
Cell: 651-336-5563<br>
<a href="mailto:steve.siltman@assurant.com" target="_blank">steve.siltman@assurant.com</a></font>
<p>
</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>Thank you.<br>
</p><hr>
<p></p>
<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></blockquote></div><br>