[cisco-voip] E1 trunk

[matthew at ciscovoiceguru.com]

The fundamental difference is with the way FXO's and PRI's handle outbound calls.  When using an analog loop-start line, when you take the receiver off-hook, you will get a dial tone from the carrier.

For your scenario, you would need to do the following:
1. Define a VoIP dial-peer on HQ to with a destination pattern of 9.  The destination would be the IP address (ideally loopback) of the remote CME system.

2. The remote CME system would have a POTs dial peer with a destination pattern of 9 and forward digits of 0.  You would also define the analog port or a trunk group.

When the user at HQ pressed 9, it would send the call to the remote CME system, match on 9, send 0 digits, and seize the analog port.

HQ -
dial-peer voice 100 voip
destination-pattern 9
session target ipv4:10.10.10.10

CME - 
dial-peer voice 200 pots
destination-pattern 9
port 1/0/8 (or trunk-group NAME]
forward-digits 0

However, it sounds like you're trying to do this with analog. Perhaps there's a TCL script you could write for that function, but I think the PRI will be your biggest restraint.

Let me ask you, why are you trying to set things up as a key system?  Wouldn't it be better to train the users on a new (and more updated) way of interacting with the system?

Matthew



Matthew Berry, CCIE #26721

Email: matthew at ciscovoiceguru.com
Twitter: http://twitter.com/CiscoVoiceGuru
Blog: http://ciscovoiceguru.com

On Feb 8, 2011, at 5:46 AM, Cisco Voip wrote:

> Dear Sir, 
> 
> Did you mean that if i have a FXO at my HQ, i shall be able to seize it on a remote CME according to the dial peer you defined ? i thought it certainly is not possible since, CME shall collect all the digits prior before sending it to remote router right ?
> 
> How can it seize a trunk when the digit collection is not complete ?
> 
> From: "matthew at ciscovoiceguru.com" <matthew at ciscovoiceguru.com>
> To: Cisco Voip <cisco_newbie at yahoo.com>
> Cc: Paul <asobihoudai at yahoo.com>; "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
> Sent: Tue, February 8, 2011 2:41:49 AM
> Subject: Re: [cisco-voip] E1 trunk
> 
> 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/5ed47963/attachment.html>