Trunk - inbound digit manipulation

[trilogy8]

I have a site in Europe where the carrier provided an isdn30, which I've had plenty experience with. However, I'm unable to get inbound calls working to individual numbers. What I'm observing in the traces is the middle digits of the e.164 number and not the end digits that I typically treat with incoming treatment. ex. + xxx aaa bbb xxxx. I only see the aaabbb digits on the trace and therefore cannot get the xxxx numbers to the deskphones. In this situation I can only send every call to 1 number. The carrier insist the provisioning is correct and mentioned our PBX timers being an issue, along with we should be accepting overlap and blockdialing. I know on page 2 of the TG form you can alter the digit handling field, but once done additional fields appear that ask about digit treatment and digits. Not clear of the logic there and when that is invoked the incoming trunk treatment is wiped out.

Essentially, I need to get the final number to be the xxxx portion of the number. Any help would be appreciated.. thanks in advance.

 

[AvayaTier3]

Hardware Platform? Definity/CM Software version?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[trilogy8]

CM6.3 / s8300/G450

 

[AvayaTier3]

See the example for cm3 on this link

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[trilogy8]

The problem I'm getting is the trace I have on the tac shows aaabbbb and not the ending 4 digits of the full dialed number, which is what I would use to map to my internal dial plan. If I randomly call 5 different numbers in the range I'm still only seeing aaabbbb and not the last 4. I can't treat the call without the ending portion of the number; However the carrier is saying they are sending those digits. I can send the entire number range to 1 number and use a vector as an AA, but I'll get skulled if I leave it that way. Because they mentioned the overlap and timer setting I recalled that was a setting in the TG form, but like I referenced earlier, it opens up additional fields I'm not clear about.

 

[Speewah]

Which country? We have PRIs in most European countries so I may have some config that will help.
At sites where we the carrier has provided variable length DIDs we set Digit Handling (in/out) to overlap/enbloc and in the Digits field enter the AAR access code.
Then we use the AAR digit conversion table for that location to manipulate the digits to fit our internal dial plan.

 

[wpetilli]

That would be so helpful, thank you. Country is Luxembourg.

 

[mattKnight]

Can you post a list trace tac? and a copy of your Incoming Call Treatment table

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[wpetilli]

Sorry for hijacking your thread Trilogy... I have a similar issue, just not an emergency.. been having intermittent inbound issues for a while. Some work, some don't. Not hearing complaints enough to put it at the top of the list.

 

[Speewah]

In Luxembourg it is similar to as I described above, except on page 2 of the trunk group form we have set Digit Handling (In/Out) to overlap/overlap.
Then we set the Digits field to the AAR access code and populated the AAR digit conversion table for that location.
Does that help or do you need some AAR Digit Conversion samples?

 

[trilogy8]

The site is Luxembourg. For the Digit Treatment I am using 'insertion'? If you have some examples of the aar conversions that'd be helpful as a visual. I'm still not wrapping my head around how these numbers are presented, but I'll test out how you've done it. Thanks again-

@wpetilli - not a problem

 

[Speewah]

The below example assumes your carrier is sending 6 - 9 digits beginning with 123456, and that your internal dial plan is 7 digits and extensions at this site start with 789.
Based on the feedback from your carrier that you need to accept overlap and block dialing I would suggest that Digit Handling should be set to overlap/enbloc, Digit Treatment should be Insertion and Digits should be set to your AAR Access Code.
Of course, if the carrier is sending you junk then none of this will help..

AAR DIGIT CONVERSION REPORT

Location: xx

Matching Pattern Min Max Del Replacement String Net Conv ANI Req

123456 6 6 6 7891000 ext y n
1234567 7 7 7 7891000 ext y n
12345678 8 8 8 7891000 ext y n
1234567xx 9 9 9 78967 ext y n

 

[trilogy8]

Will have a go, thanks. Just curious, your examples look like you're replacing with 1 internal extension for all entries.

 

[trilogy8]

Actually, I put in 1 entry with length of 10 with matching pattern aaa and deleted 6 and replaced with nothing and random individual DID's are working.

 

[Speewah]

Only for the first 3 entries, as an example we send multiple 'pilot' numbers to the same VDN.
The 4th entry covers a range of 100 DIDs, although I just noticed an error - it should be:
1234567xx 9 9 6 7896 ext y n

 

[trilogy8]

Sorry for bringing this back into the fold, but do you have sample ars entries for outbound and anything special in the rp? outbound calls are failing with a variety messages in the trace :
12:06:12 denial event 3731: Incompatible caps for end D1=0x7f000b72 D2=0x9f9
a
12:06:12 denial event 2300: Ept capabilities mismatch D1=0xfa D2=0xfa
12:06:12 denial event 3731: Incompatible caps for end D1=0x7f000b72 D2=0x9f9
a
12:06:12 denial event 2300: Ept capabilities mismatch D1=0xfa D2=0xfa
12:06:12 G711A ssff ps:20
rgn:250 [10.192.237.46]:13116
rgn:1 [10.2.30.25]:53360
12:06:12 dial 9 route:ARS
12:06:12 denial event 3731: Incompatible caps for end D1=0x7f000b72 D2=0x9f9