Symptom

CUBE sets up a call normally with itself performing the session refresh. On the first refresh, CUBE sends Session-Expires: 1800;refresher=uac PSTN replies to the first refresh with Session-Expires: 1800;refresher=uas This is an RFC violation, but CUBE logs an error and continues the call. SIP/Error/Session-Timer/sipSTSLCheckCompliance: Received refresher is not same as sent refresher When the PSTN sends the second refresh, it triggers the New call flag within CUBE. CUBE responds with a 100 trying, but does not send any additional SIP message.

Conditions

CUBE with session refresh

Workaround

Remove session refresh negotiation via Inbound/Outbound SIP profiles voice class sip-profiles 1 request ANY sip-header Min-SE remove response ANY sip-header Min-SE remove request ANY sip-header Session-Expires remove response ANY sip-header Session-Expires remove request ANY sip-header Supported modify "timer,|timer" "" response ANY sip-header Supported modify "timer,|timer" ""

Further Problem Description