Overlap trunks. Incoming call handleing

[Nick44]

Hi.
I have 2 remote gateways located in Europe. 1 in Germany and 1 in Italy.
Both Gateways have BRI local trunks connected.
Problem I am experiancing is that incoming calls seem to be a mix of both enbloc and overlap signalling depending on where within the country the calls are origionating.

I have set both trunks up as enbloc/enbloc, and the majority of DDI calls route to the extension fine, however, some callers from some areas get a number unobtainable message, and I can see partial digit strings in the trunk trace.

I have tried changing the trunk groups to be in/out overlap/enbloc, but at this setting the inc-tru-treatment page is locked out.

My question is, how do you steer incoming call digits on an overlap trunk?

Thanks,
Nick.


Speak softly and carry a big switch

 

[Nick44]

Anyone able to assist me with this please?

Speak softly and carry a big switch

 

[AvayaTier3]

C:\avayadoc\Aura CM5_2\CM5_2_avayadoc\CM52FDandImplementation.pdf

ISDN Service starts on page 1089

Your provider will send the incoming DNS digits.

Direct Inward Dialing (DID)
Some public network operators may not offer full DID service on BRI trunks, but instead
may offer the BRI equivalent, which typically is called MSN. This is the case if the public
network treats the BRI as an endpoint interface rather than a trunk group interface. In such
a case, the network only routes up to 10 public numbers to a particular pair of BRI trunks.
The network may not let calls overflow from one BRI trunk to another.

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

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com