We wanted to weigh in both RMX-Lync integration scnerios of using same SIP domain or through the static route and another SIP domain video.domain.com. In the first case we created a user with displayname RMX9000 and simply assigned the SIP address used in our SIP domain i.e SIP:email@example.com as any normal SIP user would have. Subsequently a meeting room was created on RMX with following settings.
- Server IP Address or Name: FEPool.Domain.com
- Server Domain Name: Domain.com
- Port: 5061
- Display Name: RMX9000
- Routing Name: 9000
- Sip Registration in network services Checked.
We started to see the user's presence correctly, everything worked fine as expected so far. After testing we removed the meeting room from RMX, but didn't disable from Lync as we wanted to some more testing.
However whoever added this user as a contact during testing phase or even new users looking up firstname.lastname@example.org are getting the presence information as available, and when try to start a video call it says RMX9000 is offline. Wondering where the clients are getting this status of "available".
Have you seen Jeff's blog:
If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks.
Jean-Philippe Breton | Senior Microsoft Consultant | MCTS, MCITP, MCT, Lync MVP
Yes I saw Jeff's articles and actually based on the one given below we decided to test both scnarios. My issue now is finding a way to unregister, as lync keep showing available when its doesn't even exist on RMX
You can try to remove this contact and re-create it again so that the presence info would be refresh.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
That's what we have already done to carry on our testing, however this is very unrealistic approach especially when we are expecting to have 10-15 meeting rooms. It would be practically unfunctional solution to keep remove/re-creating these users every now and than.