<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>Thanks alot Sir. You surely cleared my confusion :-)<br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Paul <asobihoudai@yahoo.com><br><b><span style="font-weight: bold;">To:</span></b> Cisco Voip <cisco_newbie@yahoo.com>; "matthew@ciscovoiceguru.com" <matthew@ciscovoiceguru.com><br><b><span style="font-weight: bold;">Cc:</span></b> "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net><br><b><span style="font-weight: bold;">Sent:</span></b> Tue, February 8, 2011 11:03:24 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [cisco-voip] E1
trunk<br></font><br>
Now we're just getting into semantics. . .<br>if you mean can remote CCME boxes make calls out of a remote office? Yeah sure <br>they can...if you mean can a CCME box physically control the remote E1 PRI's <br>d-channel? No, that's probably not going to happen.<br><br><br>________________________________<br>From:Cisco Voip <<a ymailto="mailto:cisco_newbie@yahoo.com" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>><br>To:Paul <<a ymailto="mailto:asobihoudai@yahoo.com" href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>>; "<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>" <br><<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>><br>Cc:"<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a
ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Sent: Tue, February 8, 2011 9:59:57 AM<br>Subject: Re: [cisco-voip] E1 trunk<br><br><br>Dear Sir, <br><br>Am i correct in my assumption that, a remote CME cant seize a remote E1 channel <br>? I know this sounds stupid but just need to confirm this point.<br><br>Can you kindly confirm it <br><br><br><br><br>________________________________<br>From:Paul <<a ymailto="mailto:asobihoudai@yahoo.com" href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>><br>To:Cisco Voip <<a ymailto="mailto:cisco_newbie@yahoo.com" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>>; "<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>" <br><<a ymailto="mailto:matthew@ciscovoiceguru.com"
href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>><br>Cc:"<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Sent: Tue, February 8, 2011 10:13:40 PM<br>Subject: Re: [cisco-voip] E1 trunk<br><br>Making calls out of the E1 PRI remotely is perfectly doable AFAIK. You just have <br><br><br>to be careful about your voip dialpeers. I don't remember any requirements for <br>CCME to have local trunks but then again, I don't think I'd design a system that <br><br><br>way since all of your PSTN connectivity will die as soon as your WAN dies.<br><br><br><br>________________________________<br>From:Cisco Voip <<a ymailto="mailto:cisco_newbie@yahoo.com" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>><br>To:Paul <<a
ymailto="mailto:asobihoudai@yahoo.com" href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>>; "<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>" <br><<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>><br>Cc:"<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Sent: Tue, February 8, 2011 8:39:04 AM<br>Subject: Re: [cisco-voip] E1 trunk<br><br><br>Sir your assumptions are 100% correct. Sorry if i didnt ask the question <br>properly, but even then i am able to conclude that there is no way to seize a <br>channel of E1 PRI remotely. <br><br><br>Thanks
alot<br><br><br><br><br>________________________________<br>From:Paul <<a ymailto="mailto:asobihoudai@yahoo.com" href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>><br>To:Cisco Voip <<a ymailto="mailto:cisco_newbie@yahoo.com" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>>; "<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>" <br><<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>><br>Cc:"<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Sent: Tue, February 8, 2011 7:32:41 PM<br>Subject: Re: [cisco-voip] E1 trunk<br><br>The problem here is that you haven't provided a full scope
of your <br>infrastructure.<br><br>I have spoken about your design with these assumptions:<br>One E1 PRI at HQ using CCME<br>branch offices have no trunks analog or digital.<br>branch offices using CCME<br>Four offices all using CCME with solid connectivity amongst the four office with <br><br><br><br><br>either meshed/hub-spoke topology<br><br><br><br><br>________________________________<br>From:Cisco Voip <<a ymailto="mailto:cisco_newbie@yahoo.com" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>><br>To:"<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>" <<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>><br>Cc:Paul <<a ymailto="mailto:asobihoudai@yahoo.com" href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>>; "<a ymailto="mailto:cisco-voip@puck.nether.net"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <br><<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Sent: Tue, February 8, 2011 3:46:54 AM<br>Subject: Re: [cisco-voip] E1 trunk<br><br><br>Dear Sir, <br><br>Did you mean that if i have a FXO at my HQ, i shall be able to seize it on a <br>remote CME according to the dial peer you defined ? i thought it certainly is <br>not possible since, CME shall collect all the digits prior before sending it to <br>remote router right ?<br><br>How can it seize a trunk when the digit collection is not complete ?<br><br><br><br><br>________________________________<br>From:"<a ymailto="mailto:matthew@ciscovoiceguru.com" href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>" <<a ymailto="mailto:matthew@ciscovoiceguru.com"
href="mailto:matthew@ciscovoiceguru.com">matthew@ciscovoiceguru.com</a>><br>To:Cisco Voip <<a ymailto="mailto:cisco_newbie@yahoo.com" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>><br>Cc:Paul <<a ymailto="mailto:asobihoudai@yahoo.com" href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>>; "<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <br><<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Sent: Tue, February 8, 2011 2:41:49 AM<br>Subject: Re: [cisco-voip] E1 trunk<br><br><br>To my knowledge this is not possible with a PRI. If you had analog trunks (FXO) <br>you could have a dial peer with a destination pattern of 9 and forward digits of <br><br><br><br><br><br>0. When a user pressed 9, it would match, seize a trunk, and provide dial tone <br>from the
carrier.<br><br>It sounds like you are trying to make CME function as a key system.<br><br>Sent from my iPhone<br><br>On Feb 8, 2011, at 1:57 AM, Cisco Voip f <<a ymailto="mailto:cisco_newbie@yahoo.com" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>> wrote:<br><br><br>Sorry Sir, i forgot that. <br>> <br>>HQ is also running CME(7.x). But sir the issue is, when the user will press 9 on <br>><br>><br>><br>><br>><br>>branch router, CME will still collect all the digits and then forward it out to <br>><br>><br><br><br><br>>HQ right ? how can it possibly seize the channel before hand ? let me clear the <br><br><br><br><br><br>>requirement so that there is no ambiguity, <br>><br>> <br>>When the user press 9 in any branch, a channel of E1 trunk (in HQ) should be <br>>allocated to him. Is this possible ?<br>><br>><br>><br>><br>________________________________<br>From:
Paul <<a ymailto="mailto:asobihoudai@yahoo.com" href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>><br>>To: Cisco Voip <<a ymailto="mailto:cisco_newbie@yahoo.com" href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>>; <a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>>Sent: Mon, February 7, 2011 2:14:34 PM<br>>Subject: Re: [cisco-voip] E1 trunk<br>><br>><br>>Use a voip dial-peer.<br>><br>><br>>If user dials X, then session target ipv4:<HQboxip><br>><br>><br>>make sure you have enough DSPs to transcode sessions across the WAN.<br>><br>><br>>This of course brings the question...what the heck is the HQ running?<br>><br>><br>><br>________________________________<br>From:Cisco Voip <<a ymailto="mailto:cisco_newbie@yahoo.com"
href="mailto:cisco_newbie@yahoo.com">cisco_newbie@yahoo.com</a>><br>>To:<a ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>>Sent: Mon, February 7, 2011 10:53:14 AM<br>>Subject: [cisco-voip] E1 trunk<br>><br>><br>>Hi all.<br>> <br>>Our customer came up with requirement. They have 1 head office and 3 branches. <br>>All 3 branches are using CME. Headoffice has taken E1 from local telco. Now the <br><br><br><br><br><br>>requirement is,<br>> <br>>When any person in any of 3 branches, dials 9 (access code), one of the E1 <br>>channels should be allocated to him !!! (if none are free, then he should hear <br>>busy tone)<br>> <br>>Is this even possible ? how can a remote CME router can do that ?<br>><br>><br>><br>_______________________________________________<br>>cisco-voip mailing list<br>><a
ymailto="mailto:cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>><br><br><br> <br></div></div>
</div><br>
<hr size=1>The fish are biting.<br>
<a href="http://us.rd.yahoo.com/evt=49679/*http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php?o=US2140&cmp=Yahoo&ctv=Q107Tagline&s=Y&s2=EM&b=50"> Get more visitors</a> on your site using <a href="
http://us.rd.yahoo.com/evt=49679/*http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php?o=US2140&cmp=Yahoo&ctv=Q107Tagline&s=Y&s2=EM&b=50">Yahoo! Search Marketing.</a></body></html>