Acme Packet (MOSC)

MOSC Banner

How to enforce using the matching authentication credentials on a multi-identity SIP trunk

in Acme Packet (MOSC) 5 commentsAnswered

Hi,

we have the curiosum that a single SIP trunk to a telecom provider is supporting multiple so-called "pilotnumbers". We need to actively REGISTER on the provider´s registrar and receive incoming calls for the registered pilotnumbers afterwards. Registration is realized with multiple surrogate-agent elements with individual registration identities and corresponding passwords, which is working fine.

However, when an "incoming" call is accepted by the PBX, to which the call was forwarded by the SBC, it is sending a SIP re-INVITE message immediately afterwards. The provider is responding with an authentication challenge (407) and the SBC needs to authenticate on base of the configured AUTH-ATTRIBUTE entries in multiple session-agent elements. And now the problem starts:

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