Messages

1

MiVoice Office 250/Mitel 5000 / Re: Off-Node Routing call to display CLI

« on: February 16, 2014, 08:43:43 AM »

TE

I thought i followed you up to your last post. 

I've added my comments to your sentences below for clarity only: -

Now, what he wants to do is for those stations that are answering the call [on Node 2] to present the DDI that is routed to them as their Outbound Caller ID (Calling Party Number) and that number belongs to a different System [on Node 1] and maybe even a different carrier and that can only be done if the carrier allows it. This is what is commonly referred to as Non-Native Caller ID.

Since the phone your are initiating the call with is on another node [yes] and you set its Calling Party Number to a DDI that is local to its own controller [no, not yet] and sending that information over when dialling out that is where your problem occurs.

Correct in that the phone initiating the call is on Node 2 but i want to set the CPN to a DDI that is local to Node 1 not Node 2. At the same time, those phones should only display that DDI when calls are routed via Node 1 and not display it within calling its own native market.

Perhaps a bit of the background. Both nodes route ARS calls to each other via a facility/routing group that is configured with IP routing. Node 1 has a local DDI that routes incoming CO trunk calls to Node 2 that rings in to stations within Node 2's HG. When ringing, the display on Node 2's phones shows the same username configured for the DDI under the call routing tables in Node 1. All expected behaviour.

When the reverse is happening, Node 2 (via IP routing again) calls a number within the Node 1 market and routes out over its CO trunks. The CLI that is now observed is the billable number for that line. I want to change it so that when the HG within Node 2 calls the Node 1 market via Node 1, it also shows the incoming DDI set for it.

Currently, Node 2 does not have any DDI configured that would conflict with the Node 1 whitelist. The DDI i want allocated is on the Node 1 whitelist.

Is this the same thing as you've said or am i confusing myself here? 

Cheers!
Pops

2

MiVoice Office 250/Mitel 5000 / Re: Off-Node Routing call to display CLI

« on: February 15, 2014, 06:39:47 AM »

Think about what he is asking about. He has control of outbound Caller ID and I assume that it works if he changes the Calling Party Number of the station to a DDI that exists on that Node.

Correct. I can assign any of the DDI's allocated to us to any phone on the local node and it will be presented on outgoing calls.

Pops,

Most likely as I stated before the Carriers are not allowing for Non-Native Caller ID to be sent out from those stations. You will need to get them to change that then you will be able to use any number you want as the Calling Party Number and it will solve your problem.

Assuming i can get this changed with the carrier, how does one distinguish and allocate the DDI to outbound ARS calls routed to Node 1 without changing the phone's Calling Party Number so that it won't affect their regional CLI within Node 2?

Now, what he wants to do is for those stations that are answering the call to present the DDI that is routed to them as their Outbound Caller ID (Calling Party Number) and that number belongs to a different System and maybe even a different carrier and that can only be done if the carrier allows it. This is what is commonly referred to as Non-Native Caller ID.

Bingo, you've hit the nail on the head but this still leaves me unsure of something. If the Node 2 call is routed via ARS to Node 1, how does the carrier detect the call is initiated by a "non-native" node if the outgoing trunks are being used from the local node? I thought the internal routing would be transparent and the carrier wouldn't detect that a non-native node initiates the call.

Thanks chaps. Learn something every day here.....
Pops

3

MiVoice Office 250/Mitel 5000 / Re: Off-Node Routing call to display CLI

« on: February 14, 2014, 11:31:19 AM »

Yes, I am trying to present outbound calls from node 2 (that are routed via node 1) as the same allocated DDI number that is used to call the HG on node 2.

Cheers
Pops

4

MiVoice Office 250/Mitel 5000 / Re: CallerID issue

« on: February 14, 2014, 10:16:56 AM »

Had a similar issue and we requested BT to enable COLP too. Stumped us at first I must admit....

5

MiVoice Office 250/Mitel 5000 / Off-Node Routing call to display CLI

« on: February 14, 2014, 10:08:23 AM »

Hey guys

I currently have inbound calls to a UK DDI number routed to an off-node hunt group overseas. That second node can also make calls that routes back into the UK via the first node but how where do I change the programming so that the outbound CLI on such calls is presented as that same DDI?

Individual phones can be changed via 'calling party number' and the same on the individual CO lines but I cannot seem to do this for off-node routed calls.

Cheers
Pops

6

MiVoice Office 250/Mitel 5000 / Re: Call connection delay

« on: December 09, 2013, 07:10:11 AM »

Thanks 619, I thought that mention of System Monitor and Diagnostic Monitor was familiar - the last time I used it was with the v3.2 firmware. It appears that Mitel do not bundle it with recent SysAd packages so I don't have access to it.

It is beginning to dawn on me that there is an error with the software (DB checks out fine) and so while searching on other's experiences i found similar references that implied it was a CF card fault. I just need to get hold of the dumps to establish this which is the first hurdle.

Rgds
Pops

7

MiVoice Office 250/Mitel 5000 / Re: Call connection delay

« on: December 05, 2013, 12:35:12 PM »

Hmm, seems there is more to this than I thought. I am finding a good deal of M4000 WRN DB CP Numbering Plan Analysis: No Match With Table For x errors in the message print which appears to imply that there are indeed errors with the ARS. However, reading up on the error I find this: -

Cause: The software was searching for the specified object in the specified table and didn't find it. This indicates some form of software error. The software tried to handle the situation in a reasonable manner to continue service.

Action: Save the database. From Diagnostics Monitor/System Monitor, dump the “Numbering Plan Analysis” table via Database Records. Capture this information and send a report to Mitel Field Service.

I recreated the numbering plan but it doesn't seem to fix it. Also, I cannot find how to dump the analysis or any sign of Database Records. Any idea where this could be or is this specialised diagnostic equipment?

Suspect I may need to refer this up the chain.... 

Pops

8

MiVoice Office 250/Mitel 5000 / Re: Call connection delay

« on: December 04, 2013, 06:31:43 PM »

If you're in an area where 7-digit dialing is allowed the long timer is going to kick in...once you dial 7 digits it needs to wait to see if you're going to dial more before trying to route call.  Shortening timer will help this, but if a user hesitates in dialing a 10 digit number it will stop waiting and try to process as local.  If you are using 7 digits, try this: dial the number, then press pound.  This over-rides timer and tells system to route what you've dialed.  If this solves it it's time to start reducing the SHORT timer...this is the timer used after a valid number (7 digits) is dialed to wait for additional digits.  Long timer is only used until system sees a valid number (7 digits).

Cheers, interesting to learn of this. Any UK local number in their shortest form is comprised of 8 digits, while 11-digits are commonly used in their 'long' form. Therefore i presume that we'd almost never hit the short timer and instead the system is either trying to match against ARS or timing out (and so signifying an ARS issue) according to the long timer.

This has given me food for thought. I'm going to test tomorrow and post back.

Thanks both.
Pops

9

MiVoice Office 250/Mitel 5000 / Re: Call connection delay

« on: December 04, 2013, 02:59:55 PM »

Cheers AJ. I'm wondering whether the system is now always waiting for the Long Timer to expire before triggering the short timer. That would be approximately the same wait time that i've heard from the users.

But i see your point on ARS - presumably if it has to wait for the expiry of the LT then this perhaps is implying that it is not detecting a valid number combination? Odd really, nothing has changed with the routing but i'll take a look.

Rgds
Pops

10

MiVoice Office 250/Mitel 5000 / Call connection delay

« on: December 04, 2013, 07:55:24 AM »

Is there a timer or flag that controls the wait after the digits have been dialled and the outgoing call rings? Upgrading to V6 PR4 seems to have introduced a pause during this time which is making users think the call has failed.

Cheers
Pops

11

MiVoice Office 250/Mitel 5000 / Re: Mitel 5000 "Waiting for CP" Error

« on: November 18, 2013, 02:13:13 PM »

Does the system lock up with no calls possible when this alarm shows?

Is the system networked to another node or does it have File Based MOH?

Mitel just asked us the same question for a fault we've just escalated to them. We're seeing every handset display saying "Waiting for Resources" and no calls can be made/received on trunks and IC. Nothing much appears on the diagnostics other than the number of camped calls & time on camp increasing from reboot.

They instructed us to remove the MoH so inbetween reboots now. Is this the same fault?
Pops

ETA - Confirmed fault with file-based MoH only. Apparently the system consumes resources without releasing them. Frustratingly there are NO indications on either the front-end or via SysAdmin. Enquiring now for an ETA on the fix. Sorry for the thread hijack

I had the same issue on an out of hours upgrade to V6, no calls could be made.

Turned File Based MOH off on the instruction of Mitel and the issue went away, this bug has now been fixed in V6 PR2.

Excellent thanks for the update. I will relay this to our support team and schedule an upgrade.

12

MiVoice Office 250/Mitel 5000 / Re: Mitel 5000 "Waiting for CP" Error

« on: November 18, 2013, 10:28:30 AM »

Does the system lock up with no calls possible when this alarm shows?

Is the system networked to another node or does it have File Based MOH?

Mitel just asked us the same question for a fault we've just escalated to them. We're seeing every handset display saying "Waiting for Resources" and no calls can be made/received on trunks and IC. Nothing much appears on the diagnostics other than the number of camped calls & time on camp increasing from reboot.

They instructed us to remove the MoH so inbetween reboots now. Is this the same fault?
Pops

ETA - Confirmed fault with file-based MoH only. Apparently the system consumes resources without releasing them. Frustratingly there are NO indications on either the front-end or via SysAdmin. Enquiring now for an ETA on the fix. Sorry for the thread hijack

13

MiVoice Office 250/Mitel 5000 / Re: Accessing an off-node CO trunk

« on: September 22, 2013, 06:38:37 AM »

Ok, I think I got things working but ARS is a dog to get your heard around how it works.....

My understanding of it is that when off-noding calls, you need the 1st & 2nd dialling rules in the facility group so that the digits are off-loaded to the other side. As long as you have a rule that handles the node-local calls, it should route over an outgoing trunk (CO's in my case).

Also, i was tearing my hair out until i discovered that under Associated Extensions, Outgoing Access must be switched to the ARS extension (82000 in my case). Despite setting up the correct routing groups, it took me a while to realise that outgoing access on each of the phones was pointing to a CO trunk group...

My next step is figuring out how to route calls when the full international code is dialled so that a selection of countries go over their own routing facility while not affecting the rest of the I+ facility. Seems like some of my users have the full codes in their address books so this needs adding.

I wish there was a small app that was designed that you could load up with your routes and it would tell you where you call goes based on examples...

14

MiVoice Office 250/Mitel 5000 / Accessing an off-node CO trunk

« on: September 21, 2013, 03:50:58 AM »

Hi all

First poster here and not a seasoned Mitel admin but have learned so much after reading through the forum. I'm trying to make use of call routing between 5000's which are in different countries.

I have a 2-node system (HX & CS controllers running v6.1) that can now see each other and are correctly sharing off-node resources. For the moment, I've imported only phone extensions and b-channels between sites. I noticed that i can create an off-node b-channel station so i duplicated the extension numbers for the (ISDN2) CO lines from the node they are homed on to the other. It appears that i can now use the off-node CO line if i dial the individual extension number.

But, how can i pool the CO lines to use off-node? I cannot seem to find where i can create an off-node trunk group that will route to the same on the remote system. The end goal is to either change the dialling method to use ARS or have selected users press a softkey on the handset to use that off-node trunk to route calls.

Any pointers?

Cheers!
Popolou