[cisco-voip] E1 trunk

[matthew at ciscovoiceguru.com]

To my knowledge this is not possible with a PRI. If you had analog trunks (FXO) you could have a dial peer with a destination pattern of 9 and forward digits of 0. When a user pressed 9, it would match, seize a trunk, and provide dial tone from the carrier.

It sounds like you are trying to make CME function as a key system.

Sent from my iPhone

On Feb 8, 2011, at 1:57 AM, Cisco Voip f <cisco_newbie at yahoo.com> wrote:

> Sorry Sir, i forgot that.
>  
> HQ is also running CME(7.x). But sir the issue is, when the user will press 9 on branch router, CME will still collect all the digits and then forward it out to HQ right ? how can it possibly seize the channel before hand ? let me clear the requirement so that there is no ambiguity,
>  
> When the user press 9 in any branch, a channel of E1 trunk (in HQ) should be allocated to him. Is this possible ?
> 
> From: Paul <asobihoudai at yahoo.com>
> To: Cisco Voip <cisco_newbie at yahoo.com>; cisco-voip at puck.nether.net
> Sent: Mon, February 7, 2011 2:14:34 PM
> Subject: Re: [cisco-voip] E1 trunk
> 
> Use a voip dial-peer.
> 
> If user dials X, then session target ipv4:<HQboxip>
> 
> make sure you have enough DSPs to transcode sessions across the WAN.
> 
> This of course brings the question...what the heck is the HQ running?
> 
> From: Cisco Voip <cisco_newbie at yahoo.com>
> To: cisco-voip at puck.nether.net
> Sent: Mon, February 7, 2011 10:53:14 AM
> Subject: [cisco-voip] E1 trunk
> 
> Hi all.
> 
>  
> 
> Our customer came up with requirement. They have 1 head office and 3 branches. All 3 branches are using CME. Headoffice has taken E1 from local telco. Now the requirement is,
> 
>  
> 
> When any person in any of 3 branches, dials 9 (access code), one of the E1 channels should be allocated to him !!! (if none are free, then he should hear busy tone)
> 
>  
> 
> Is this even possible ? how can a remote CME router can do that ?
> 
> 
> 
> 
> _______________________________________________
> 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/20110208/f0932d56/attachment.html>