Mitel 53xx Phone Number issue

[mitelpoep]

Hi There,

I have a problem where the 53xx Series phones can not have a "0" as an extension. eg 0600 on Mitel 5330 IP Phone. The phone just displays " Application Loading" .

I have done a number sub. for incomming calls and this works fine, Just like to know why this is happening on the 53xx phones.

thanks

Mitelpoep

 

[cwssa]

Mitelpoep, I am experiencing the same problem at a client, that has a PRI range starting with 0, and they want DDI numbers as well.

Apart from the number substitution solution, which means they have a different internal number to that of their incoming number. Of course this is not a major issue just very annoying.

 

[MitelInMyBlood]

We have 0xxx DID numbers WORKING via PRI but it's on a big SX2K with 3rd party voice mail (Octel Overture 250). However, we've not tried it with a 53xx instrument on any of the clustered 3300s. Do you think this is a SET issue?

What I can tell you from experience is if we had it to do over (0xxx) we would not have done it as it has just been a royal P.I.T.A.

However, 0xxx is indeed a valid digit range and therefore should work and if not, is a pretty big bug. What has Mitel had to say about it?

 

[kwbMitel]

I have a vague (possibly imaginary) recollection that I saw a tech bulletin regarding leading zero's but I can't find it.

Hardly worth mentioning but...

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

Hi,
definitely a bug. have a ticket logged with 3rd line. I think only to be fixed in 9 UR1. Prelim trials for 9 still had the issue I believe.

no workaround you'll just have to change the dn for now.

 

[MitelInMyBlood]

Is it mentioned in the KPI? (If not, why not?)

 

[Mitelpassion]

don't think it is and don't know why it's not listed...not even sure what gets on the KPI and what not..

 

[kwbMitel]

In my experience Mitel only posts KPI's for issues that they know how to fix or have already fixed.

More a "Was Known" as opposed to "Is Known"

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

Point well taken. That explains why when we call with a bug we hear, Oh there's a DPAR open on that already. Would sure save some time if everything was in the KPI

 

[Mitelpassion]

God bless tek-tips!

 

[GX5Krocks]

I've been told that the kpi only lists the ones that rnd hitlists for resolution, they change on a daily basis. not all defects make this list

 

[MitelInMyBlood]

So, is there an open DPAR open to track this issue and if so would you mind sharing the DPAR number so we can note it on our internal ticket?