In TMS, all endpoints are allowed both incoming and outgoing SIP and H323.
Whenever I book a conference, it always shows H.323 as the connection method, even though SIP is enabled. I would have expected it to say SIP-H323 as it can connect via either protocol. Note that the call still works, but if I am experiencing the issue outlined in the thread I linked above, it's interworking from H323 to SIP rather than being SIP to SIP.
If I untick the boxes for incoming and outgoing H323 on the endpoint in TMS and book a conference, the connection then changes to SIP and works fine without needing to be interworked. This proves to me that TMS knows the endpoint can make and recieve SIP calls.
Can anyone tell me if this is expected behaviour, or have I misconfigured something?
TMS version is 14.2.2, booking conferences on TP server 3.0.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...