CCM with a Publisher and two subscribers issue

[Todd]

Okay, hoping someone can provide some guidance here.  I have a customer with a Cisco Call Manager setup with HA, so they have a Publisher and two Subscribers.  The issue i'm running into is the Genesys documenation vs what the CCM technical folks say they can do.  This works great if i'm just standing up one TServer as I have NATs to the CTI Managers which are all on the associated Publisher/Subscriber boxes.

However, I need to obviously setup an HA pair (8.1 TServer) to connect to them.  The documenation says they need to provide me seperate IPs vs ports with makes sense to me (at least the ports do).  However, the Cisco techs are saying that they can only have one port (2748) to their CTI Manager. 

So my question is, anyone out there dealt with this type of setup and should they be able to open up a second port per CTI Manager.  If not, what would the solution to this be? 

Thanks in advance for any feedback!!
Todd

[René]

Hi Todd,

I'm not sure what you mean by 'I have NATs to the CTI Managers'... Does it mean that all Cisco boxes - Publisher and 2 Subscribers - are accessible via single IP address only? If that's the case then you can't implement Genesys HA in a standard way. However, you should be able to configure same link on both T-Servers (using different user) and rely on Cisco to provide you connectivity in case of primary CTIManager failure.

If there is IP address available for each Cisco box then you should configure 3 links - each pointing to one box.

EDIT - You can find more info about Cisco CTIManagers and JTAPI here - [url=http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_0_1/ccmsys/a08cti.html#wp1026279]http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_0_1/ccmsys/a08cti.html#wp1026279[/url] and [url=http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/jtapi_dev/7_0_1/jtdch3af.html#wp999624]http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/jtapi_dev/7_0_1/jtdch3af.html#wp999624[/url]

R.

[Todd]

Hey Rene, thanks for the response.  Each Publisher/Subscriber has it's own CTI Manager with their own NAT'd IP.  The problem i'm having is that if i setup one link, i can cannect to each of the boxes individually, both publisher and subscriber.  When i add a second link (link-2-name = subscriber1, link-1-name = publisher) the TServer shows "Out of Service".  I do have unique user names for each link as well, connecting through port 2748.  I'm assuming that isn't the expected behavior.  Just wondering if there is something i'm missing.  Any thoughts?

Thanks,
Todd

[Fra]

Forget publishers, TServer for Cisco connects to subscribers only, as only they host the CTI Manager interface to the JTAPI link.
To set up an HA solution in your architecture you have to configure 1 JTAPI link only per TServer instance, i.e.
- TServer primary --> link-1: IP address of subscriber 1 (CTI Manager 1)
- TServer backup --> link-1: IP address of subscriber 2 (CTI Manager 2)

Indeed, there's a unique combination of IP address - port, however, the port that CTI Managers open on their side is 2748.

Fra

p.s. not sure what you mean with NAT'd IP in this context - whatever IP address is used on the CTI Manager interface must be reached by TServer.

[Todd]

Thanks Fra!  So right now we are "only" connected to the CTI Manager on the Publisher box and that seems to work fine.  My fear is we dont have failover setup to the Subscribers.  So you're saying this isn't how it should work?  If the Publisher is the active instance, will the Subscribers be able to report on everything happening on the Publisher?  I'm assuming yes, but am not a Cisco person at all.

Also, the reason NATs are in the picture is this implementation is with an outsourcer, so they NAT their internal IPs so we can see them.

[Fra]

Todd,

I'm not a Cisco expert, so I don't want to mislead you. As far as I know, publishers are used to host the IP telephony config, whereas the proper call processors are the publishers. So in terms of failover on the Cisco side, you need to have your provider set up the correct failover mechanism between subscribers, if you have more then one.
That doesn't mean that the CTI manager can't run on a publisher at all, however, I'm not sure of how you would imlement a resilient platform.
Also, my understanding is that if you want to support the subscriber failover, you need to have a TServer in HA, as when the subscriber fails over, the CTI manager usually does the same?

Fra

[smile]

i faced with the same question. we have two subscribers and t-server in hot-standby.
do i need to configure two links per t-server or just one?
cucm admin guy tell that all DNs registered on first subscriber and only in case of it failure DN will move to second subscriber.
If i set one link per tserver and my primary tserver failure, then backup tserver became primary and connect to second subscriber which doesn't have DNs registered on it.
deployment guide show two different types of configurations, how to choose correct one?

[Fra]

[quote author=smile link=topic=7669.msg35677#msg35677 date=1385676430]
i faced with the same question. we have two subscribers and t-server in hot-standby.
do i need to configure two links per t-server or just one?
[/quote]
If the subscribers are configured in a failover mode, then you need just one link per T-Server: TS_pri to Sub1 and TS_bac to Sub2.
[/quote]
[quote author=smile link=topic=7669.msg35677#msg35677 date=1385676430]
cucm admin guy tell that all DNs registered on first subscriber and only in case of it failure DN will move to second subscriber.
If i set one link per tserver and my primary tserver failure, then backup tserver became primary and connect to second subscriber which doesn't have DNs registered on it.
deployment guide show two different types of configurations, how to choose correct one?
[/quote]
Although I presume the DNs won't 're-home' to the second subscriber, the newly primary T-Server should be able to register all DNs.

Fra

[smile]

Thanks, Fra!

How i can know "If the subscribers are configured in a failover mode"? Do you know where to look at cucm admin console?

[Fra]

sorry, I don't..