Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 08-16-2017, 05:40 AM
tomfarrell tomfarrell is offline
Member
 
Join Date: Mar 2013
Posts: 7
tomfarrell has 10 reputation points
Default PAI, From or Diversion Header ?

Hello,
We are having problems completing calls to 8YY toll free numbers when routing thru a vector to ATT’s SIP service IP Flex

1. Public caller dials 483-4400

2. 483-4400 is a vdn that routes caller to vector 115 (see attached pdf of the vector)

3. If caller selects option 1 or option 2 caller is routed to a toll free number.
a. 855-474-xxxx
b. 866-835-xxxx

4. The caller ID sent is the public callers phone number, not one of our cm7 numbers.

5. ATT rejects the call because ATT cannot properly bill the owner of the toll free number.
a. All ATT will see is caller ID of the person making the call
b. ATT apparently checks that caller ID against all the numbers in our IP Flex trunks and rejects the call because it cannot find a match in the database.
c. ATT suggested a couple of options and Avaya chose the diversion header method.

ATT suggested fixes:

Tom,
You just need to change the From, PAI or Diversion header to match a number in your call plan and the 8yy calls will complete.

Thanks,
Patrick C.


Avaya then comes up with the following script for use in our SBCE’s.
We named it Diversion Manipulation

See attachment Script 1 Diversion Manipulation

This script fixed the problem with the toll free numbers sent thru the vector.
BUT, I noticed that the script was applied globally, so that now every outbound invite from the SBC has that diversion header attached.

A couple other problems became apparent in the next few weeks.
Some systems (pbx’s) don’t like the diversion header.

1. A local call from one of our desk phones to the State Police Helpdesk will not complete normally.
a. Cell calls to the SP complete normally.
b. Removing the diversion header and calls complete normally from a desk phone.

2. A call to another toll free number 877-963-xxxx routes to the diversion header number 483-4400.
a. Removing the diversion header and calls complete normally from a desk phone.


Avaya created a New Diversion:

See attachment Script 2 New Diversion

Now we have:

1. 855-474-xxxx thru vector works ok
2. 866-835-xxxx thru vector works ok
3. Local call to SP works ok
4. Toll free call to 877-963-xxxx routes to the diversion header number (483-4400 local) which is wrong


So now I am thinking that the solution may not be SBCE related.
I feel like the guy plugging leaks in the dam, and I am running out of fingers.

Questions:

• Is there a better way to route callers off network from vector processing ?
o If the vector can be manipulated to send the toll free numbers with a cm7 caller ID that would solve all the problems

• You just need to change the From, PAI or Diversion header to match a number in your call plan and the 8yy calls will complete
o This note from ATT suggests that there is more than 1 way to skin a cat.

• Is there a way to put a header into the signaling manipulation in a case by case basis ?
o The Global signaling may solve some problems but create new ones also.

Any suggestions are appreciated.

Tom in Michigan
Attached Files
File Type: pdf vector 115.pdf (12.0 KB, 37 views)
File Type: docx Script 1 called Diversion Manipulation.docx (12.1 KB, 110 views)
File Type: docx Script 2 called New Diversion.docx (12.3 KB, 93 views)

Last edited by tomfarrell; 08-16-2017 at 06:33 AM. Reason: clarified statements
Reply With Quote
  #2  
Old 01-10-2018, 04:09 PM
beyerj123 beyerj123 is offline
Aspiring Member
 
Join Date: Feb 2011
Posts: 2
beyerj123 has 10 reputation points
Default

Greetings,

Could someone (Patrick?:-) ) tell me where in CM one would change the "value" of the From, PAI or Diversion header field to match a DID in our dialing plan?

Thanks,
Jeff

Tom,
You just need to change the From, PAI or Diversion header to match a number in your call plan and the 8yy calls will complete.

Thanks,
Patrick C.
Reply With Quote
  #3  
Old 01-12-2018, 04:37 AM
kumar1499 kumar1499 is offline
Whiz
 
Join Date: Oct 2017
Location: Bangalore, India
Posts: 40
kumar1499 has 11 reputation points
Default

the FROM, PAI and values in Diversion/History info is taken based on your public or Private numbering configuration.

make sure these numbers are updated in Public uknown number or private unknown numbering forms.
Reply With Quote
  #4  
Old 01-26-2018, 12:45 AM
vanh34 vanh34 is offline
Member
 
Join Date: Jan 2018
Posts: 3
vanh34 has 10 reputation points
Default

In my opinion, the best way to fix this is a sigma script on the sbc that only effects VDN/Vector outgoing calls. I have done this a couple of times and it works fine. Just add a prefix for the VDN in the public numbering and find/replace this prefix for a valid cli in the SBC.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:53 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.