<div>Hey John,</div>
<div> </div>
<div>Not sure if you still need some advice on this.</div>
<div> </div>
<div>Previosuly I used dial-peers and cor-lists. I created a voip dial-peer to match on the calling number and created COR-Lists one for each ISDN trunk group where the trunk group contained the ISDN lines individually.</div>
<div> </div>
<div>That way if a calling number was from either 1XXXX or 3361XXXX or 073361XXXX it would only have access to call via the ISDN trunk group ISDN-1XXX which I created.</div>
<div> </div>
<div>It worked a treat and definetely helps if you have multiple ISDN's with different number ranges hanging off the same router. If you have a perfect setup where the external phone number mask is always specificied and correct then that will reduce the number of dial-peers etc that you have to create to match on the calling number. Otherwise you need to create one for every possible scenario such as internal number, external number and external number with national prefix etc etc.</div>
<div> </div>
<div>Example:</div>
<div> </div>
<div>dial-peer cor custom<br> name ISDN-1XXXX<br> name ISDN-54XXX<br>!<br>!<br>dial-peer cor list ISDN-1XXXX<br> member ISDN-1XXXX<br>!<br>dial-peer cor list ISDN-54XXX<br> member ISDN-54XXX<br>!</div>
<div> </div>
<div>dial-peer voice 1101 pots<br> trunkgroup ISDN_3361XXXX<br> corlist outgoing ISDN-1XXXX<br> translation-profile outgoing Drop-0-Called<br> destination-pattern 0T<br> direct-inward-dial<br> forward-digits all<br>!</div>
<div>dial-peer voice 1102 pots<br> trunkgroup ISDN_3845XXXX</div>
<div> corlist outgoing ISDN-54XXX<br> translation-profile outgoing Drop-0-Called<br> destination-pattern 0T<br> direct-inward-dial<br> forward-digits all<br>!</div>
<div>dial-peer voice 2101 voip<br> corlist incoming ISDN-1XXXX<br> description Incoming VoIP DialPeer<br> answer-address 1....<br> voice-class codec 1<br> voice-class sip transport switch udp tcp<br> session protocol sipv2<br>
session target sip-server<br> dtmf-relay rtp-nte h245-signal h245-alphanumeric<br> no vad</div>
<div>!</div>
<div>dial-peer voice 2102 voip<br> corlist incoming ISDN-54XXX<br> description Incoming VoIP DialPeer<br> answer-address 54...<br> voice-class codec 1<br> voice-class sip transport switch udp tcp<br> session protocol sipv2<br>
session target sip-server<br> dtmf-relay rtp-nte h245-signal h245-alphanumeric<br> no vad</div>
<div> </div>
<div> </div>
<div> </div>
<div>Regards</div>
<div> </div>
<div>Karen<br><br></div>
<div class="gmail_quote">On Fri, Feb 18, 2011 at 11:43 AM, Daniel <span dir="ltr"><<a href="mailto:dan.voip@danofive.id.au">dan.voip@danofive.id.au</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><font size="2"><font face="verdana,sans-serif">John,</font></font>
<div><font size="2"><font face="verdana,sans-serif"><br></font></font></div>
<div><font size="2"><font face="verdana,sans-serif">We had this issue with a major project that had two ISDN trunks spread across two sites. We ended up using business continuity plan with the carrier where the DID range was spread across both trunks.</font></font></div>
<div><font size="2"><font face="verdana,sans-serif"><br></font></font></div>
<div><font size="2"><font face="verdana,sans-serif">You could manually create CSSs, so that this phone uses this route list and this phone uses that route list. Or look at local route groups and different device pools. A device pool for the first ISDN range and a device pool for the second ISDN range. That way you point to different route groups on each phone still manual reconfiguration required though.</font></font></div>
<div><font size="2"><font face="verdana,sans-serif"><br></font></font></div>
<div><font size="2"><font face="verdana,sans-serif">I don't think you can route on the source, will have a think about it.</font></font></div>
<div><font size="2"><font face="verdana,sans-serif"><br></font></font></div>
<div><font size="2"><font face="verdana,sans-serif">cheers,</font></font></div>
<div><font size="2"><font face="verdana,sans-serif"><br></font></font></div>
<div><font size="2"><font face="verdana,sans-serif">Dan</font></font></div>
<div><font size="2"><font face="verdana,sans-serif"><br></font></font></div>
<div><font size="2"><font face="verdana,sans-serif"><br></font></font><br>
<div class="gmail_quote">
<div>
<div></div>
<div class="h5">On Fri, Feb 18, 2011 at 11:16 AM, <span dir="ltr"><<a href="mailto:John.VanLaecke@ghd.com" target="_blank">John.VanLaecke@ghd.com</a>></span> wrote:<br></div></div>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>
<div></div>
<div class="h5"><font size="2" face="sans-serif">Hello all,</font> <br><br><font size="2" face="sans-serif">I have 2 x isdn 30's at a side with 2 different in dial ranges.</font> <br><font size="2" face="sans-serif">but on the outgoing call if i sent the calling number to the wrong isdn, I get an unallocated number error from the carrier.</font> <br>
<font size="2" face="sans-serif">Is there any way to send the call to the correct line?</font> <br><br><br><br><br><font size="2" face="Verdana">Regards,<br><b><br>John Van Laecke </b></font><font color="#5f5f5f" size="2" face="Verdana"><b><br>
</b></font><br>_____________________ <br>This email and all attachments are confidential. For further important information about emails sent to or from GHD or if you have received this email in error, please refer to <a href="http://www.ghd.com/emaildisclaimer.html" target="_blank">http://www.ghd.com/emaildisclaimer.html</a> .<br>
_____________________ <br>This e-mail has been scanned for viruses by MessageLabs.<br><br></div></div>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">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></div><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>