[cisco-voip] H323 w/ a PRI and 8 Copper Line for Subtenant
Syed Khalid Ali
khalid_khursheed at hotmail.com
Sat Jun 21 08:02:26 EDT 2008
Greetings,
I did not try with Call Manager, because at that time I did not have that much expertise with Call Manager as compared with cisco IOS gateways. since I am coming from a total data environment.
Regards,
Khalid
> Subject: RE: [cisco-voip] H323 w/ a PRI and 8 Copper Line for Subtenant
> Date: Thu, 19 Jun 2008 15:28:48 -0700
> From: mark.turpin at Calence.com
> To: droush at mckennalong.com; khalid_khursheed at hotmail.com; cisco-voip at puck.nether.net
>
> You could create two route pattern and route list pairs pointing at the h.323 gateway route group.
>
> Use the equivalent of steering codes on the route group member of the route list by setting a prefix on the entry.
>
> When the call arrives at the gateway, strip the prefix off the destination-pattern.
>
> ! for pri customer
> dial-peer voice 100 pots
> destination-pattern 01T
> port 0/0/0:23
> !
> dial-peer voice 200 pots
> destination-pattern 02T
> port 0/1/0
> !
> dial-peer voice 201 pots
> destination-pattern 02T
> port 0/1/1
> !
> etc..
>
> Obviously you'll have more patterns and this assumes you're stripping the 9 but that should illustrate the idea. This eliminates the extra work you'd be doing on the gateway to try and match all your tenant's numbers.....
>
> -mark
>
>
> --
>
> MARK TURPIN | Senior Consultant - UC | Calence / Insight Networking Solutions | calence.com <https://myaccess.calence.com/exchweb/bin/redir.asp?URL=http://www.calence.com/>
> t. 314.656.2315 c. 314.660.5800 f. 314.656.2355 mark.turpin at calence.com
>
> The information contained in this message and any attachment may contain privileged or confidential information protected from disclosure. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this information is strictly prohibited. If you have received this transmission in error, please notify the sender immediately by replying to this message and destroying the original and all copies. Thank you.
>
> ________________________________
>
> From: cisco-voip-bounces at puck.nether.net on behalf of Roush, David
> Sent: Thu 6/19/2008 3:51 PM
> To: Syed Khalid Ali; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] H323 w/ a PRI and 8 Copper Line for Subtenant
>
>
>
> Thanks Khalid for the link. I will give it a shot. Have you tried doing it w/ translation patterns in Call Manager before sending it to the voice gateway? Also, Can you think of any side effects of using Trunk Groups for the fxo ports in instances like this?
>
>
>
> From: Syed Khalid Ali [mailto:khalid_khursheed at hotmail.com]
> Sent: Thursday, June 19, 2008 4:23 PM
> To: Roush, David; cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] H323 w/ a PRI and 8 Copper Line for Subtenant
>
>
>
> Hi,
>
> I had a similar problem where some of executives had to have a dedicated phone line. However major calls were done via 2 x PRIs. Check this link for mapping out calls to FXO ports:
>
> http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a00801bc341.shtml
>
> I hope this helps!
>
> regards,
>
> Khalid
>
> ________________________________
>
> Date: Thu, 19 Jun 2008 14:15:20 -0400
> From: droush at mckennalong.com
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] H323 w/ a PRI and 8 Copper Line for Subtenant
>
> I'm about to migrate one of our remote offices from an Avaya G3 to Call Manager 4.2(3) and they have a subtenant. Our office calls come/go via a single PRI and the Subtenant uses 8 Analog Lines for their calls. We would like to continue this pattern, but I'm having a hard time figuring out how to route the subtenant's calls out the analog ports. We will be using a 2851 w/ a VWIC2-2MFT for the PRI and 2 x VIC2-4FXO cards for the 8 analog lines. The gateway is going to be setup using H323. I figure I can separate everything using Partitions and Calling Search Spaces, but I can't figure out how to force the subtenant calls out via the fxo ports. My first thought was to setup the gateway as both H323 and MGCP and create separate Route Groups/Route List. Use H323 for PRI and MGCP for the FXO ports. Then create route patterns and assign them to the proper Route List. Another thought was to create a translation pattern for outgoing calls for the subtenant to translate it from 9 to another digit and create a matching dial-peer and send it out the fxo ports. Is there an easier way of handling this?
>
>
>
> Thanks
>
>
> David
>
>
>
> CONFIDENTIALITY NOTICE:
>
> This e-mail and any attachments contain information from
>
> the law firm of McKenna Long & Aldridge LLP, and are
>
> intended solely for the use of the named recipient or
>
> recipients. This e-mail may contain privileged
>
> attorney/client communications or work product. Any
>
> dissemination of this e-mail by anyone other than an
>
> intended recipient is strictly prohibited. If you are not a
>
> named recipient, you are prohibited from any further
>
> viewing of the e-mail or any attachments or from making any
>
> use of the e-mail or attachments. If you believe you have
>
> received this e-mail in error, notify the sender
>
> immediately and permanently delete the e-mail, any
>
> attachments, and all copies thereof from any drives or
>
> storage media and destroy any printouts of the e-mail or
>
> attachments.
>
>
>
> ________________________________
>
> Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it! <http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us>
>
> CONFIDENTIALITY NOTICE:
> This e-mail and any attachments contain information from
> the law firm of McKenna Long & Aldridge LLP, and are
> intended solely for the use of the named recipient or
> recipients. This e-mail may contain privileged
> attorney/client communications or work product. Any
> dissemination of this e-mail by anyone other than an
> intended recipient is strictly prohibited. If you are not a
> named recipient, you are prohibited from any further
> viewing of the e-mail or any attachments or from making any
> use of the e-mail or attachments. If you believe you have
> received this e-mail in error, notify the sender
> immediately and permanently delete the e-mail, any
> attachments, and all copies thereof from any drives or
> storage media and destroy any printouts of the e-mail or
> attachments.
>
>
_________________________________________________________________
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080621/8b1832c9/attachment.html>
More information about the cisco-voip
mailing list