Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: Enobaham on October 18, 2019, 07:53:09 PM

Title: Wrong caller id on transfer on night mode
Post by: Enobaham on October 18, 2019, 07:53:09 PM

We have a 3300 cx ii. 3 different companies programmed in the pbx with different tenant numbers. 1, 2, and 3. Issue is with company 2

When a call comes in during night mode it is forwarded to a speed call which calls the owners cell phone. The issue is that the caller id showing up on the owners phone is the wrong caller id. It is the caller id from company 1 (Not even his own, which is company 2). He would like the calling parties caller id to be passed on to his cell phone.

When a call comes in, it hits mailbox 4000 which gives them the AA tree. The issue I can't seem to work around is that 4000 does not show up in the User and Services Configuration sheet where I could then add a CPN substitution. The only COS I can find for 4000 is on the MiCollab NuPoint web console.

It seems to be using the default (company 1) main number as the caller id sent to the owners cell phone. How can we get it to work so the callers caller id can be sent to the owners cell phone so he knows who is calling?

We looked at setting up a phantom but that seems convoluted and not actually a phantom. If there is a work around for this then any help would be greatly appreciated.

Title: Re: Wrong caller id on transfer on night mode
Post by: ZuluAlpha on October 21, 2019, 01:44:59 PM

In Maintenance Commands try LOCATE NUMBER 4000

You could probably add CPN Substitution for the speed call under Telephone Directory Management > Associated Directory Numbers. However that wouldn't pass along calling party ID, you can only use numeric digits there.

4000 may already be a phantom appearance which is how it gets to the NuPoint.

Title: Re: Wrong caller id on transfer on night mode
Post by: PC77375 on October 23, 2019, 04:16:07 PM

You will need to look at your trunk settings under the ISDN protocol- "Replace external CLID" , and set to yes. Test this option, and see if it achieves what you are looking for.

Keep in mind that this may not work because many carriers are blocking "unauthorized number" call origination.  This type of service can appear as a "fraud" call to the provider as it did not originate from an authorized and billable DID on your service account.
If you are using SIP trunks, it is even more likely that it will not work.