Cisco meeting server timing disconnection

[IsenLin]

Cisco meeting server 2.4.1
SX20 CE9.4.1 and Webex Room Kit CE 9.5
Dial into the CMS using SIP, disconnected every 15 minutes 32 seconds
But using H323 will not be disconnected
Does anyone encounter this situation?

Error message:

2018-11-01	01:24:51.825	Info	call 34573: incoming encrypted SIP call from "sip:192.168.1.202" to local URI "sip:2320@192.168.1.221"
2018-11-01	01:24:51.853	Info	sending prompt response (2) to BFCP message
2018-11-01	01:24:51.875	Info	participant "192.168.1.202" joined space c2eb92bd-2585-42ec-9c5c-5fa37ebc7d63 (1.meet)
2018-11-01	01:26:52.263	Info	call 34574: incoming SIP audio call from "sip:1001@192.168.1.221" to local URI "sip:00348224815826@192.168.1.221"
2018-11-01	01:26:52.273	Info	call 34574: ending; local teardown, destination URI not matched - not connected after 0:00
2018-11-01	01:31:55.183	Info	web user "admin" log in timed out
2018-11-01	01:31:55.183	Info	web session 1 for user "admin": deactivating due to time out
2018-11-01	01:31:55.183	Info	web session 1 deactivated for user "admin"
2018-11-01	01:33:20.631	Info	call 34575: incoming SIP audio call from "sip:1001@192.168.1.221" to local URI "sip:00448224815826@192.168.1.221"
2018-11-01	01:33:20.642	Info	call 34575: ending; local teardown, destination URI not matched - not connected after 0:00
2018-11-01	01:34:08.307	Info	media module status 1
2018-11-01	01:38:59.979	Info	call 34576: incoming SIP audio call from "sip:1001@192.168.1.221" to local URI "sip:00548224815826@192.168.1.221"
2018-11-01	01:38:59.988	Info	call 34576: ending; local teardown, destination URI not matched - not connected after 0:00
2018-11-01	01:39:51.847	Info	handshake error 336032784 on outgoing connection 169 to 192.168.1.202:5061 from 192.168.1.221:60148
2018-11-01	01:40:23.847	Info	handshake error 336032784 on outgoing connection 170 to 192.168.1.202:5061 from 192.168.1.221:60186
2018-11-01	01:40:23.847	Info	call 34573: ending; remote SIP teardown with reason 11 (network - connection closed) - connected for 15:32

[Patrick Pettit]

Around the 15 minute mark, usually a SIP Session Refresh is needed, but it seems when the server tries to make the outgoing connection to 192.168.1.202:5061, it doesn't work and it doesn't connect.  Perhaps take a pcap from the server and see if the TCP connection is establishing.  If not, you may have something blocking it or the endpoint in question is not answering it, or its rejecting it. 

[micwilbu]

If not resolved already! When I've seen this issue, it has always been a certificate issue on CMS. When the certificate is signed it should have both client and server extended attributes. In the event it doesn't, the call will get torn down during the SIP refresh. Test by establishing a call not using SIP TLS and see if it remains active for 15 minutes.