<html><head><base href="x-msg://9/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>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.</div><div><br></div><div>For your scenario, you would need to do the following:</div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>HQ -</div><div>dial-peer voice 100 voip</div><div>destination-pattern 9</div><div>session target ipv4:10.10.10.10</div><div><br></div><div>CME - </div><div>dial-peer voice 200 pots</div><div>destination-pattern 9</div><div>port 1/0/8 (or trunk-group NAME]</div><div>forward-digits 0</div><div><br></div><div>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.</div><div><br></div><div>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?</div><div><br></div><div>Matthew</div><div><br></div><div><br></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Matthew Berry, CCIE #26721<br><br>Email: <a href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a><br>Twitter: <a href="http://twitter.com/CiscoVoiceGuru">http://twitter.com/CiscoVoiceGuru</a><br>Blog: <a href="http://ciscovoiceguru.com">http://ciscovoiceguru.com</a></div></div></span></span>
</div>
<br><div><div>On Feb 8, 2011, at 5:46 AM, Cisco Voip wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Dear Sir,<span class="Apple-converted-space"> </span><br><br>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 ?<br><br>How can it seize a trunk when the digit collection is not complete ?<br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "><br><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold; ">From:</span></b><span class="Apple-converted-space"> </span>"<a href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>" <<a href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>><br><b><span style="font-weight: bold; ">To:</span></b><span class="Apple-converted-space"> </span>Cisco Voip <<a href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>><br><b><span style="font-weight: bold; ">Cc:</span></b><span class="Apple-converted-space"> </span>Paul <<a href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>>; "<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br><b><span style="font-weight: bold; ">Sent:</span></b><span class="Apple-converted-space"> </span>Tue, February 8, 2011 2:41:49 AM<br><b><span style="font-weight: bold; ">Subject:</span></b><span class="Apple-converted-space"> </span>Re: [cisco-voip] E1 trunk<br></font><br><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">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.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">It sounds like you are trying to make CME function as a key system.<br><br>Sent from my iPhone</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br>On Feb 8, 2011, at 1:57 AM, Cisco Voip f <<a rel="nofollow" ymailto="mailto:cisco_newbie@yahoo.com" target="_blank" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>> wrote:<br><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "></div><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Sorry Sir, i forgot that.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">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,</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> </div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">When the user press 9 in any branch, a channel of E1 trunk (in HQ) should be allocated to him. Is this possible ?<br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "><br><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold; ">From:</span></b><span class="Apple-converted-space"> </span>Paul <<a rel="nofollow" ymailto="mailto:asobihoudai@yahoo.com" target="_blank" href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>><br><b><span style="font-weight: bold; ">To:</span></b><span class="Apple-converted-space"> </span>Cisco Voip <<a rel="nofollow" ymailto="mailto:cisco_newbie@yahoo.com" target="_blank" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>>;<span class="Apple-converted-space"> </span><a rel="nofollow" ymailto="mailto:cisco-voip@puck.nether.net" target="_blank" href="mailto:cisco-voip@puck.nether.net"></a><a rel="nofollow" ymailto="mailto:cisco-voip@puck.nether.net" target="_blank" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><b><span style="font-weight: bold; ">Sent:</span></b><span class="Apple-converted-space"> </span>Mon, February 7, 2011 2:14:34 PM<br><b><span style="font-weight: bold; ">Subject:</span></b><span class="Apple-converted-space"> </span>Re: [cisco-voip] E1 trunk<br></font><br><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-size: 12pt; font-family: times, serif; "><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Use a voip dial-peer.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">If user dials X, then session target ipv4:<HQboxip></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">make sure you have enough DSPs to transcode sessions across the WAN.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; ">This of course brings the question...what the heck is the HQ running?</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "><br><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold; ">From:</span></b><span><span class="Apple-converted-space"> </span>Cisco Voip <<a rel="nofollow" class="smarterwiki-linkify" ymailto="mailto:cisco_newbie@yahoo.com" target="_blank" href="mailto:cisco_newbie@yahoo.com"></a><a rel="nofollow" ymailto="mailto:cisco_newbie@yahoo.com" target="_blank" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>></span><br><b><span style="font-weight: bold; ">To:</span></b><span><span class="Apple-converted-space"> </span><a rel="nofollow" class="smarterwiki-linkify" ymailto="mailto:cisco-voip@puck.nether.net" target="_blank" href="mailto:cisco-voip@puck.nether.net"></a><a rel="nofollow" ymailto="mailto:cisco-voip@puck.nether.net" target="_blank" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br><b><span style="font-weight: bold; ">Sent:</span></b><span class="Apple-converted-space"> </span>Mon, February 7, 2011 10:53:14 AM<br><b><span style="font-weight: bold; ">Subject:</span></b><span class="Apple-converted-space"> </span>[cisco-voip] E1 trunk<br></font><br><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "><p>Hi all.</p><div style="padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; min-height: 8pt; height: 8pt; "> <br class="webkit-block-placeholder"></div><p>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,</p><div style="padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; min-height: 8pt; height: 8pt; "> <br class="webkit-block-placeholder"></div><p>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)</p><div style="padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; min-height: 8pt; height: 8pt; "> <br class="webkit-block-placeholder"></div><p>Is this even possible ? how can a remote CME router can do that ?</p></div><br></div></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "></div></div><br></div></div></div><br></div></blockquote><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a rel="nofollow" ymailto="mailto:cisco-voip@puck.nether.net" target="_blank" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br><span><a rel="nofollow" target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br></div></blockquote></div></div></div><br></div></span><br class="Apple-interchange-newline"></blockquote></div><br></body></html>