Acme Packet (MOSC)

MOSC Banner

Reg caching and port mapping

edited Oct 3, 2014 10:45AM in Acme Packet (MOSC) 1 commentAnswered

Hi,
I've got problem with port map and reg caching - basically port mapping works great for REGISTERs (each one has unique port), but some customer sends INVITE without correct AOR (ex. has plenty of E164 numbers). Will be very difficult to change it, because it has worked for months, without SBC.
Examples:

 

REGISTER sip:46.xxx.xxx.209:5060 SIP/2.0

Via: SIP/2.0/UDP 46.yyy.yyy.119:5060;branch=z9hG4bK76add394a1f506c40
Route: <sip:46.xxx.xxx.209:5060;lr>
Max-Forwards: 70
From: <sip:abce-testy3_521@46.xxx.xxx.209:5060>;tag=f428355f10
To: <sip:abce-testy3_521@46.xxx.xxx.209:5060>
Call-ID: 3e135885b2940353
CSeq: 6834 REGISTER
Authorization: Digest username="abce-testy3_521",realm="adescom",nonce="00036f35",uri="sip:46.xxx.xxx.209:5060",response="6a54bfcd26e12b5fc49289524f4cb03e"

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