02-22-2012 11:53 AM - edited 03-21-2019 05:23 AM
I need to reset a voicemail PIN on a Cisco 524s IP Phone. It is connected to a UC520. I can change the PIN in CME and reset it, but when I hit the voicemail button on the phone and put in the new PIN a voice says "Invalid entry".
I'm wondering if I need to factory reset the phone, but I can't find the method for doing that.
Can someone tell me what I need to do to reset the PIN on this phone? It seems like it should be something really simple.
Thanks,
Pete
02-22-2012 03:55 PM
Pete,
I assume that you're trying to reset the PIN in CLI. Do you have access to the CUE GUI? It's default address is 10.1.10.1. Just type that into a web browser and log in with your admin username and password. Find Users and the appropriate user associated with your phone. Click on it and scroll down to PIN. Click apply when you are finished changing the PIN. Should be as simple as that.
02-22-2012 04:15 PM
Thank you for the reply. I was never able to find a way to reset the PIN in the CLI. I'm pretty new to Cisco telephony products, but I don't believe this system has CUE. Is there a way to tell?
The way I have been trying to change the PIN is through Cisco Unified Communications Manager Express. I just browse to http://UC520-ip/ccme.html and login with the admin user/pass. I am able to change display names and extension labels, etc. here, just not the PIN. There is a field to enter a new PIN, but the change never happens after saving and resetting the phone. I don't get an error or anything.
Maybe I need to find out how to access the CUE gui? Or is there a way to change the PIN from the CLI?
Any help I can get with this will be greatly appreciated.
Thanks,
Pete
02-22-2012 04:17 PM
I would access the CUE GUI. Type 10.1.10.1 into a web browser and follow the instructions I gave in my first post. There is also a way to change it via CLI, but the GUI is much easier.
02-23-2012 07:24 AM
I don't get anything to come up when I browse to 10.1.10.1. I didn't set this system up, so it's possible that CUE is not running on the default ip. Can you tell me where to look to find out which ip CUE is using?
Thanks,
Pete
02-23-2012 08:11 AM
You should be able to do a "show run int in0/0" from the CLI and get the information about the module. My output is below, we can see the "service-module ip address 10.1.10.1" gives us the address of the CUE.
UC_560#show run int in0/0
Building configuration...
Current configuration : 279 bytes
!
interface Integrated-Service-Engine0/0
description Interface used to manage integrated application modulecue is initialized with default IMAP group
ip unnumbered Vlan90
service-module ip address 10.1.10.1 255.255.255.252
service-module ip default-gateway 10.1.10.2
02-27-2012 10:32 AM
Here is the output for 'show run int in0/0'
CIS_CDR#show run int in0/0
Building configuration...
Current configuration : 263 bytes
!
interface Integrated-Service-Engine0/0
description cue is initialized with default IMAP group
ip unnumbered Loopback0
ip nat inside
ip virtual-reassembly
service-module ip address 10.1.10.1 255.255.255.252
service-module ip default-gateway 10.1.10.2
end
It looks like it should be using 10.1.10.1, but I still don't get
anything when I browse to http://10.1.10.1
--
Pete
02-27-2012 11:26 AM
Looks like your PC may not have a route to the 10.1.10.x network. Post the following -
ipconfig (from the PC)
show ip int brief | ex un (from the UC)
02-27-2012 01:37 PM
Here is the output
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.1.10.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
CIS_CDR#show ip int brief | ex un
Interface IP-Address OK? Method Status Protocol
In0/0 10.1.10.2 YES TFTP up up
Vlan1 192.168.10.1 YES NVRAM up up
Vlan100 10.1.1.1 YES NVRAM up up
Loopback0 10.1.10.2 YES NVRAM up up
CIS_CDR#
I think it's odd that it shows the ip of In0/0 is 10.1.10.2, but yet the out put of 'show run int in0/0' says it's ip is 10.1.10.1.
CIS_CDR#show run int in0/0
Building configuration...
Current configuration : 263 bytes
!
interface Integrated-Service-Engine0/0
description cue is initialized with default IMAP group
ip unnumbered Loopback0
ip nat inside
ip virtual-reassembly
service-module ip address 10.1.10.1 255.255.255.252
service-module ip default-gateway 10.1.10.2
end
I've tried different IP's in the 10.1.10.x/24 range. I need a 192.168.10.x/24 ip to be able to telnet to the UC520.
02-28-2012 05:53 AM
It looks like your computer doesn't have a default gateway. Are you getting your IP via DHCP?
02-28-2012 08:30 AM
Normally the UC520 would assign me a 192.168.10.x/24 ip with the gateway 192.168.10.1 (the UC520). I've tried a lot of different IP settings on my PC. Which ip, subnet mask and gateway should I be using? I could post the UC520 and CUE configs if that would help.
Thanks,
Pete
02-28-2012 09:20 AM
I might would set my computer a static IP in the 192.168.10.1/24 range for the time being. I would then try to go to 10.1.10.1 on a web browser and change the PIN.
02-28-2012 10:45 AM
If your PC is on the same subnet as the UC data vlan, you should be getting a DHCP IP address in the same subnet. If that is not working, assign a 192.168.10.x/24, with 192.168.10.1 as the default gateway. This should help you connect to 10.1.10.1
You may want to start checking why DHCP isn't working - check DHCP settings on the UC, vlan and port settings on the switch you are connected to (if any).
02-28-2012 01:50 PM
DHCP does work. It assigns 192.168.10.x/24 ip's and everything works fine when I set my PC to use DHCP, except for not being able to open the CUE web gui on 10.1.10.1. I manually assigned my PC to use a 10.1.10.x/24 ip just to see if that would allow me to open the CUE web gui.
I have wondered if it could be a problem with my access-list. Below is the access-list config. Does anyone see something that I am missing that would prevent access to 10.1.10.1?
access-list 1 remark SDM_ACL Category=2
access-list 1 permit 10.1.1.0 0.0.0.255
access-list 1 permit 192.168.10.0 0.0.0.255
access-list 1 permit 10.1.10.0 0.0.0.3
access-list 100 remark auto generated by SDM firewall configuration
access-list 100 remark SDM_ACL Category=1
access-list 100 deny ip 192.168.10.0 0.0.0.255 any
access-list 100 deny ip host 255.255.255.255 any
access-list 100 deny ip 127.0.0.0 0.255.255.255 any
access-list 100 permit ip any any
access-list 101 remark auto generated by SDM firewall configuration
access-list 101 remark SDM_ACL Category=1
access-list 101 permit tcp 10.1.1.0 0.0.0.255 eq 2000 any
access-list 101 permit udp 10.1.1.0 0.0.0.255 eq 2000 any
access-list 101 deny ip 192.168.10.0 0.0.0.255 any
access-list 101 deny ip 10.1.1.0 0.0.0.255 any
access-list 101 deny ip host 255.255.255.255 any
access-list 101 deny ip 127.0.0.0 0.255.255.255 any
access-list 101 permit ip any any
access-list 102 remark auto generated by SDM firewall configuration
access-list 102 remark SDM_ACL Category=1
access-list 102 deny ip 10.1.10.0 0.0.0.3 any
access-list 102 deny ip 10.1.1.0 0.0.0.255 any
access-list 102 deny ip host 255.255.255.255 any
access-list 102 deny ip 127.0.0.0 0.255.255.255 any
access-list 102 permit ip any any
access-list 103 remark auto generated by SDM firewall configuration
access-list 103 remark SDM_ACL Category=1
access-list 103 permit tcp 10.1.10.0 0.0.0.3 any eq 2000
access-list 103 permit udp 10.1.10.0 0.0.0.3 any eq 2000
access-list 103 permit udp any 10.1.10.0 0.0.0.3 range 16384 32767
access-list 103 permit udp 10.1.10.0 0.0.0.3 range 16384 32767 any
access-list 103 deny ip 192.168.10.0 0.0.0.255 any
access-list 103 deny ip host 255.255.255.255 any
access-list 103 deny ip 127.0.0.0 0.255.255.255 any
access-list 103 permit ip any any
access-list 104 remark auto generated by SDM firewall configuration
access-list 104 remark SDM_ACL Category=1
access-list 104 deny ip 10.1.10.0 0.0.0.3 any
access-list 104 deny ip 192.168.10.0 0.0.0.255 any
access-list 104 deny ip 10.1.1.0 0.0.0.255 any
access-list 104 permit udp any eq bootps any eq bootpc
access-list 104 permit icmp any any echo-reply
access-list 104 permit icmp any any time-exceeded
access-list 104 permit icmp any any unreachable
access-list 104 deny ip 10.0.0.0 0.255.255.255 any
access-list 104 deny ip 172.16.0.0 0.15.255.255 any
access-list 104 deny ip 192.168.0.0 0.0.255.255 any
access-list 104 deny ip 127.0.0.0 0.255.255.255 any
access-list 104 deny ip host 255.255.255.255 any
access-list 104 deny ip any any
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide