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)

Local policy: to-address wildcard xxx452?

Jul 5, 2017 3:23PM edited Jul 15, 2017 5:00AM in Acme Packet (MOSC) 6 commentsAnswered

I'm trying to see if I can have wildcard digits to the left of a fixed string in the to address of an invite. All I've seen is matching from the left to the right.

I believe the number of options is not 1000 (the full three digits all used) but something much less. For now I've just done a handful like (100452 101452 102452)...but that's obviously got scale issues.

Any other thoughts? Am I missing anything?

Tagged:

SIP - Signalling, Trunking and Interconnect

1

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