[cisco-voip] E1 trunk
Paul
asobihoudai at yahoo.com
Tue Feb 8 09:25:14 EST 2011
If you're using H.323 for signaling, then it should be simple. User dials a
destination pattern of X, send to IP address Y.
It will NOT seize the channel until the users dial a matching pattern for a voip
dial peer. If all 30 channels are seized, branch users will encounter a busy
signal at the next call.
________________________________
From:Cisco Voip <cisco_newbie at yahoo.com>
To:Paul <asobihoudai at yahoo.com>; cisco-voip at puck.nether.net
Sent: Mon, February 7, 2011 11:57:50 PM
Subject: Re: [cisco-voip] E1 trunk
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 ?
More information about the cisco-voip
mailing list