Actions

Use Cases:SIP Redirect no processing: Difference between revisions

mNo edit summary
No edit summary
Line 29: Line 29:


Also make sure these settings are applied:
Also make sure these settings are applied:
   SIP -> Header Parameters -> Allow Recurse [unchecked]
   SIP -> Header Parameters -> Use legacy redirection mode [unchecked] (old naming convention was: Allow Recurse)

Revision as of 12:48, 10 January 2019

Applies to version(s): v2.8 and above

In this scenario, the incoming call is sent to a SIP redirect server, which returns a 3xx message. The first contact is returned to the incoming leg while releasing the call.

Redirect (no processing).png


This is the call flow of such a scenario. A 302 Moved temporarily is returned from the SIP redirect server and the contact information is returned to the incoming leg. for example in ISDN, the contact number will be included in the redirection number of the RELEASE message.

SIP Redirect callflow (stop).png

Configure Reason Cause Configure Routes
  • Toolpack:Modify_NAP_profile_D. You need to modify the default behavior or some reason causes:
    • Profiles -> Edit Reason Cause Mapping
      • 300 Multiple Choices-> Route retry action -> Stop Call

Do this for all Reason Cause that will be used

  • Create normal routes to the redirect server: Configure Routes:
    • Routes -> Create New Static Route
      • Name -> To_SIP_Redirect_Server
      • NAP -> any
      • Remapped_NAP -> NAP_SIP_REDIRECT

Also make sure these settings are applied: 

 SIP -> Header Parameters -> Use legacy redirection mode [unchecked] (old naming convention was: Allow Recurse)
Retrieved from "https://docs.telcobridges.com/index.php?title=Use_Cases:SIP_Redirect_no_processing&oldid=26433"