Mitel Forums - The Unofficial Source
Mitel Forums => MiVoice Office 250/Mitel 5000 => Topic started by: dan231 on July 20, 2017, 05:10:26 PM
-
I setup a new phone extension at a branch location. I am not able to forward a vm to this extension. I get an error that this is not a valid extension. Did I miss a flag or setting?
-
This is what I am doing.
After listening to a message, you have the following options:
Press 1 to replay the message from the beginning.
Press 3 to forward a copy of the message to anot
her subscriber. If you want to include an
introduction, press
Opt 3: I enter 1234 (a valid ext at a diff branch, it states the number entered is not valid.
-
Does the extension have a mailbox?
In what system does the mailbox exist, or is your voicemail networked (not part of normal networking, VM networking is completely different)?
Did you Export/Import to the other network nodes?
-
Are you licensed for networked voice mail? If not, you'll need to purchase and apply the licenses, or centralize the mailboxes on one controller.
-
Does the extension have a mailbox?
In what system does the mailbox exist, or is your voicemail networked (not part of normal networking, VM networking is completely different)?
Did you Export/Import to the other network nodes?
How can I check the nodes? I didn't do anything other than setup the local extension/user/vm box
Are you licensed for networked voice mail? If not, you'll need to purchase and apply the licenses, or centralize the mailboxes on one controller.
Yes - I am licensed for this. It's just this one mailbox that isn't reachable, so I think I missed a setting somewhere.
-
Does the extension have a mailbox?
In what system does the mailbox exist, or is your voicemail networked (not part of normal networking, VM networking is completely different)?
Did you Export/Import to the other network nodes?
How can I check the nodes? I didn't do anything other than setup the local extension/user/vm box
You can go into your Phones or Mailboxes on the system local to you, then open the remote node in that menu and see if it is there... since this is a mailbox issue I would look at the mailbox first. On the system you are trying to send the message from, go to Voice Processor - Devices - Mailboxes - Node XX (whatever node the mailbox you are trying to send to is on) and see if the mailbox is listed, otherwise the system doesn't know where it is. If it isn't there, do a full Export/Import of devices to all network nodes.
Are you licensed for networked voice mail? If not, you'll need to purchase and apply the licenses, or centralize the mailboxes on one controller.
Yes - I am licensed for this. It's just this one mailbox that isn't reachable, so I think I missed a setting somewhere.
Only the licensing and POP/SMTP configuration is required for VM networking, nothing is required on the mailbox level, you just need to keep the systems in sync by performing regular Export/Import functions when making changes.
-
do a full Export/Import of devices to all network nodes.
This is most likely my issue - I was not aware I needed to do any type of import/export.
Where can I learn how to do this properly?
-
do a full Export/Import of devices to all network nodes.
This is most likely my issue - I was not aware I needed to do any type of import/export.
Where can I learn how to do this properly?
To do an Export/Import? It is quite simple actually, in DB Studio (the programming software) at the top open the Operations drop-down, select Export/Import devices, then in the resulting window select all nodes, select all types of information, and then Export, when that is done, Import. Make sure to do it in that order, because after an Import you must restart the programming software. Make sure you are not logged into other nodes when doing this, the process will fail.
For other maintenance, contact your vendor for training or have them sponsor you to an official Mitel system administration course.
-
do a full Export/Import of devices to all network nodes.
This is most likely my issue - I was not aware I needed to do any type of import/export.
Where can I learn how to do this properly?
To do an Export/Import? It is quite simple actually, in DB Studio (the programming software) at the top open the Operations drop-down, select Export/Import devices, then in the resulting window select all nodes, select all types of information, and then Export, when that is done, Import. Make sure to do it in that order, because after an Import you must restart the programming software. Make sure you are not logged into other nodes when doing this, the process will fail.
For other maintenance, contact your vendor for training or have them sponsor you to an official Mitel system administration course.
This makes me nervous - will any good data get overridden?
-
do a full Export/Import of devices to all network nodes.
This is most likely my issue - I was not aware I needed to do any type of import/export.
Where can I learn how to do this properly?
To do an Export/Import? It is quite simple actually, in DB Studio (the programming software) at the top open the Operations drop-down, select Export/Import devices, then in the resulting window select all nodes, select all types of information, and then Export, when that is done, Import. Make sure to do it in that order, because after an Import you must restart the programming software. Make sure you are not logged into other nodes when doing this, the process will fail.
For other maintenance, contact your vendor for training or have them sponsor you to an official Mitel system administration course.
This makes me nervous - will any good data get overridden?
All it is doing is telling the other systems in the network what devices are where, it doesn't over-write anything on the remote nodes, if there is a conflict (which there likely will be for some things, it's normal in some cases) the local system data has precedence. You are basically just updating there "where is it" database, so when you add x1234 in Node 4 until you tell nodes 1, 2, and 3 where it is they won't know and will consider 1234 an unused extension, once you Export/Import the remote lists come into sync and Node 1 now knows "Hey, the user dialed 1234, that's in Node 4 so I need to shoot it across the Intertel Networking link to IP XX.XX.XX.XX". In other words, it is just updating it's remote device database.
This is not an automated process, and should be done whenever extension are added or taken away, and by "extensions" I mean anything with an extension number such as phones, phantoms, hunt groups, applications, mailboxes, etc. otherwise remote systems don't know about the addition/deletion.
This is a safe process.
-
ok great - I will give this a try.
So I fulyl understand the process - I open Branch A DB Studio. Export all (like you instructed), Export.
Go to Branch B and import - or just choose import right after the export?
Do I then repeat for all branches?
-
ok great - I will give this a try.
So I fulyl understand the process - I open Branch A DB Studio. Export all (like you instructed), Export.
Go to Branch B and import - or just choose import right after the export?
Do I then repeat for all branches?
No... You Export then Import from the same node... the terminology of "export and import" as we normally see them is what is catching you up.
When you export, select all nodes and all devices, then click Export, the MiVO system will export it's device database to all other nodes in the network automatically via the Intertel VoIP Networking links, then when it is done you want to Import, which will reach out to all nodes in the network the same way and ask them to essentially perform an Export back to the node requesting an Import.
It is usually best to perform this on the node that you made the changes on. You don't normally do this from every node, just the one you made the changes on... if the systems are very much out of sync, performing this process on 2 or 3 nodes will correct them all as the remote databases are a sort of "shared" form.
-
ok great - I will give this a try.
So I fulyl understand the process - I open Branch A DB Studio. Export all (like you instructed), Export.
Go to Branch B and import - or just choose import right after the export?
Do I then repeat for all branches?
No... You Export then Import from the same node... the terminology of "export and import" as we normally see them is what is catching you up.
When you export, select all nodes and all devices, then click Export, the MiVO system will export it's device database to all other nodes in the network automatically via the Intertel VoIP Networking links, then when it is done you want to Import, which will reach out to all nodes in the network the same way and ask them to essentially perform an Export back to the node requesting an Import.
It is usually best to perform this on the node that you made the changes on. You don't normally do this from every node, just the one you made the changes on... if the systems are very much out of sync, performing this process on 2 or 3 nodes will correct them all as the remote databases are a sort of "shared" form.
It was easy enough. I did this on the Branch I added the extension. Restarted the DB Programming but I am still getting the same error when I try to fwd the vm.
-
OK, so go to the MiVO system you are located on, and look in the database... does the local system know the the extension and mailbox exist on the remote node?
-
OK, so go to the MiVO system you are located on, and look in the database... does the local system know the the extension and mailbox exist on the remote node?
Not from Voice Processor, Devices, Mailboxes Any where I look on that branch, this new ext is not listed.
-
OK, so go to the MiVO system you are located on, and look in the database... does the local system know the the extension and mailbox exist on the remote node?
Not from Voice Processor, Devices, Mailboxes Any where I look on that branch, this new ext is not listed.
We need to determine if you are really using stand-alone independent voicemail systems, networked voicemail systems (which is really not that common), or if one system is the "centralized" voicemail server for all/most nodes... Or if we actually have synchronization problem or numbering conflict. Unfortunately I am running out of time and cannot assist you right now, perhaps later today or over the weekend.
-
OK, so go to the MiVO system you are located on, and look in the database... does the local system know the the extension and mailbox exist on the remote node?
Not from Voice Processor, Devices, Mailboxes Any where I look on that branch, this new ext is not listed.
We need to determine if you are really using stand-alone independent voicemail systems, networked voicemail systems (which is really not that common), or if one system is the "centralized" voicemail server for all/most nodes... Or if we actually have synchronization problem or numbering conflict. Unfortunately I am running out of time and cannot assist you right now, perhaps later today or over the weekend.
Ok, fair enough - thanks.
I can tell you that each voicemail is on its own controller at the local branch.
-
So if you are sure that each branch has it's own voicemail service and the mailboxes are all hosted on the local controller, we need to look at potential sync issues... Try a Export/Import and look at the System Output and see if there is any issue with the sync... for testing purposes, just go to the site that has the new x1234 and perform the export, then check the logs on both systems and see if a change was rejected due to a conflict.
-
Finally got in front of a system today... So just to confirm the location of the remote node mailboxes, if you to Voice Processor - Devices - Mailboxes, you have a "Local - VP Local Node" and other remote nodes listed at this level, are the remote node mailboxes inside the remote nodes at this level, or do you have to click into "Local - VP Local Node" and inside of that the other nodes are listed and the remote mailboxes are under this level?
-
So if you are sure that each branch has it's own voicemail service and the mailboxes are all hosted on the local controller, we need to look at potential sync issues... Try a Export/Import and look at the System Output and see if there is any issue with the sync... for testing purposes, just go to the site that has the new x1234 and perform the export, then check the logs on both systems and see if a change was rejected due to a conflict.
Correct. Each branch has it's own local controller and voicemail. I don't know how to check logs.
Finally got in front of a system today... So just to confirm the location of the remote node mailboxes, if you to Voice Processor - Devices - Mailboxes, you have a "Local - VP Local Node" and other remote nodes listed at this level, are the remote node mailboxes inside the remote nodes at this level, or do you have to click into "Local - VP Local Node" and inside of that the other nodes are listed and the remote mailboxes are under this level?
On my local controller: I go to Voice Processor : Devices : Mailboxes. I do have a local and a PP200, PP201, PP202. Each branch is a PP#. The ext 1234 is at PP200. Under PP200, Local, which is empty. and PP200, 97002, 97003, 97004 - which are all the other branches. The branch where 1234 is at, is PP200/97002. All exts for this branch are listed except for 1234
-
Found logs under Favorites : Software. I checked the cp_database_log and see no errors that jump out at me.
Since this is a new user - does their vm have to be setup fully for this to work? As in, they logged into it, reset password, recorded name, etc?
-
Found logs under Favorites : Software. I checked the cp_database_log and see no errors that jump out at me.
Since this is a new user - does their vm have to be setup fully for this to work? As in, they logged into it, reset password, recorded name, etc?
It shouldn't matter if the mailbox is setup or not... I am puzzled now, going to have to defer to someone else because my knowledge of networked voicemail systems is very limited and this seems to be going beyond what I have done. Sorry.
-
Found logs under Favorites : Software. I checked the cp_database_log and see no errors that jump out at me.
Since this is a new user - does their vm have to be setup fully for this to work? As in, they logged into it, reset password, recorded name, etc?
It shouldn't matter if the mailbox is setup or not... I am puzzled now, going to have to defer to someone else because my knowledge of networked voicemail systems is very limited and this seems to be going beyond what I have done. Sorry.
I appreciate the assistance! Thanks
-
dan231,
Did you create the associated mailbox on your local system to match the one on the remote system?
Go to Voice Processor > Devices > Mailboxes > {VPIM NODE} > {97xxx} >
Right-Click and then select Create Associated Off-Node Mailbox. You should see a list of devices and then you select the extension of the person you created on the remote node. Now this is all predicated on the fact that you have already done an Import/Export of the remote node so that you can see the remote extension to create a mailbox for it.
At this point I can't remember if the Remote Mailbox Extension field is checked or not. I think it is for Associated Mailboxes, but not for Non-Associated Mailboxes; since they don't have to be the same extension number at both locations.
See if that solves your problem.
Thanks,
TE
-
Right-Click and then select Create Associated Off-Node Mailbox. You should see a list of devices and then you select the extension of the person you created on the remote node. Now this is all predicated on the fact that you have already done an Import/Export of the remote node so that you can see the remote extension to create a mailbox for it.
I did the export/import and the ext in question is still not showing up. Could this be the way the ext was created?
-
dan231,
If the extension is up and working at the remote site then your problem is not with how it was created, but whether or not the extension conflicts with another extension in the other nodes.
What you can do to prove this point is try creating that extension as a new extension on your node. If it let's you do it then there is an issue, if it doesn't then you need to find where that extension conflict occurs within your node.
This is typically a simple process, IF the systems are maintained properly. It sounds as though you haven't been performing Imports/Exports every time you create a new extension, but it should take care of that for you over time. What you won't notice is whether you have issues with conflicts until it is too late.
Thanks,
TE
-
Import/export isn't required when new extensions are created. They are automatically populated across the network to remote nodes, pretty much in real time.
-
Import/export isn't required when new extensions are created. They are automatically populated across the network to remote nodes, pretty much in real time.
Then this isn't happening for me. :(
-
Maybe this is a silly question, but does the new extension have a system forwarding path to voice mail?
-
Maybe this is a silly question, but does the new extension have a system forwarding path to voice mail?
Under devices/phones/forwarding paths, the new ext is setup exactly like other working extensions.
-
If it's an intercom call, the Fwd Call Type-IC Calls needs to be set to yes, on the system forwarding path. Devices>Phones>Ext>Fwd Path
-
If it's an intercom call, the Fwd Call Type-IC Calls needs to be set to yes, on the system forwarding path. Devices>Phones>Ext>Fwd Path
Its set to yes already. It appears the issue is ONLY with exts with 123X same branch, but 121X or 122X work fine - even brand new ext???!!!
-
Maybe an ext conflict with the calling node, preventing an import of numbers from the one where 123X numbers reside? In the calling node try to create a new phone with a 123X extension (even though you don't really want to). I'm betting it will give you an errer message telling you what device at the calling node is already using 123. If it does, just renumber the offending device and redo import.
-
Maybe an ext conflict with the calling node, preventing an import of numbers from the one where 123X numbers reside? In the calling node try to create a new phone with a 123X extension (even though you don't really want to). I'm betting it will give you an errer message telling you what device at the calling node is already using 123. If it does, just renumber the offending device and redo import.
Which controller is the"calling node"
Also, my phone support (TelCom support we bought the system from) is telling me NOT to do an export/import. States they have seen an increase of this causing a lot of system errors/corruption.
-
Also, my phone support (TelCom support we bought the system from) is telling me NOT to do an export/import. States they have seen an increase of this causing a lot of system errors/corruption.
Then they are obviously clueless.
-
Also, my phone support (TelCom support we bought the system from) is telling me NOT to do an export/import. States they have seen an increase of this causing a lot of system errors/corruption.
Then they are obviously clueless.
I'm not arguing that
-
dan231,
First of all an Import/Export will find system errors and can be an indicator for corruption, but it will not cause it.
There has to be something about this new extension you created that is not right. Have you tried creating another extension that you know doesn't exist in either system and see if that works?
Thanks,
TE
-
dan231,
First of all an Import/Export will find system errors and can be an indicator for corruption, but it will not cause it.
There has to be something about this new extension you created that is not right. Have you tried creating another extension that you know doesn't exist in either system and see if that works?
Thanks,
TE
Yes I have tried that. It is a problem with ext 123X. When enter the ext to forward to, I get to 1,2,3, then it states not a valid number. I never get to enter in the last digit.
-
dan231,
Do you really have your heart set on making this extension work even if you found a work-around with a new extension or are you just trying to figure out why it is happening?
In your local system [the calling node], have you tried to create extension 123x as a local phone to see what it tells you; it should provide an error.
Thanks,
TE
-
dan231,
Do you really have your heart set on making this extension work even if you found a work-around with a new extension or are you just trying to figure out why it is happening?
In your local system [the calling node], have you tried to create extension 123x as a local phone to see what it tells you; it should provide an error.
Thanks,
TE
I would say my concern at this point is will I ever be able to use the 123X range of extensions?
I did try to create a local phone 1234 - I get a conflict error that points to the existing off-node phone and mailbox in the other branch
-
dan231,
So, when you try to create the associated mailbox in your local node for their Voice Processor node it doesn't show up?
Have you verified that this phone and mailbox error is showing up for the node you expect it to be in?
Thanks,
TE
-
dan231,
So, when you try to create the associated mailbox in your local node for their Voice Processor node it doesn't show up?
Have you verified that this phone and mailbox error is showing up for the node you expect it to be in?
Thanks,
TE
Are you referring to creating an associated mailbox? If so, then yes, I see no branch phones listed to add. I was getting the error under my local controller/devices/phones.
-
If it hasn't been done already, I would delete the offending extension and rebuild it.
-
dan231,
You will need to create the associated mailbox under the Voice Processor not System > Devices and Feature Codes > Phones; that wouldn't work at all. Look at my previous post on how to create the associated mailbox for an off-node device.
Thanks,
TE
-
I have no idea what the phone tech guy did -
"With Mitel’s assistance, we made a change in the Mitel 5000 which should resolve the issue"
It works now, but I have no idea what was done and the tech is on PTO this week