[cisco-voip] E1 trunk

[Cisco Voip]

Sir your assumptions are 100% correct. Sorry if i didnt ask the question 
properly, but even then i am able to conclude that there is no way to seize a 
channel of E1 PRI remotely. 


Thanks alot




________________________________
From: Paul <asobihoudai at yahoo.com>
To: Cisco Voip <cisco_newbie at yahoo.com>; "matthew at ciscovoiceguru.com" 
<matthew at ciscovoiceguru.com>
Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Sent: Tue, February 8, 2011 7:32:41 PM
Subject: Re: [cisco-voip] E1 trunk

The problem here is that you haven't provided a full scope of your 
infrastructure.

I have spoken about your design with these assumptions:
One E1 PRI at HQ using CCME
branch offices have no trunks analog or digital.
branch offices using CCME
Four offices all using CCME with solid connectivity amongst the four office with 

either meshed/hub-spoke topology




________________________________
From:Cisco Voip <cisco_newbie at yahoo.com>
To:"matthew at ciscovoiceguru.com" <matthew at ciscovoiceguru.com>
Cc:Paul <asobihoudai at yahoo.com>; "cisco-voip at puck.nether.net" 
<cisco-voip at puck.nether.net>
Sent: Tue, February 8, 2011 3:46:54 AM
Subject: Re: [cisco-voip] E1 trunk


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/2d3cb3ab/attachment.html>