Acme Packet (MOSC)

MOSC Banner

Untrusted Connection Timeout for UDP

in Acme Packet (MOSC) 1 commentAnswered

Hello,

We got acmelog full of minor system alarm events after upgrade. System complains about unconfigured connection timeout. It is expectable for TCP or TLS 'cause we have 'untrusted-conn-timeout' params set to 0 on the sip-interfaces, but how it can be applied to UDP transport (50K UDP ports are affected according to acmelog)? Does anybody know?

Aug 23 14:00:25.832 sipd03@SBC-4600-01: MINOR untrustedConnectionTimeout for socket TCP:13.13.46.14:9266->4.25.29.25:5081 not initialized

Aug 23 14:00:28.855 sipd01@SBC-4600-01: MINOR untrustedConnectionTimeout for socket UDP:4.25.40.18:5060 not initialized

Aug 23 14:00:28.860 sipd01@SBC-4600-01: MINOR untrustedConnectionTimeout for socket UDP:172.18.1.15:10000-60000 not initialized


Thanks in advance. Regards, Daureen

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center