Bryan Stepp

You are correct with your response (using snooper): <property name="DefaultPersistentChatPoolUri">sip:gc-1-persistentchatservice-1@domain.com</property> <property name="PersistentChatPoolUris">sip:gc-1-persistentchatservice-1@domain.com sip:gc-2-persistentchatservice-2@domain.com</property>

Microsoft Skype for Business client has no issues connecting to multiple persistent chat pools - and no additional information/actions is required for the end user of the Microsoft Skype for Business client to connect to these persistent chat rooms on the secondary Pchat server. I was notified by our Linux users that PIDGIN with SIPE wasn't able to join these rooms. So now it looks like we may have a workaround using the Advance settings, but these users will need to run two instances of PIDGIN SIPE...

Microsoft Skype for Business client has no issues connecting to multiple persistent chat pools - and no additional information/actions is required for the end user of the Microsoft Skype for Business client to connect to these persistent chat rooms on the secondary Pchat server. I was notified by our Linux users that PIDGIN with SIPE wasn't able to join these rooms. So now it looks like we may have a workaround using the Advance settings, but these users will need to run two instances of PIDGIN SIPE...

I entered the SIP id of the RegistrarPool of the 2nd Persistent Chat pool into the Group Chat Proxy field. I then connected with my account and was able to see/enter the rooms of that 2nd Persistent Chat pool but not the first/default Persistent Chat pool. This bug turns more into a feature request. Is it possible to define the Group Chat Proxy per persistent chat room when joining or enter multiple Group Chat Proxies that SIPE will attempt to use to connect to persistent chat rooms?

Room list only displays the first 100 rooms. We have about 4,000 persistent chat rooms for our organization. We have a service that displays the ma-chan URI for persistent chat rooms. We then join the channel by using the ma-chan URI in PIDGIN.

I need to run this on our development environment to pull the logs. I will get the logs to you as soon as I can so we can troubleshoot this issue. A quick look over the logging - it looks like I don't even see the discovery of our 2nd persistent chat pool SIP id at all in the debug logs, I only see it checking the first persitent chat pool SIP id. Thank you for looking into it.

Does Pidgin-Sipe support multiple backend persistent chat pools? We have two pools hosting rooms on Skype for Business. When I try to join rooms on the second pool of persistent chat rooms, I get a PIDGIN SIPE error: Error joining chat room [6] Node <room uri=""> not found When I try to join rooms on the first pool of persistent chat rooms - it connects fine. I'm running SIPE (1.20.1-2.el7.x86_64) for CentOS 7 Would this be considered a bug?

Multiple Persistent Chat Pools