[cisco-voip] Add a SIP trunk to Route Group

[Christopher Trown]

On 11/9/2010 3:55 PM, Joe Martini wrote:
> Chris,
> 
> The reason you're not seeing this is due to: "If the route group contains a gateway that uses the QSIG protocol, only gateways that use the QSIG protocol display in the list. If the route group contains a gateway that uses the non-QSIG protocol, gateways that use the controlled intercluster trunks, which are QSIG protocol, do not display in the list.
> 
> If you included the route group in a route list that contains QSIG gateways, the H.323 gateways do not display in the list."
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/b03rtgrp.html
> 
> The workaround is to create a new route group that contains the non-qsig devices and add it to the route list.
> 


     Hmmm...  After trying to add the newly created SIP Route Group and
having zero success, I went to look at the documentation and found this:

If the route list contains a QSIG route group, H.323 route groups do not
display in the drop-down list box. If the route group contains a H.323
route group, QSIG route groups do not display in the drop-down list box.

     at:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/b03rtlst.html#wp1023999

     Bleah...

     Hmmm...  So can the SIP trunk be terminated on another device and
still allow me to do what I want?

Chris...

> 
> On Nov 9, 2010, at 6:51 PM, Cristobal Priego wrote:
> 
> Have you checked the dependency records on the sip trunk to double check what is associated to it ?
> 
> 2010/11/9 Christopher Trown <ctrown at uoregon.edu>
> 
> 
>     Greetings all.
> 
>     This should not be difficult.  I have set up a SIP trunk to an
> Avaya SES server.  I added some specific route patterns during testing
> to some test sets.  I could make calls in either direction.  I have
> removed the route patterns I used for the initial set up and testing.
> Out of desperation, I've even removed the SIP trunk and recreated it.
> 
>     The current route group has just a QSIG trunk in it.  MGCP was used
> for this.
> 
>     I'm using CUCM 7.1.3.3.  When I try to add the SIP trunk, it is not
> listed in the available devices.
> 
>     I must be missing something.  What should I check?
> 
> Chris...
> 


-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ctrown.vcf
Type: text/x-vcard
Size: 236 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101110/0af2c198/attachment.vcf>