Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Thread Tools Search this Thread Display Modes
Old 01-16-2020, 03:48 AM
lam107 lam107 is offline
Aspiring Member
Join Date: Nov 2018
Posts: 2
lam107 has 10 reputation points
Default CM8.1 SIP Trunk to Session Manager keep alive


i got the situation that physically disconnected SM connection then CM signaling group still keep to in-services status last for at least 5 mins, checked with the SIP OPTION sent from CM to SM only every 15 mins, is it possible to tune it faster?

Anyone can help? Many Thanks
Attached Images
File Type: jpg ScreenHunter_512.jpg (65.1 KB, 11 views)
Reply With Quote
Old 01-20-2020, 12:44 PM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Join Date: Sep 2010
Location: New York
Posts: 506
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points

From SOLN232389:

In case the L3 testing is enabled on the SIP sig-group page, the CM will do a SIP OPTION message exchange for testing the trunk’s state. Test 1675 is performed by CM periodically, and it may take up to 15 minutes for the test to be run again on the same trunk related signaling group. If this testing fails, CM will further move on and report the trunk state/alarm (warning by default based on the “set options” screens – can be done by Avaya init or inads login only). Even though the CM can realize a TCP socket down (denial 2094), this is not in direct connection with the test 1675. The test 1675 has to fail, to see a “IP SIG-GRP xyz IS BYPASS” message in the logs, to look further for any CM alarms.

If there are calls over the SIP trunk, and calls are failing to establish, then maintenance will be notified and the test will be performed earlier than the scheduled maintenance testing. This will cause the signaling group to be placed in bypass much more quickly. Sending of SIP OPTION message is triggered by periodic maintenance, which happens every 15 minutes (not adjustable) and it take 32 second after that to determine that the far end is not responding. This is in case of the IDLE scenario when there is no other traffic. If there is traffic on the signaling/trunk group (calls traversing), then after some call failure the CM will forcefully run the test and determine the signaling group’s state.
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 08:58 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.