ODI Destroyes After Trans-expire Expires, But Is Reused In INVITE To Second AS When There is 2 AS ( Application Server ) configured in Core Session manager ( CSM ) (Doc ID 2427585.1)

Last updated on SEPTEMBER 29, 2023

Applies to:

Goal

Please find the call flow

X.X.X.X             Y.Y.Y.Y           Z.Z.Z.Z  
          
  INVITE 1 -----------> Transmission 1
 
  INVITE 1 -----------> Transmission 2
 
  INVITE 1 -----------> Transmission 3 ( Timeout )
 
 
 
  INVITE 1 ----------------------------------->
   <----------------------------------- 100 trying


   <----------------------------------- INVITE 1
  503    ------------------------------------>


User is using loose routing ( test.route.com has Y.Y.Y.Y and Z.Z.Z.Z as next hop ( Application Server - AS ) ).

NOTE : Call flow and issue as below :

1. INVITE from X.X.X.X ( egress ) is sent to Y.Y.Y.Y.
2. INVITE times out after 500 ms.
3. Now SBC destroys the ODI used ( 4257 ).
4. Now SBC is trying the second IP Z.Z.Z.Z for INVITE.
5. Here SBC uses the same ODI ( 4257 ) in the INVITE sent to Z.Z.Z.Z ---
But the same ODI was destroyed before.
6. Now when Z.Z.Z.Z sends a re-invite, SBC rejects the same with 503 (Could not find ODI 4257 ).


I think either SBSC should use a new ODI for INVITE sending to Z.Z.Z.Z
or SBC should not destroy the ODI after expire time of 500ms as there is
another next-hop to be tried.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.