[cisco-voip] Select b channel in a bri ougoing call call

Kelemen Zoltan keli at carocomp.ro
Mon Dec 17 10:09:50 EST 2007


As far as I know, (I have tried it before, but have not found a 
solution) this can't be done. When you are debugging, (and using show 
int. etc.) the separate channels appear as BRIx/x/x:1 and BRIx/x/x:2, 
but they are not addressable as ports in a dial-peer. At least they 
weren't last time I tried. Since a BRI does not have a controller (like 
E1 for PRI) you don't have groups, and if you think about it, you can't 
adress individual PRI channles either (Serialx/x/x:11 for example).

It's a pity, since contrary to a 30 (or 23 for you Americans) channel 
PRI line, it usually DOES matter wich channel you use. But it shows: 
cisco is US, ISDN BRI isn't (popular there, that is).

Your other hope is, that your NT has *some* routing capability.

If somebody does have an answer, I'd be interested as well.

best regards,
  Zoltan

Wes Sisk wrote:
> I know on PRI in IOS you can have multiple pri-group.  If you can do the 
> same on a bri then it is possible but you would have to use h.323 
> between CM and the gateway.  use different prefixes for the calls.  use 
> different dial-peers on the gateway to point to different (?)bri-group?
>
> /Wes
>
> Anthony Kouloglou wrote:
>   
>> Hi all,
>> is it possible to use rules based on a specific patterns so some calls 
>> are directed via the first b channel
>> of a bri vic2-2bri and some others via the second b channel?
>>
>> Thanks
>> Akoul
>> _______________________________________________
>> 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
>   



More information about the cisco-voip mailing list