Changed to a 406 V2 outgoing CLI has stoped working???

[bm97ppc]

Hi,

We had a 406 V2 with PRI60 card in the office so I decided to swap our current 403 Demo kit with it to try out some of the version 4.0 + improvements.

Anyway simple task, we use ISDN 2e so I added the card from out current system (PRI 60 Slot A BRI 8 Slot B) Upgraded the system from 3.2 to 4.2 (11) uploaded our config, all well and good.

Didn't notice any problems tell the next day, all calls out are using the main number CLI not there respective DDi’s so I did the following:

1) Check incoming call routes (yes DDi still inbound ok)
2) Notice you can have time profiles ICR so thought you may need to specify out going CLI in a user short code as it is now ‘Many to One’ (albeit only 1 to 1 on a time profile) tried short code still no luck, tested user short code withheld (.SW) that worked fine.
3) Downgraded to 3.2, still a problem
4) OK what's differene other then hardware?, so removed PRI60 leaving just BRI 8 in Slot B (how it was in 403), still no luck.
5) Upgraded back to 4.2 as run out of ideas,
6) had one last thought, blanked Config tested with the most basic config still main number going out.

So the only change not eliminated is the 406 v2 unfortunately our 403 when out as maintenance stock so I couldn't go back to the original setup to eliminate BT / the hardware (would be very unlucky for BT to mess up some thing at the exchange at exactly the same time I switch the PBX but then again it is BT).

Have I missed something or has anyone else had an outgoing DDI problem from a 406 V2?

Regards

Piers

 

[mattKnight]

You need to look at the ARS section in the config. This is new in 4.x

If you set the outgoing CLI from there, I reckon it will all be fine

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.

 

[bm97ppc]

Just tried it, no difference, I added Snnnnnnn (where nnnnnn = a valided DDi) after the . on the Main (default) ARS, I would expect all calls to show this DDI. I would expect a user short code to override this anyway.

It is like the IPO is sending out a invalid CLI and BT are replacing it with the default.

Well thanks for the suggestion.

Piers

 

[mattKnight]

Post a monitor trace of an outbound call, with ISDN trace turned on.

TBH, this sounds like a config problem, I've found all 4.x builds behave ok with outbound CLI on BT lines

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.

 

[jamie77]

I agree with Matt (I always bow down to those clverer than me, Mr. Matt "ACE" Knight!!!). We need more info on your config.

User SC's, System SC's and ARS.

When going from 3.2 to 4.2 did you check your outgoing routes?? The change from LCR programming in 3.2 to ARS in post 4.0 could screw things for you.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

Football is not a matter of life and death-It is far more important!!!!

 

[bm97ppc]

OK, i'll post a Monitor log. I was suspicious of the config but as mentioned I cleared it and tried a clean simple config. So that should have ruled that out.

Regards

Piers

 

[IPOfficeIreland]

try sending out less than 6 digits, maybe 4

 

[tlpeter]

There was an issue with a 406 and a pri 60
It did not work at all and Avaya could replicate the issue
It went to the developers and did not hear back till now
Try 4.1.15 is you have the change


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[TomMills]

tlpeter, he said he isnt using the pri 60 to dial out

have found that if you are trying to force digits out using user shortcodes you sometimes need to match the amount of digits you are sent.

Try changing the amount of digits you are sending as TheTaker suggested

 

[tlpeter]

it was too early


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[TomMills]

if you ask me, anytime before 17:30 is too early

 

[mattKnight]

>if you ask me, anytime before 17:30 is too early

17:30 is a bit early for me...

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.

 

[bm97ppc]

Hi All,

The PRI 60 is no longer in the PBX so there should be no problem from that.

I believe (or have always been told) BT send 6 digits and Telewest send 3 digits. I have tried varying the number of digit between the full 10 and 6.

Piers

 

[TomMills]

so how are your shortcodes currently set up?

are you using user shortcodes to send the digits?

 

[bm97ppc]

Not normally, the correct DDI has always gone out fine on ours and all our customers systems with no shortcode. Occational we add user based SC to send out the main number instead of DDi's.

I added a user based SC just to make sure i knew what it was sending as User SC over rule all other SC's.

 

[TomMills]

what was the shortcode? did it work?

i was told once that the system recognises which DDI is assigned to the user and sends that out, so you would need to use user shortcodes in the instance of wanting to send the main number or a group ddi or if an extn had more than one call route pointed at it?

 

[bm97ppc]

No, it was the second thing i tried.

I used (where XXX = relavavent DDi):

?
Dial
.S2085897XXX (10 digits)

10 digits has always worked but i also used 10 to 6 digits

e.g .S897XXX (6 digits)

 

[TomMills]

how many digits are they sending you? how many do you have programmed in your incoming calls routes?

have you tried four?

 

[bm97ppc]

They send 6, i haven't tried any lower then 6

 

[TomMills]

are you pointing the user shortcode straight to the line group or through the ars?