IP406 Lets me Dial Any Number - even 12345!!!

[mytelecoms]

Hi folks,

We have an IP406 (1st edition) which is allowing us to dial ANY number - even 12345. The system presents a ring tone to the caller.

This only happens when we run V3 firmware (any version including Beta). Rolled it back to V2 and it works fine.

My disti has raised a case with Avaya, but as usual, it's taking forever. Our traces seem inconclusive.

It's as though the firmware is handling the PRI signalling wrong. We're using Q931 over PRI (38 channels using two circuits).

Anyone seen this before?

Thanks

Chris

 

[CarGoSki]

Yes. Well sort of. Until I had my routing tables correct Site B would dial out of site A with some extranneous numbers.

Post your short codes.

 

[mytelecoms]

Just tested this further, and done some more traces. It seems it's not just non-existing numbers that ring. If you call a number that is busy, it too will ring. The system traces however show the ISDN is presenting the number as busy. It's the switch which seems to misunderstand the signalling.

Currently at Avaya Tier 3 and waiting.

BTW, shortcode is:

SC: ?
TN: .
F: Dial

Also tried 9n instead of using "." but no joy. It's definately the switch or PRI cards which don't read the line right. As I say, V2 and 2.1 work fine!

 

[CarGoSki]

I am not fond of using a wildcard for dialing. Your short code translates in my mind as "look for any number and send any number to dial."

If you were to use a standard 9 short code does this remedy the situation.

 

[IPOdan]

I agree with CarGoSki. Reprogram your short codes to look for specific numbers, and try it. The ? is a wildcard and acts as a default entry, dialing when nothing else matches. I would say that is why that short code will let you dial any number. Change it to a 9N as suggested by CarGoSki.

 

[mytelecoms]

Thanks for the tips but I'm not sure you both read my last post properly. I have alreay tried the 9N code.

We're up to Tier 3 with Avaya now, and they are still struggling to replicate it to get up to Tier 4. Nothing wrong with the configs Avaya have said.

Definately smells like firmware to me. Runs fine on any level other than 3.

I'll let you all know the outcome.

 

[CarGoSki]

Well o.k. but I still believe that if you were to use the standard 9 dial codes then it would work. Post the monitor traces where a call fails.

Also when you used the 9N code did you also still have the wild card code active?

 

[mytelecoms]

It is definately nothin to do with the shortcodes. I have used ? and 9n and also used 9n to generate a secondary dial tone. Have also tried 9 without the wildcard. Avaya have already confirmed it is nothing to do with the shortcode.

Dialing out works whatever the codes are. If you call a number that exists, then you can get connected. If the number is busy or does not exist, then it still rings.

Our traces always show correctly a number that is busy. It is the system not presenting the tone or line signalling through the the extensions.

Thanks for your suggestions, but I think you're looking in the wrong place.

 

[CarGoSki]

Perhaps but I am a monitor trace kinda guy ya know.

 

[mytelecoms]

PROBLEM SOLVED!!!!

Seems we were getting DASS2 messaging across Q931 PRI. The circuit was a Telewest Q931 PRI, but I guess there software is outdated because the signalling is different to BT's Q931.

Avaya have removed support on V3 for DASS2 messaging. They used to identify the text in the message and return busy or NU tones - but not anymore.

Whilst we're waiting for Telewest to fix their end, Avaya have provided us with a private build to add DASS2 support back in. They won't be including it in any new builds though.

 

[CarGoSki]

Great. What is DASS2 messaging. Don't make me pull out an ISDN book. I hate reading that boring crap ; }

 

[mytelecoms]

If you're not in the UK, chances are you won't know what it is!!

DASS2 is a signalling type which was widely used in the UK on PRI circuits. The UK has now moved more to Q931 signalling, which is much cleaner the DASS2. However, some providers seem to still be running early versions of Q931 which appear similar to DASS2.

Telewest are upgrading their software now to full ETSI to make sure this never happens again!

 

[aramsay]

Must be a local issue; we're running a 406v1 on at Telewest PRI Q931, without any problems.

I know that Telewest had some problems with switches in Bristol / Birmingham / Leeds when they tried to break out on to the BT network, as we would always get NU when we tried to dial some numbers; turned out that there was something wrong at those locations to do with DASS2 (not quite sure what).

Anyway, Telford / Wolverhampton appears ok on v3 on a Telewest PRI, which we've been on for a few months (incidentally, v3 has solved any outstanding issues that we've had!).

 

[mytelecoms]

This circuit is in Liverpool, so perhaps it is a local thing.

The funny thing is, since we installed this box two years ago, they have had rather strange things happening which we put down to firmware, as upgrades always seemed to help.

When we thought about it, none of our other customers had problems, and they were all on BT or BT tail-end circuits.