Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
N/A

CUCM 8.6.2 Phones not registering 7841 and 8831

Hi all

I am trying to register some new phones - 7841 and 8831.  We installed the COP and Device Pack and rebooted the cluster.  Firmware defaults in the server are sip78xx.10-1-1SR2-1 and sip8831.9-3-3-5. 

These are the first phones of these models that we are trying to use.  All other devices are up and working.  I added the phones manually, auto-reg is disabled.  These new phones are both displaying the same behavior - they booted, but neither device will register.  They are both running the the same firmware version configured as the default in the server.

I have looked at some other discussions but haven't seen any solutions that match up with our issue.   Your input and ideas appreciated, thanks

Everyone's tags (1)
25 REPLIES
VIP Purple

Hi, can u share the show

Hi,

 

can u share the show version active from CLI of CUCM ?

 

regds,

aman

Anonymous
N/A

Hello AmanSorry about the

Hello Aman

Sorry about the delayed reply, and thanks for your input.  Here is the output from CLI...

Active Master Version: 8.6.2.22900-9

Thanks

 

VIP Purple

Hi, It shows no Device pack

Hi,

 

It shows no Device pack is added.

 

can u capture the complete output from CLI and share.

 

regds,

aman

Anonymous
N/A

Here is what we have

Here is what we have installed...

Active Master Version: 8.6.2.22900-9
Active Version Installed Software Options:
cmterm-cupc-dialrule-wizard-0.1.cop
cmterm-devicepack8.6.2.24123-1.cop
cmterm-9971.9-3-2-10.cop
cmterm-9951.9-3-2-10.cop
cmterm-7940-7960-sccp.8-1-2SR2.cop
cmterm-78xx.10-1-1SR2-1.cop
ciscocm.ntp_option.v1.0.cop
cmterm-devicepack8.6.2.24093-2.cop
cmterm-bfcp-e.8-6-2.cop
cmterm-7940-7960-sccp.8-0-9.cop
cmterm-7940-7960-sccp.8-1-1.cop
ciscocm.refresh_upgrade_v1.1.cop
cmterm-7945_7965-sccp.9-3-1SR2-1.cop

Hi,Please make sure that you

Hi,

Please make sure that you assign a DN to the phone for the SIP phone to register successfully.

HTH

Manish

 

Anonymous
N/A

Hello ManishSorry, I was away

Hello Manish

Sorry, I was away from the office.  Thanks for your input.  I assigned a DN and reset the phone.  Still hasn't registered.

Anonymous
N/A

The phone I tested with

The phone I tested with registered after a long delay.  I thought I had powered it off and back on, but perhaps not.  I assigned DNs to the other 8831 and the 7841 and all three phones are registered.  Thank you very much for your assistance.

Regards,

Ellen

Silver

I have similar problem like

I have similar problem like yours couple of days ago...this is what helped me:

- I have upgraded 8.6.1 to 8.6.2 with adequate device pack inside (you already have this)...

- defined 78XX phones but they didn't want to register...

- I restarted cluster one more time (maybe this was needed because of upgrade - not sure) and enabled auto-register...after this phones started registering in auto mode.

I'm not saying that this is proper solution for problem - but at least it's working :)

I think that with manual definition of phones everything should work - but that wasn't the case with me...

Anyway you can try above solution and see if it's working - the main fact is that it should work 100% one or another way...

BR,

Dragan

HTH, Dragan
New Member

I'm having this same problem.

I'm having this same problem. Over the weekend, I installed the latest device packs and restarted both servers in the cluster. I'm running CUCM 8.6.2 and the phones are 8831.

What's really strange is that the phone is getting incorrect info from the switch port. It's getting a DHCP address from the VLAN2 subnet, when it should be receiving an IP from the VLAN100 subnet.

VLAN2 = Data

VLAN100 = Voice

The original port config:

interface FastEthernet0/25
 description Workstations on VLAN2 - Phones on VLAN 100
 switchport access vlan 2
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 2
 switchport mode trunk
 switchport voice vlan 100
 srr-queue bandwidth share 10 10 60 20
 srr-queue bandwidth shape 10 0 0 0
 mls qos trust device cisco-phone
 mls qos trust cos
 auto qos voip cisco-phone
 spanning-tree portfast
end

 

I even changed the switch port configuration to this:

interface FastEthernet0/25
 description Workstations on VLAN2 - Phones on VLAN 100
 switchport access vlan 100
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 100
 switchport mode trunk
 switchport voice vlan 100
 srr-queue bandwidth share 10 10 60 20
 srr-queue bandwidth shape 10 0 0 0
 mls qos trust device cisco-phone
 mls qos trust cos
 auto qos voip cisco-phone
 spanning-tree portfast
end

 

VLAN 2 isn't even in the configuration, but the phone (even after a RESET) is still getting an IP from the DHCP server on VLAN2.

Very strange behavior.

Additional info:

The phone status menu is showing a continuous message of:

TFTP Timeout : SEPXXXXXXXXXXXX.cnf.xm.

No Trust List Installed.

 

Any suggestions / ideas would be appreciated.

Haven't tried this out but

Haven't tried this out but maybe the reason you're still getting a DHCP address from VLAN 2 is because you have a native vlan mismatch. The other side may still be configured with "native vlan 2" while the switch is configured with "native vlan 100".

Regards,

Yosh

HTH Regards, Yosh
New Member

I'm assuming by "the other

I'm assuming by "the other side" that you mean the 8831. That's the strange part, after doing a full reset on the 8831, it shows the operational VLAN ID of 100 and the Admin VLAN ID of 4095. (see attached)

It must be getting this VLAN 100 info from the switch, but it still has an IP address from VLAN 2.

 

Weird...

My apologies, I read this way

My apologies, I read this way too fast and thought that the config you posted was for the uplink of the switch.

Would you be able to post the config of your switch?

Regards,

Yahsiel

HTH Regards, Yosh
New Member

See attached. 

See attached. 

Silver

If you have catalyst (and I

If you have catalyst (and I think so) you only need these two commands on port connected to phone:

switchport access vlan X

switchport voice vlan Y

And you can put your QoS commands offcourse...this way you don't need to create trunk on port to phone because of voice and data vlan - switch is going to do that for you automatically by listening what device is on other end (ie CDP etc)...

BR,

Dragan

HTH, Dragan
New Member

Ok, I tried this and no luck.

Ok, I tried this and no luck. Based on your suggestion, I changed the port to this configuration:

interface FastEthernet0/25
 description Workstations on VLAN2 - Phones on VLAN 100
 switchport access vlan 2
 switchport trunk encapsulation dot1q
 switchport mode access
 switchport voice vlan 100
 srr-queue bandwidth share 10 10 60 20
 srr-queue bandwidth shape 10 0 0 0
 mls qos trust device cisco-phone
 mls qos trust cos
 auto qos voip cisco-phone
 spanning-tree portfast

No difference. The 8831 still shows the exact same info. Same VLAN 100, Admin VLAN 4095, IP address on the DATA Vlan, and all the same error messages.

It's frustrating that all 200+ of my other phones, including the 7937 can connect. This is the only one I've seen behave like this.

 

Silver

Where is DHCP located for

Where is DHCP located for phones?

You have option 150 on it?

BR,
Dragan

HTH, Dragan
New Member

DHCP for VLAN 100 (voice) is

DHCP for VLAN 100 (voice) is served by the 3750 switch stack. We have a windows DHCP server for VLAN 2 (data). Both of them server up the TFTP server.

The 8831 is showing the correct TFTP server address as well.

Silver

And other 200+ phones - they

And other 200+ phones - they receive their IP from DHCP for VLAN 100 fine? 

Or you configured them manualy?

Something is strange there - there is no way that only one phone makes troubles and the rest are working fine in same VLAN with same DHCP etc???

Dragan

HTH, Dragan
New Member

Yes - 18 locations, multiple

Yes - 18 locations, multiple routers/switches (all Cisco), same setup. All phones work fine, but this model of phone.

I'm truly stumped. What's strange is if I change all of the VLAN settings on the port to be VLAN 100 and I specify the allowed VLANs on the trunk as only 100, it still gets an IP from the DATA network.

... While typing this, I had a thought ...

--UPDATE: It's connected and working. I changed the settings on the phone from DHCP to STATIC and assigned it a VLAN 100 IP address from the phone system.

This is definitely not ideal. Plus, after heavily searching google, a LOT of people are having these same or very similar registration issues with this model of phone, and I wonder if there's a bug in the firmware that doesn't handle VLAN trunking or tagging correctly? How would I get this information to Cisco TAC to get them to look into it? Any suggestions?

Silver

You can always search cisco

You can always search cisco bug toolkit on cisco.com if you have adequate privileges with your CCO account.

Other options - try to write to tac@cisco.com some unofficial mail and I think that some of support engineers is going to answer you even if you don't have any official contract with cisco.

BR,

Dragan

HTH, Dragan
VIP Purple

Hi Mike, Just  guessing  7841

Hi Mike,

 

Just  guessing 

 

7841 Cannot join VLAN if broadcast over 30kbps
CSCun23612
Symptom:
7841 Devices are not able to process CDP response to gain VLAN knowledge from switch when large amount of broadcasts (30kbps / approx 40 to 60 pps) on VLAN/Subnet are occurring. 

The phone looks like it will still follow through with DHCP requests but will not accept the offered DHCP address due to the phone not knowing the VLAN structure.

** Issue does not occur when same amount of traffic is sent directly to the phone; only when it is broadcast traffic.

Conditions:
7841 on a switch port with a VLAN with a large amount of broadcasts occurring in subnet.

Workaround:
Reduce Broadcast traffic below 30kbps and reboot phone
or
Remove VLAN from Switch port that has the high Broadcast traffic.

 

[+5] to Dragan for extending support.

regds,

aman 

New Member

I was experiencing the exact

I was experiencing the exact same issue as Mike.  I put the phone behind a router on it's own network.  It received an IP address for the voice VLAN and registered without any issues.

Tim

Hi Mike,Did you get this

Hi Mike,

Did you get this resolved, i am having the same issue today, 7841's are getting IP address's from the data vlan when the switchport is configured as a trunk and not access.

Thanks, 

Richard

New Member

Hi,Not in the manner I wanted

Hi,

Not in the manner I wanted, but I did find that setting a fixed IP from the voice VLAN on the phone made it work. Using DHCP was the problem. Still no permanent solution, but I don't have a lot of these and they move rarely. If I do move them, I just have to remember to change the static IP and to update the reservation in the DHCP server.

I've seen issues with the

I've seen issues with the 78XX phones not registering due to MTU issues.  I'd suggest a packet capture from CUCM and phone side.

 

I had to lower the MTU on my CUCM servers to get my 7861s to register.

8049
Views
15
Helpful
25
Replies
CreatePlease to create content