Session Border Controller (SBCE):SBCE restarts and doesn't work on URI Modifcation rule with an $ sign


Doc ID    SOLN309223
Version:    7.0
Status:    Published
Published date:    09 Dec 2020
Created Date:    05 May 2017
Author:   
Steffen Koberstaedt
 

Details

SCBE running on 7.1.0.2-01-13249 

Problem Clarification

Issue:
1. Interworking Rule for URI Modification needs to be saved twice to get active
2. When a call runs into this URI Rule, the SBCE stops working and restarts

Action:
Create in Interworking Rule with an “$” Sign at the end of the User Regex put a $ sign, as can be seen on the attachment

1. The rule is not working, you have to go in again into this rule, delete the $ sign, press finish,
go again in this rule add it again and press finish again, now the rule will work,
but you will run into issue 2 now.
2. When now a call hits this rule, the SBCE crashs
After the SBCE is back, and a new (the second call) hit the same rule, it works fine.
It happens only for the first call, after this crash, all calls for this rule will work on this rule.

Cause

SBCE SW issue

Solution

This issue is fixed with MR AURORA-12436 in 7.2.1 (7.2 FP1)

https://downloads.avaya.com/css/P8/documents/101044503

Note:

In releases(7.2 Fp1) we have Uri based routing. If you face some issue with” No subscriber flow matched”  and then they have to configure the respective  flow to make it work.

In prior SBCE release the server configuration within the routing profile was only match for the target IP - the first matching server flow with a server configuration containing this target IP was used.      

But with 7.2FP1 the server configuration within the routing profile is determining the exact call flow with the same server configuration (this was not the case with former release).
 

Attachment File

URI Manipluation.png
0Bytes • < 1 minute @ 56k, < 1 minute @ broadband


Additional Relevant Phrases

SBCE crash, SBCE restart, URI Manipulation Problemas con SIP Trunk

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy