Acme Packet (MOSC)

MOSC Banner

The translation-rule not working well

in Acme Packet (MOSC) 6 commentsAnswered

Dear All,

We have AP4600 SW9.3 eSBC.

I would like to ask for help with configuring a translation rule. We need to remove the E0130000 prefix from the request-URI (this part is working), and if the call arrives without the E-prefix and the short number 1439 is dialed, it should be translated to 18771425.

The rule works correctly when tested with test-translation-rule, but in live traffic it does not match the local-policy, so the SBC returns SIP 480 and does not forward the call toward 18771425.

The call may arrive in these formats, and the test-translation correctly translates them

sip:E013000022321439@10 .130.0.40:5060;transport=udp;user=phone --> sip:22321439@10 .130.0.40:5060;transport=udp;user=phone

Tagged:

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