I am setting up MVA and have run into a strange issue. The setup is as follows:
Local CUCM DN: 5551234
Remote Destination: 19995551234
The remove destination number listed above is associated with the cucm dn above as well.
When I dial in to the MVA access number and am prompted to enter the remote destination number, I enter the number above and the associated pin. I then hit "1" to dial a number and can successfully dial another local DN 5556789# successfully.
The problem is when I set the remote destination number to 5551234. This was by request of the customer. When I dial in, enter the new remote destination of 5551234# (same as actual DN) and the pin, I am authenticated. I then press "1" to dial a number and then enter the same 5556789# after which I am taken back to the original message to login with my remote destination number.
For some reason when I use a remote destination number that is the same as my actual DN it seems to be causing a problem. I am using an MGCP controlled voice gateway and at the moment not interested in number reach.
Any idea's what restrictions are in place for remote destination extensions other than the length? I was under the impression it could be anything and could be used basically as an access code/pin to get into the cucm. Not sure if having the remote destination number as the same as the actual user and DN would cause an issue?
