#Cisco cucm upgrade upgrade#

In process of upgrading isnГўВЂВ™t sending a reINVITE at half the SE value. Issue can now be recreated there as well.

#Cisco cucm upgrade upgrade#

With the Pub out the way, the subscriberГўВЂВ™s upgrade was started and the Was placed after the upgrade completed and the issue cannot be recreated. SIP dialog to source from the Subscriber node results in no issues and SIP Timeframe (SE of 240 seconds) and failed to see a refresh from CUCM afterДЎ20 seconds ГўВЂВ“ the call again disconnected once the SE expired. I lowered the Session Expires timer to recreate the issue in a shorter Looking at CCM traces showed no refresh was sent at half the Session Upgrading the Publisher node, a call was active where the SIP dialog wasД®stablished between the Publisher and CUBE. Send a SIP session refresh while an upgrade is in progress? I noticed thisД«ehavior when running through a mock upgrade for a customer. Wondering if anyone else has observed an issue where a CUCM node fails to This is going from 8.0-1 to 8.1-1 and I've yet to test this using other upgrade paths, but I plan on testing this once more once time permits in order to set proper expectations w/ the customer. If this is expected behavior, I can make sure the customer's Session Expires value is temporarily increased during the upgrade window, but I can't seem to locate any documentation stating this is a known or expected caveat. Basically, it seems the CM node in process of upgrading isn't sending a reINVITE at half the SE value. With the Pub out the way, the subscriber's upgrade was started and the issue can now be recreated there as well. Back to the Publisher, another call was placed after the upgrade completed and the issue cannot be recreated. Forcing the SIP dialog to source from the Subscriber node results in no issues and SIP refresh requests are sent as expected. I lowered the Session Expires timer to recreate the issue in a shorter timeframe (SE of 240 seconds) and failed to see a refresh from CUCM after 120 seconds - the call again disconnected once the SE expired. The active call dropped and looking at CCM traces showed no refresh was sent at half the Session Expires value. While upgrading the Publisher node, a call was active where the SIP dialog was established between the Publisher and CUBE. Wondering if anyone else has observed an issue where a CUCM node fails to send a SIP session refresh while an upgrade is in progress? I noticed this behavior when running through a mock upgrade for a customer.