Acme Packet (MOSC)

MOSC Banner

Delay when using ENUM with multiple records and no session agent

edited Sep 19, 2014 7:39PM in Acme Packet (MOSC) 3 commentsAnswered

Hello,

 

I have ENUM configured to route calls and some numbers have 2 different ENUM entries with different orders, in order to provide alternate routing. No session agent is defined for the 1st ENUM entry. The call should be routed directly to the IP address (e.g. 1.2.3.4 below). 

When the target of the 1st ENUM record is not reachable, it takes about 30 seconds until the SBC tries the 2nd route.

Is there a way I can improve this?

 

Regards,

Alain

 

The ENUM records look like:

!^(.*)$!sip:\1@1.2.3.4;egress=realm1!
!^(.*)$!sip:\1@some-session-agent!

 

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center