Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Acme Packet (MOSC)

Block unwanted user agent from SDP field?

Mar 28, 2016 11:43AM edited Mar 29, 2016 4:59PM in Acme Packet (MOSC) 2 commentsAnswered

Is it possible to use an HMR to block specific user agents in the "S=" field of sdp? See below for example INVITE:

Summary: INVITE SDP From: <sip:556624@xx.xx.xx.xx:5060 To: <sip:01150251756941@xx.xx.xx.xx:5060> sip:01150251756941@xx.xx.xx.xx:5060

INVITE sip:01150251756941@xx.xx.xx.xx:5060 SIP/2.0

Via: SIP/2.0/UDP xx.xx.xx.xx:5060;branch=z9hG4bKdbt58f102od15lokb140.1

From: <sip:556624@xx.xx.xx.xx:5060;transport=UDP>;tag=4adaf50-a77245e-13c4-5c196-c41a76e6-5c196

To: <sip:01150251756941@xx.xx.xx.xx:5060>

Call-ID: 4b2fb30-a77245e-13c4-5c196-a2e7b4fd-5c196@67.141.40.228

Tagged:

HMR - Header Manipulation Rules

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month