Voice Gateway - Voip Trunk Group

[Marek (gaman-gt.com)]

Dear Community,

A couple of months ago Cisco gave us a new opportunity to write integrations for Cisco voice gateway - Cisco Unified Communications Gateway Services API Guide (Link). One of the available API’s is XSVC which can be used for route monitoring. The documentation states that it can be used to monitor:

• Trunk groups
• Voip trunk groups

I did some tests in the lab and I was able to write a code that integrates with this service. What is interesting, I was not able to pull any statistic data for voip trunk groups (only configuration changes are visible). I also didn’t find any useful info on how to position this new configuration object compared to sip server groups, individual dial peers. Based on this, here are my questions:

1. Has anyone been able to pull any data for sip voip trunk group?
2. What is the purpose of the new voip trunk group object in relation to the objects that we use in routing definition on voice gateway?

[Jaime Valencia]

Probably want to ask over at DevNet where the APIs are supported.

[Marek (gaman-gt.com)]

@Jaime Valencia 

Thanks, but I think that the questions relate to voice gateway config objects which are "voip trunk groups" not the API or API implementations.  In the VG docs (like command reference) I didn't find much about them and how to use them in production deployments. 

[Rajan]

Hi Marek,

There is no concept of voip trunk groups in Cisco Voice gateways as its applicable only for analog connections like T1, FXO etc. Though voice class server-group can be used to group the trunk IPs for SIP trunks. Even in the document you pointed, i could see only "VoIP trunks" and not voip trunk groups.

//For PSTN trunks, the trunk group is a logical grouping of interfaces with the same signaling characteristics, such as DS1, FXO, or PRI interfaces. The trunk group can have more than one PRI interface and can also support FXO, but you cannot mix FXO and T1/E1 interfaces. The trunk group resource manager supports the logical configuration of trunk groups.

For VoIP trunks, the trunk manager monitors a VoIP trunks by using Internet Control Message Protocol (ICMP) pings. The trunk manager supports up to 1000 trunks.//

HTH
Rajan
Please rate all useful posts by clicking the star below and mark solutions as accepted wherever applicable

[Marek (gaman-gt.com)]

Thanks @Rajan 
Please look at the sample config that is also provided in the same document. It is in the next chapter where you find details on how to set it up:

ip http server
!
call fallback monitor
call fallback icmp-ping count 1 interval 2 timeout 100
!
uc wsapi
source-address 10.1.1.1
provider xcc
remote-url http://test.com:8090/xcc
!
provider xsvc
remote-url 1 http://test.com:8090/xsvc
!
provider xcdr
remote-url 1 http://test.com:8090/xcdr
!
trunk group pri
xsvc
 
voip trunk group 1
xsvc
session target ipv4: 11.1.1.1
!
interface Serial0/1/0:23
isdn switch-type primary-ni
isdn incoming-voice voice
trunk-group pri 

As you can see here we have voip server groups. If you look at the config above, you will see it contains 2 types of trunk groups:

• trunk groups for E1/T1 - highlighted in blue
• voip trunk group - highlighted in red. This one can be configured for SIP or H323.

In my opinion, those are 2 different type of objects. The funny thing is that you can only configure a single IP address under voip trunk group.

[Chester Rieman]

Hi Marek(a year later

        This should still work for xsvc, is your app registering with the GW correctly?
see: https://d1nmyq4gcgsfi5.cloudfront.net/fileMedia/3cc79248-a407-476f-976c-c2c91086b715/Developer%20Guide.pdf
For examples, hope this helps....

[Marek (gaman-gt.com)]

Hi @Chester Rieman 

Thanks for the input. Yes, my app registered to VG correctly and was build based on the Cisco doc. Finally, I dropped the idea of pulling stats using xsvc and did that in a different way. My tests were just PoC to check the capabilities of API.

What is interesting - other services worked as a charm.