Genesys Trunkgroups for Outbound

[PFCCWA]

Hello,

I am wondering, do we need a primary and backup trunkgroup for outbound.
We are using media server/sip/rm/ocs 8 for outbound dialling.
We operate using an nlb cluster ip for resource manager which both trunk groups use but am wondering if there is any point in having both?
However what would happen if the trunkgroup became out of service?? Should a second one automatically take over?

Thanks,
Wasim

[Flávio]

HI,

according to the release notes you should create the backup trunk group because of that:

- SIP Server now correctly applies the Active Out-of-Service detection mechanism to DNs of type Trunk Group.

That was implemented in version: 8.0.400.90

i would implemente both and make a few tests to double check.

if you have problems please post the logs so we can move a little bit further on that.

cheers,

[bublepaw]

Hi,

Could You be more specific - trunk or trunk group. "Trunk" is used to reach number outside SIP Server while "trunk group" is used to communicate with RM to get resources for CPD. You can have multiple trunk and system will select automaticaly one that is need/available. Trunk group object is defined in campaign group (it can be different for each campaign) but there is no notion of backup trunk group. If You log into logs You will see that trunk group object is used as source for events used for dialing outbound calls (MakePredictiveCall has Trunk Group as ThisDN field).

[PFCCWA]

I am referrring to trunkgroups which are used in an outbound IP environment.
Genesys need to update their documentation, I have found this within their sipserver 8.0 deployment guide, trunk group section:
[i]Limited features.
The features available to Trunk
Group DNs are limited by design.
For example:
 No active out-of-service
detection.
 No primary/backup redundancy.[/i]

and

[i]Note: Trunk Group DNs cannot be placed out of service. If a Trunk Group DN
does not respond to an INVITE, the DN remains available for further
call attempts.[/i]

yet the release notes suggest it can be done?!?
From reading the documentation, we should configure 1 trunk group, pointing to the RM cluster IP, in which case should one resource manager become unresponsive the trunk group continues to use this IP to connect with backup RM?

[bublepaw]

PFCCWA You are right. SIP will continue to talk to RM through virtual IP

[IF]

Also the documentation is wrong in the fact that Trunk Group DN does not support active out of service detection. It actually does, not sure if this has been included in the release notes though.