[cisco-voip] Call Routing for sepecarte numbers

[Karen Cheng]

Hey John,

Not sure if you still need some advice on this.

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.

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.

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.

Example:

dial-peer cor custom
 name ISDN-1XXXX
 name ISDN-54XXX
!
!
dial-peer cor list ISDN-1XXXX
 member ISDN-1XXXX
!
dial-peer cor list ISDN-54XXX
 member ISDN-54XXX
!

dial-peer voice 1101 pots
 trunkgroup ISDN_3361XXXX
 corlist outgoing ISDN-1XXXX
 translation-profile outgoing Drop-0-Called
 destination-pattern 0T
 direct-inward-dial
 forward-digits all
!
dial-peer voice 1102 pots
 trunkgroup ISDN_3845XXXX
 corlist outgoing ISDN-54XXX
 translation-profile outgoing Drop-0-Called
 destination-pattern 0T
 direct-inward-dial
 forward-digits all
!
dial-peer voice 2101 voip
 corlist incoming ISDN-1XXXX
 description Incoming VoIP DialPeer
 answer-address 1....
 voice-class codec 1
 voice-class sip transport switch udp tcp
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte h245-signal h245-alphanumeric
 no vad
!
dial-peer voice 2102 voip
 corlist incoming ISDN-54XXX
 description Incoming VoIP DialPeer
 answer-address 54...
 voice-class codec 1
 voice-class sip transport switch udp tcp
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte h245-signal h245-alphanumeric
 no vad



Regards

Karen

On Fri, Feb 18, 2011 at 11:43 AM, Daniel <dan.voip at danofive.id.au> wrote:

> John,
>
> 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.
>
> 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.
>
> I don't think you can route on the source, will have a think about it.
>
> cheers,
>
> Dan
>
>
>
>   On Fri, Feb 18, 2011 at 11:16 AM, <John.VanLaecke at ghd.com> wrote:
>
>>  Hello all,
>>
>> I have 2 x isdn 30's at a side with 2 different in dial ranges.
>> but on the outgoing call if i sent the calling number to the wrong isdn, I
>> get an unallocated number error from the carrier.
>> Is there any way to send the call to the correct line?
>>
>>
>>
>>
>> Regards,
>> *
>> John Van Laecke **
>> *
>> _____________________
>> 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 http://www.ghd.com/emaildisclaimer.html .
>> _____________________
>> This e-mail has been scanned for viruses by MessageLabs.
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110226/f8864b81/attachment.html>