<div>Hi Bob,</div>
<div> </div>
<div>What are the translations you are applying?</div>
<div> </div>
<div>I notice your dial peer is inbound and outbound... </div>
<div> </div>
<div>The translations arent stripping off something they shouldnt and then sending it off to the GK?</div>
<div> </div>
<div>Have you debugged on the gateway and gatekeeper to see the H.225 call setups? </div>
<div> </div>
<div>Cheers,</div>
<div> </div>
<div>Tim<br><br> </div>
<div><span class="gmail_quote">On 7/24/08, <b class="gmail_sendername">Bob</b> <<a href="mailto:bobsjunkmail@bellsouth.net">bobsjunkmail@bellsouth.net</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div><span><font face="Arial">The actual problem is caused in the gatekeeper. A user in a CME or a call manager dials an on net call. I send the request to a gatekeeper via RAS. If the dialed DN is 17727331, and there is a CME somewhere that has registered to the gatekeeper and includes 7331 as a E164 ID, the gatekeeper matches the last 4 digits of 17727331. </font></span></div>
<div><span><font face="Arial"></font></span> </div>
<div><span><font face="Arial">This results in the the call being sent to whatever CME (gateway) that registered 7331 (which in this example is at the endpoint that registered 1299 as it's tech prefix), rather than the gateway that 1772 calls should be sent to. <em>(gw ipaddr <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://10.47.18.120/" target="_blank">10.47.18.120</a> 1720 gw-type-prefix 1772* gw ipaddr) </em>I guess I don't understand why the gatekeeper is matching based on the last four digits of the dialed number. </font></span></div>
<div><font face="Arial" size="2"></font><font face="Arial" size="2"></font> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div><span class="q">Bob,<br><br>I understand what you are asking, although I do not have the answers to the<br>question you are asking I do have a solution to you problems.<br><br>I have in other implementations started with 10 digit DNs. The enables the<br>
ability to have specific DNs for are the DID phones. Then to have the dial<br>plan you currently desire, you could do some digit manipulation. <br><br>For instance, if 7331 is dialed expand to 6077957331<br>If 13027331, translate 1302.... to 607795....<br>
<br>This is a cleaner install over all in my experience. You can even only<br>display the 4 last digits as far as the user is concerned.<br><br><br>Semper Fidelis,<br><br>Dustin Fowler<br>Senior Cisco Consultant<br><br></span>Email: <a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">dustin.s.fowler at gmail.com</a><span class="q"><br>
"KEEPING YOUR BUSINESS HIGHLY AVAILABLE"<br></span></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" 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>