Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ARS Digit Conversion / SIP Diversion Header

Status
Not open for further replies.

Keggles

IS-IT--Management
Jul 30, 2014
35
US
I am trying to dive into things I am not quite comfortable with as my disclaimer. Avaya Aura/CM 6.3

So, I know there is SigMa Scripting, ARS Digit Conversion, and UDP, etc. Some of the customers/locations we call do not accept our SIP Diversion header so obviously inbound/outbound is a failure in some way. Trying to get a location or their provider to work together to fix this is like pulling teeth on a unicorn. What I am trying to figure out is, what is the best way to strip the area code from the number so if one of our customers dials the number it goes out like a local call.

-- In ARS Digit Conversion what I am thinking I would have to do is :

Matching Pattern Min/Max Del Replacement String Net Conv

3 Digit Area Code 3/3 3 Blank ARS Y

If I am understanding that it will strip off 850 when it is dialed leaving the 7 digits, correct?



-- I also attempted to write into the manipulation section on SBCE with

/*To remove the Diversion Header from XXX-XXX-XXXX Area Code For ------*/
within session "INVITE"
{
act on request where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
{
if (%HEADERS["TO"][1].URI.USER.regex_match("1XXXXXXXXXX(.*)")) then
{
remove(%HEADERS["Diversion"][1]);
}
}
}

 
If its for the whole area code 555, you could have an ARS match for 10 digit numbers with 555 or 11 digits 1-555 and have a particular route pattern that deletes those leading digits.

A diversion header is generally for indicating that the call was redirected - like when A calls B that covers to voicemail, the call is sent to voicemail number C from caller A's number and B is put as the diversion header - that's what Aura Messaging uses to decide who's mailbox greeting to answer with.

On some SIP carriers, they require certain headers to contain numbers that are on your service - so if A calls B and forwards to C on the PSTN, certain headers might be A and the diversion from B. There are sigma scripts that say "where a diversion header is present, change the P-Asserted-Identity from the outside caller's number to the B, the diverting party"

Normal laws of SIP state if you don't support a header, pretend its not there. Maybe the fact that your call is being diverted could indicate its an outside caller and the far end is requiring some FROM or PAI headers of numbers belonging to you and not the outsider being diverted?

Just a guess.
 
So, in GEDI I would write that out

Matching Pattern Min/Max Del Replacement String Net Conv

555 10/10 3 Blank ARS Y

or

555 11/11 3 blank ARS Y
 
not in ARS digit conversion. In the resulting route pattern you can manipulate the digits. So, if in ars analysis 555 min10/max10 goes to route 3 (like a lot of other dialed strings), give it a new unused route pattern and have that delete the 3 leading digits
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top