cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Get the latest Cisco news in this December issue of the Cisco Small Business Monthly Newsletter

3799
Views
0
Helpful
8
Replies
Highlighted
Participant

UC540 - Phones getting data vlan IP not voice vlan IP

Phones on a UC540 are getting IP addresses from a Windwos server connected to vlan1 (data vlan) and not from the local UC540 vlan 100 voice vlan. In looking at the dhcp debug, when the phone is reset, it is only looking on vlan 1 for an IP address. The switchport voice vlan 100 command does not seem to be doing anything. This was configured with CCA. IOS is uc500-advipservicesk9-mz.124-24.SB and CUE is 7.0.3.

Debug below and applicable IOS commands- help appreciated. Note data vlan is 192.168.64.0 and voice vlan is 10.1.1.0

The phone in the example is on port f0/1/0, but the issue occurs on all phones.

ip dhcp relay information trust-all
ip dhcp excluded-address 10.1.1.1 10.1.1.9
ip dhcp excluded-address 10.1.1.241 10.1.1.255
!
ip dhcp pool phone
   network 10.1.1.0 255.255.255.0
   default-router 10.1.1.1
   option 150 ip 10.1.1.1
   dns-server 68.4.16.30 68.4.16.25

interface FastEthernet0/1/0
switchport voice vlan 100
macro description cisco-phone
spanning-tree portfast

interface Vlan1
no ip address
bridge-group 1
bridge-group 1 spanning-disabled
!
!
interface Vlan100
no ip address
bridge-group 100
bridge-group 100 spanning-disabled
!
!
interface BVI1
description $FW_INSIDE$
ip address 192.168.64.5 255.255.255.0 secondary
ip address 192.168.64.1 255.255.255.0
ip nat inside
ip virtual-reassembly
!
!
interface BVI100
description $FW_INSIDE$
ip address 10.1.1.1 255.255.255.0
ip nat inside
ip virtual-reassembly

resetting 0026.CB3D.BE11
UC_540(config-ephone)#
007327: Oct 22 15:50:57.156: %PARSER-5-CFGLOG_LOGGEDCMD: User:fcadmin  logged command:reset
007328: Oct 22 15:50:57.440: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP0026CB3DBE11 IP:192.168.64.100 Socket:4 Device                     Type:Phone has unregistered normally.
007329: Oct 22 15:51:23.596: DHCPD: client's VPN is .
007330: Oct 22 15:51:23.596: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbe.11.
007331: Oct 22 15:51:23.596: DHCPD: no subnet configured for 192.168.64.100.
007332: Oct 22 15:51:23.596: DHCPD: Finding a relay for client 0100.26cb.3dbe.11 on interface BVI1.
007333: Oct 22 15:51:23.596: DHCPD: Seeing if there is an internally specified pool class:
007334: Oct 22 15:51:23.596:   DHCPD: htype 1 chaddr 0026.cb3d.be11
007335: Oct 22 15:51:23.596:   DHCPD: remote id 020a0000c0a84001f1000000
007336: Oct 22 15:51:23.596:   DHCPD: circuit id 00000000
007337: Oct 22 15:51:23.596: DHCPD: there is no pool for 192.168.64.1.
007338: Oct 22 15:51:23.596: DHCPD: there is no pool for 192.168.64.5.
007339: Oct 22 15:51:23.632: DHCPD: client's VPN is .
007340: Oct 22 15:51:23.632: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbe.11.
007341: Oct 22 15:51:23.632: DHCPD: no subnet configured for 192.168.64.100.
007342: Oct 22 15:51:23.632: DHCPD: Finding a relay for client 0100.26cb.3dbe.11 on interface BVI1.
007343: Oct 22 15:51:23.632: DHCPD: Seeing if there is an internally specified pool class:
007344: Oct 22 15:51:23.632:   DHCPD: htype 1 chaddr 0026.cb3d.be11
007345: Oct 22 15:51:23.632:   DHCPD: remote id 020a0000c0a84001f1000000
007346: Oct 22 15:51:23.632:   DHCPD: circuit id 00000000
007347: Oct 22 15:51:23.632: DHCPD: there is no pool for 192.168.64.1.
007348: Oct 22 15:51:23.632: DHCPD: there is no pool for 192.168.64.5.
007349: Oct 22 15:51:35.208: %IPPHONE-6-REG_ALARM: 22: Name=SEP0026CB3DBE11 Load= SCCP75.8-4-2S Last=Reset-Reset
007350: Oct 22 15:51:35.212: %IPPHONE-6-REGISTER: ephone-1:SEP0026CB3DBE11 IP:192.168.64.100 Socket:4 DeviceType:Phone has registered.

Everyone's tags (3)
8 REPLIES 8
Enthusiast

Re: UC540 - Phones getting data vlan IP not voice vlan IP

Can you add the "switchport mode access" command under the interface?

Another thing to check is to make sure that CDP is enabled on the phone.  I'm not sure what model you are using, but in the settings pages, there is a place to navigate to make sure CDP is enabled on the phone.

Also, run "show cdp neighbors" to make sure that you are seeing the phone as a cisco device.  This will also confirm that CDP is working on the UC500.

Participant

Re: UC540 - Phones getting data vlan IP not voice vlan IP

CDP is enabled and showing as expected-

UC_540#sho cdp neig
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
SEP0026CB3DBE11  Fas 0/1/0          150           H       IP Phone  Port 1
SEP0026CB3DBD29  Fas 0/1/7          138           H       IP Phone  Port 1
SEP0026CBBD9E31  Fas 0/1/5          125           H       IP Phone  Port 1
SEP0026CB3DBC7B  Fas 0/1/3          128           H       IP Phone  Port 1
SEP0026CBBDA36B  Fas 0/1/2          145           H       IP Phone  Port 1
SEP002699F021E5  Fas 0/1/6          171           H       IP Phone  Port 1
SEP0026CB3DBD8E  Fas 0/1/4          141           H       IP Phone  Port 1

Since PCs are connected to the 7975 phone switch port, I'm not sure why I would add "switchport mode access" since that is set by default.

This seems more like a bug than a configuration issue. If you notice, when a phone resets or boots up and searches for DHCP, it never looks at VLAN100 (see prior post) and only looks at VLAN1 for an IP address. Normally, when a phone is connected the "switchport voice vlan 100" command forces the phone to look at vlan 100 for the dhcp boot parameters.

Cisco Employee

Re: UC540 - Phones getting data vlan IP not voice vlan IP

There is a bug in some firmware versions that the phone will send a DHCP request on the data vlan instead of the voice VLAN.  Assuming that you have the voice vlan set properly in the switch (and CDP is enabled), it would be prudent to ensure that the phone is on the most recent firmware.

Try setting option 150 in your data VLAN and resetting the phone.  As long as the data VLAN is routeable to the voice VLAN, the phone will still request the config from CME's TFTP.  If you have a recent phoneload specified on the UC500 system, it will then download the new phoneload, apply it, fix the bug, and re-request the DHCP address from the voice vlan.

Participant

Re: UC540 - Phones getting data vlan IP not voice vlan IP

Is this a bug with 8-4-2S on the 7975? That is the 7975 software that is current on the UC540....

DeviceName        CurrentPhoneload       PreviousPhoneload      LastReset
=====================================================================
SEP0026CB3DBE11    SCCP75.8-4-2S          SCCP75.8-4-2S         Reset-Reset
SEP0026CBBDA36B    SCCP75.8-4-2S          SCCP75.8-4-2S         UCM-closed-TCP
SEP0026CBBD9E31    SCCP75.8-4-2S          SCCP75.8-4-2S         UCM-closed-TCP
SEP0026CB3DBD8E    SCCP75.8-4-2S          SCCP75.8-4-2S         UCM-closed-TCP
SEP002699F021E5    SCCP75.8-4-2S          SCCP75.8-4-2S         Reset-Reset


load 7975 SCCP75.8-4-2S

Cisco Employee

Re: UC540 - Phones getting data vlan IP not voice vlan IP

If you got a packet capture during boot so that we could look at the CDP exchange, we'd be able to identify if the issue is on the phone or the UC500 side.

It may be easier to just put the latest 7975 firmware on a phone, though, to rule out a known bug in the IP phone firmware.

Also, you don't have a helper-address configured anywhere on the voice VLAN, do you?  Does 'sh int g1/0/1 switchport | i Voice' show the correct VLAN?

Re: UC540 - Phones getting data vlan IP not voice vlan IP

by any strange chance do you have Telephony-Service 'no auto-reg' set?

Participant

Re: UC540 - Phones getting data vlan IP not voice vlan IP

No.

Looks like I need to try to find the latest 7975 phone load and upload to the chassis, turn off the vlan 1 dhcp server then reset all the phones. Hopefully that will fix the issue.

I will update everyone....

Participant

Re: UC540 - Phones getting data vlan IP not voice vlan IP

Here is the latest attempt at nothing....

Turned off Windows DHCP server. Reset all phones. All phones then accurately requested an IP address from VLAN100 and were given an IP from the VLAN100 DHCP pool.

As soon as I turned on the Windows DHCP server, the phones dropped the vlan100 IP address and requested a vlan1 address.....oh boy. I will have to go with the phone bug at this point and look at the manual software load for the fix...the fun never stops.

Bindings from all pools not associated with VRF:
IP address          Client-ID/              Lease expiration        Type
                    Hardware address/
                    User name
10.1.1.10           0100.26cb.3dbe.11       Oct 26 2010 10:54 PM    Automatic
10.1.1.11           0100.26cb.3dbd.8e       Oct 26 2010 10:55 PM    Automatic
10.1.1.12           0100.26cb.bda3.6b       Oct 26 2010 10:55 PM    Automatic
10.1.1.13           0100.2699.f021.e5       Oct 26 2010 10:55 PM    Automatic
10.1.1.14           0100.26cb.3dbd.29       Oct 26 2010 10:55 PM    Automatic
10.1.1.15           0100.26cb.3dbc.7b       Oct 26 2010 10:56 PM    Automatic
10.1.1.16           0100.26cb.bd9e.31       Oct 26 2010 10:55 PM    Automatic
UC_540#wr mem
Building configuration...


028770: Oct 25 22:58:43.417: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1/8, changed state to up

UC_540#
UC_540#
028771: Oct 25 22:59:15.901: DHCPD: client's VPN is .
028772: Oct 25 22:59:15.901: DHCPD: DHCPRELEASE message received from client 0100.26cb.3dbd.29 (10.1.1.14).
028773: Oct 25 22:59:15.901: DHCPD: Sending notification of TERMINATION:
028774: Oct 25 22:59:15.901:  DHCPD: address 10.1.1.14 mask 255.255.255.0
028775: Oct 25 22:59:15.901:  DHCPD: reason flags: RELEASE
028776: Oct 25 22:59:15.901:   DHCPD: htype 1 chaddr 0026.cb3d.bd29
028777: Oct 25 22:59:15.901:   DHCPD: lease time remaining (secs) = 86188
028778: Oct 25 22:59:15.901: DHCPD: returned 10.1.1.14 to address pool phone.
028779: Oct 25 22:59:15.901: DHCPD: client's VPN is .
028780: Oct 25 22:59:15.901: DHCPD: DHCPRELEASE message received from client 0100.26cb.3dbd.8e (10.1.1.11).
028781: Oct 25 22:59:15.901: DHCPD: Sending notification of TERMINATION:
028782: Oct 25 22:59:15.901:  DHCPD: address 10.1.1.11 mask 255.255.255.0
028783: Oct 25 22:59:15.901:  DHCPD: reason flags: RELEASE
028784: Oct 25 22:59:15.901:   DHCPD: htype 1 chaddr 0026.cb3d.bd8e
028785: Oct 25 22:59:15.901:   DHCPD: lease time remaining (secs) = 86173
028786: Oct 25 22:59:15.905: DHCPD: returned 10.1.1.11 to address pool phone.
028787: Oct 25 22:59:15.905: DHCPD: client's VPN is .
028788: Oct 25 22:59:15.905: DHCPD: DHCPRELEASE message received from client 0100.26cb.3dbe.11 (10.1.1.10).
028789: Oct 25 22:59:15.905: DHCPD: Sending notification of TERMINATION:
028790: Oct 25 22:59:15.905:  DHCPD: address 10.1.1.10 mask 255.255.255.0
028791: Oct 25 22:59:15.905:  DHCPD: reason flags: RELEASE
028792: Oct 25 22:59:15.905:   DHCPD: htype 1 chaddr 0026.cb3d.be11
028793: Oct 25 22:59:15.905:   DHCPD: lease time remaining (secs) = 86095
028794: Oct 25 22:59:15.905: DHCPD: returned 10.1.1.10 to address pool phone.
028795: Oct 25 22:59:15.905: DHCPD: client's VPN is .
028796: Oct 25 22:59:15.905: DHCPD: DHCPRELEASE message received from client 0100.2699.f021.e5 (10.1.1.13).
028797: Oct 25 22:59:15.905: DHCPD: Sending notification of TERMINATION:
028798: Oct 25 22:59:15.905:  DHCPD: address 10.1.1.13 mask 255.255.255.0
028799: Oct 25 22:59:15.905:  DHCPD: reason flags: RELEASE
028800: Oct 25 22:59:15.905:   DHCPD: htype 1 chaddr 0026.99f0.21e5
028801: Oct 25 22:59:15.905:   DHCPD: lease time remaining (secs) = 86179
028802: Oct 25 22:59:15.905: DHCPD: returned 10.1.1.13 to address pool phone.
028803: Oct 25 22:59:15.905: DHCPD: client's VPN is .
028804: Oct 25 22:59:15.905: DHCPD: DHCPRELEASE message received from client 0100.26cb.3dbc.7b (10.1.1.15).
028805: Oct 25 22:59:15.905: DHCPD: Sending notification of TERMINATION:
028806: Oct 25 22:59:15.905:  DHCPD: address 10.1.1.15 mask 255.255.255.0
028807: Oct 25 22:59:15.905:  DHCPD: reason flags: RELEASE
028808: Oct 25 22:59:15.905:   DHCPD: htype 1 chaddr 0026.cb3d.bc7b
028809: Oct 25 22:59:15.905:   DHCPD: lease time remaining (secs) = 86224
028810: Oct 25 22:59:15.905: DHCPD: returned 10.1.1.15 to address pool phone.
028811: Oct 25 22:59:15.905: DHCPD: client's VPN is .
028812: Oct 25 22:59:15.905: DHCPD: DHCPRELEASE message received from client 0100.26cb.bd9e.31 (10.1.1.16).
028813: Oct 25 22:59:15.905: DHCPD: Sending notification of TERMINATION:
028814: Oct 25 22:59:15.905:  DHCPD: address 10.1.1.16 mask 255.255.255.0
028815: Oct 25 22:59:15.905:  DHCPD: reason flags: RELEASE
028816: Oct 25 22:59:15.905:   DHCPD: htype 1 chaddr 0026.cbbd.9e31
028817: Oct 25 22:59:15.905:   DHCPD: lease time remaining (secs) = 86198
028818: Oct 25 22:59:15.905: DHCPD: returned 10.1.1.16 to address pool phone.
028819: Oct 25 22:59:15.909: DHCPD: client's VPN is .
028820: Oct 25 22:59:15.909: DHCPD: DHCPRELEASE message received from client 0100.26cb.bda3.6b (10.1.1.12).
028821: Oct 25 22:59:15.909: DHCPD: Sending notification of TERMINATION:
028822: Oct 25 22:59:15.909:  DHCPD: address 10.1.1.12 mask 255.255.255.0
028823: Oct 25 22:59:15.909:  DHCPD: reason flags: RELEASE
028824: Oct 25 22:59:15.909:   DHCPD: htype 1 chaddr 0026.cbbd.a36b
028825: Oct 25 22:59:15.909:   DHCPD: lease time remaining (secs) = 86203
028826: Oct 25 22:59:15.909: DHCPD: returned 10.1.1.12 to address pool phone.
028827: Oct 25 22:59:15.949: DHCPD: client's VPN is .
028828: Oct 25 22:59:15.949: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbd.8e.
028829: Oct 25 22:59:15.949: DHCPD: client has moved to a new subnet.
028830: Oct 25 22:59:15.949: DHCPD: Sending notification of ASSIGNMENT FAILURE:
028831: Oct 25 22:59:15.949:   DHCPD: htype 1 chaddr 0026.cb3d.bd8e
028832: Oct 25 22:59:15.949:   DHCPD: remote id 020a0000c0a84001f1000000
028833: Oct 25 22:59:15.949:   DHCPD: circuit id 00000000
028834: Oct 25 22:59:15.949: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
028835: Oct 25 22:59:15.949:  DHCPD: due to: Reason with no text explanation
028836: Oct 25 22:59:15.949:   DHCPD: htype 1 chaddr 0026.cb3d.bd8e
028837: Oct 25 22:59:15.949:   DHCPD: remote id 020a0000c0a84001f1000000
028838: Oct 25 22:59:15.949:   DHCPD: circuit id 00000000
028839: Oct 25 22:59:15.949: DHCPD: Sending DHCPNAK to client 0100.26cb.3dbd.8e.
028840: Oct 25 22:59:15.949: DHCPD: broadcasting BOOTREPLY to client 0026.cb3d.bd8e.
028841: Oct 25 22:59:15.949: DHCPD: client's VPN is .
028842: Oct 25 22:59:15.949: DHCPD: DHCPREQUEST received from client 0100.26cb.bd9e.31.
028843: Oct 25 22:59:15.949: DHCPD: client has moved to a new subnet.
028844: Oct 25 22:59:15.949: DHCPD: Sending notification of ASSIGNMENT FAILURE:
028845: Oct 25 22:59:15.949:   DHCPD: htype 1 chaddr 0026.cbbd.9e31
028846: Oct 25 22:59:15.949:   DHCPD: remote id 020a0000c0a84001f1000000
028847: Oct 25 22:59:15.949:   DHCPD: circuit id 00000000
028848: Oct 25 22:59:15.949: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
028849: Oct 25 22:59:15.949:  DHCPD: due to: Reason with no text explanation
028850: Oct 25 22:59:15.949:   DHCPD: htype 1 chaddr 0026.cbbd.9e31
028851: Oct 25 22:59:15.949:   DHCPD: remote id 020a0000c0a84001f1000000
028852: Oct 25 22:59:15.949:   DHCPD: circuit id 00000000
028853: Oct 25 22:59:15.949: DHCPD: Sending DHCPNAK to client 0100.26cb.bd9e.31.
028854: Oct 25 22:59:15.949: DHCPD: broadcasting BOOTREPLY to client 0026.cbbd.9e31.
028855: Oct 25 22:59:15.953: DHCPD: client's VPN is .
028856: Oct 25 22:59:15.953: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbd.29.
028857: Oct 25 22:59:15.953: DHCPD: client has moved to a new subnet.
028858: Oct 25 22:59:15.953: DHCPD: Sending notification of ASSIGNMENT FAILURE:
028859: Oct 25 22:59:15.953:   DHCPD: htype 1 chaddr 0026.cb3d.bd29
028860: Oct 25 22:59:15.953:   DHCPD: remote id 020a0000c0a84001f1000000
028861: Oct 25 22:59:15.953:   DHCPD: circuit id 00000000
028862: Oct 25 22:59:15.953: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
028863: Oct 25 22:59:15.953:  DHCPD: due to: Reason with no text explanation
028864: Oct 25 22:59:15.953:   DHCPD: htype 1 chaddr 0026.cb3d.bd29
028865: Oct 25 22:59:15.953:   DHCPD: remote id 020a0000c0a84001f1000000
028866: Oct 25 22:59:15.953:   DHCPD: circuit id 00000000
028867: Oct 25 22:59:15.953: DHCPD: Sending DHCPNAK to client 0100.26cb.3dbd.29.
028868: Oct 25 22:59:15.953: DHCPD: broadcasting BOOTREPLY to client 0026.cb3d.bd29.
028869: Oct 25 22:59:15.953: DHCPD: client's VPN is .
028870: Oct 25 22:59:15.953: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbe.11.
028871: Oct 25 22:59:15.953: DHCPD: client has moved to a new subnet.
028872: Oct 25 22:59:15.953: DHCPD: Sending notification of ASSIGNMENT FAILURE:
028873: Oct 25 22:59:15.957:   DHCPD: htype 1 chaddr 0026.cb3d.be11
028874: Oct 25 22:59:15.957:   DHCPD: remote id 020a0000c0a84001f1000000
028875: Oct 25 22:59:15.957:   DHCPD: circuit id 00000000
028876: Oct 25 22:59:15.957: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
028877: Oct 25 22:59:15.957:  DHCPD: due to: Reason with no text explanation
028878: Oct 25 22:59:15.957:   DHCPD: htype 1 chaddr 0026.cb3d.be11
028879: Oct 25 22:59:15.957:   DHCPD: remote id 020a0000c0a84001f1000000
028880: Oct 25 22:59:15.957:   DHCPD: circuit id 00000000
028881: Oct 25 22:59:15.957: DHCPD: Sending DHCPNAK to client 0100.26cb.3dbe.11.
028882: Oct 25 22:59:15.957: DHCPD: broadcasting BOOTREPLY to client 0026.cb3d.be11.
028883: Oct 25 22:59:15.957: DHCPD: client's VPN is .
028884: Oct 25 22:59:15.957: DHCPD: DHCPREQUEST received from client 0100.2699.f021.e5.
028885: Oct 25 22:59:15.957: DHCPD: client has moved to a new subnet.
028886: Oct 25 22:59:15.957: DHCPD: Sending notification of ASSIGNMENT FAILURE:
028887: Oct 25 22:59:15.957:   DHCPD: htype 1 chaddr 0026.99f0.21e5
028888: Oct 25 22:59:15.957:   DHCPD: remote id 020a0000c0a84001f1000000
028889: Oct 25 22:59:15.957:   DHCPD: circuit id 00000000
028890: Oct 25 22:59:15.957: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
028891: Oct 25 22:59:15.957:  DHCPD: due to: Reason with no text explanation
028892: Oct 25 22:59:15.957:   DHCPD: htype 1 chaddr 0026.99f0.21e5
028893: Oct 25 22:59:15.957:   DHCPD: remote id 020a0000c0a84001f1000000
028894: Oct 25 22:59:15.957:   DHCPD: circuit id 00000000
028895: Oct 25 22:59:15.957: DHCPD: Sending DHCPNAK to client 0100.2699.f021.e5.
028896: Oct 25 22:59:15.957: DHCPD: broadcasting BOOTREPLY to client 0026.99f0.21e5.
028897: Oct 25 22:59:15.957: DHCPD: client's VPN is .
028898: Oct 25 22:59:15.957: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbc.7b.
028899: Oct 25 22:59:15.957: DHCPD: client has moved to a new subnet.
028900: Oct 25 22:59:15.957: DHCPD: Sending notification of ASSIGNMENT FAILURE:
028901: Oct 25 22:59:15.957:   DHCPD: htype 1 chaddr 0026.cb3d.bc7b
028902: Oct 25 22:59:15.961:   DHCPD: remote id 020a0000c0a84001f1000000
028903: Oct 25 22:59:15.961:   DHCPD: circuit id 00000000
028904: Oct 25 22:59:15.961: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
028905: Oct 25 22:59:15.961:  DHCPD: due to: Reason with no text explanation
028906: Oct 25 22:59:15.961:   DHCPD: htype 1 chaddr 0026.cb3d.bc7b
028907: Oct 25 22:59:15.961:   DHCPD: remote id 020a0000c0a84001f1000000
028908: Oct 25 22:59:15.961:   DHCPD: circuit id 00000000
028909: Oct 25 22:59:15.961: DHCPD: Sending DHCPNAK to client 0100.26cb.3dbc.7b.
028910: Oct 25 22:59:15.961: DHCPD: broadcasting BOOTREPLY to client 0026.cb3d.bc7b.
028911: Oct 25 22:59:15.961: DHCPD: client's VPN is .
028912: Oct 25 22:59:15.961: DHCPD: DHCPREQUEST received from client 0100.26cb.bda3.6b.
028913: Oct 25 22:59:15.961: DHCPD: client has moved to a new subnet.
028914: Oct 25 22:59:15.961: DHCPD: Sending notification of ASSIGNMENT FAILURE:
028915: Oct 25 22:59:15.961:   DHCPD: htype 1 chaddr 0026.cbbd.a36b
028916: Oct 25 22:59:15.961:   DHCPD: remote id 020a0000c0a84001f1000000
028917: Oct 25 22:59:15.961:   DHCPD: circuit id 00000000
028918: Oct 25 22:59:15.961: DHCPD: Sending notification of ASSIGNMENT_FAILURE:
028919: Oct 25 22:59:15.961:  DHCPD: due to: Reason with no text explanation
028920: Oct 25 22:59:15.961:   DHCPD: htype 1 chaddr 0026.cbbd.a36b
028921: Oct 25 22:59:15.961:   DHCPD: remote id 020a0000c0a84001f1000000
028922: Oct 25 22:59:15.961:   DHCPD: circuit id 00000000
028923: Oct 25 22:59:15.961: DHCPD: Sending DHCPNAK to client 0100.26cb.bda3.6b.
028924: Oct 25 22:59:15.961: DHCPD: broadcasting BOOTREPLY to client 0026.cbbd.a36b.
028925: Oct 25 22:59:16.969: DHCPD: client's VPN is .
028926: Oct 25 22:59:16.969: DHCPD: Sending notification of DISCOVER:
028927: Oct 25 22:59:16.969:   DHCPD: htype 1 chaddr 0026.cb3d.bd8e
028928: Oct 25 22:59:16.969:   DHCPD: remote id 020a0000c0a84001f1000000
028929: Oct 25 22:59:16.969:   DHCPD: circuit id 00000000
028930: Oct 25 22:59:16.969: DHCPD: DHCPDISCOVER received from client 0100.26cb.3dbd.8e on interface BVI1.
028931: Oct 25 22:59:16.969: DHCPD: Seeing if there is an internally specified pool class:
028932: Oct 25 22:59:16.969:   DHCPD: htype 1 chaddr 0026.cb3d.bd8e
028933: Oct 25 22:59:16.969:   DHCPD: remote id 020a0000c0a84001f1000000
028934: Oct 25 22:59:16.969:   DHCPD: circuit id 00000000
028935: Oct 25 22:59:16.969: DHCPD: there is no address pool for 192.168.64.1.
028936: Oct 25 22:59:16.969: DHCPD: there is no address pool for 192.168.64.5.
028937: Oct 25 22:59:16.973: DHCPD: client's VPN is .
028938: Oct 25 22:59:16.973: DHCPD: Sending notification of DISCOVER:
028939: Oct 25 22:59:16.973:   DHCPD: htype 1 chaddr 0026.cbbd.9e31
028940: Oct 25 22:59:16.973:   DHCPD: remote id 020a0000c0a84001f1000000
028941: Oct 25 22:59:16.973:   DHCPD: circuit id 00000000
028942: Oct 25 22:59:16.973: DHCPD: DHCPDISCOVER received from client 0100.26cb.bd9e.31 on interface BVI1.
028943: Oct 25 22:59:16.973: DHCPD: Seeing if there is an internally specified pool class:
028944: Oct 25 22:59:16.973:   DHCPD: htype 1 chaddr 0026.cbbd.9e31
028945: Oct 25 22:59:16.973:   DHCPD: remote id 020a0000c0a84001f1000000
028946: Oct 25 22:59:16.973:   DHCPD: circuit id 00000000
028947: Oct 25 22:59:16.973: DHCPD: there is no address pool for 192.168.64.1.
028948: Oct 25 22:59:16.973: DHCPD: there is no address pool for 192.168.64.5.
028949: Oct 25 22:59:16.977: DHCPD: client's VPN is .
028950: Oct 25 22:59:16.977: DHCPD: Sending notification of DISCOVER:
028951: Oct 25 22:59:16.977:   DHCPD: htype 1 chaddr 0026.cb3d.be11
028952: Oct 25 22:59:16.977:   DHCPD: remote id 020a0000c0a84001f1000000
028953: Oct 25 22:59:16.977:   DHCPD: circuit id 00000000
028954: Oct 25 22:59:16.977: DHCPD: DHCPDISCOVER received from client 0100.26cb.3dbe.11 on interface BVI1.
028955: Oct 25 22:59:16.977: DHCPD: Seeing if there is an internally specified pool class:
028956: Oct 25 22:59:16.977:   DHCPD: htype 1 chaddr 0026.cb3d.be11
028957: Oct 25 22:59:16.977:   DHCPD: remote id 020a0000c0a84001f1000000
028958: Oct 25 22:59:16.977:   DHCPD: circuit id 00000000
028959: Oct 25 22:59:16.977: DHCPD: there is no address pool for 192.168.64.1.
028960: Oct 25 22:59:16.977: DHCPD: there is no address pool for 192.168.64.5.
028961: Oct 25 22:59:16.985: DHCPD: client's VPN is .
028962: Oct 25 22:59:16.985: DHCPD: Sending notification of DISCOVER:
028963: Oct 25 22:59:16.985:   DHCPD: htype 1 chaddr 0026.cb3d.bc7b
028964: Oct 25 22:59:16.985:   DHCPD: remote id 020a0000c0a84001f1000000
028965: Oct 25 22:59:16.985:   DHCPD: circuit id 00000000
028966: Oct 25 22:59:16.985: DHCPD: DHCPDISCOVER received from client 0100.26cb.3dbc.7b on interface BVI1.
028967: Oct 25 22:59:16.985: DHCPD: Seeing if there is an internally specified pool class:
028968: Oct 25 22:59:16.985:   DHCPD: htype 1 chaddr 0026.cb3d.bc7b
028969: Oct 25 22:59:16.985:   DHCPD: remote id 020a0000c0a84001f1000000
028970: Oct 25 22:59:16.985:   DHCPD: circuit id 00000000
028971: Oct 25 22:59:16.985: DHCPD: there is no address pool for 192.168.64.1.
028972: Oct 25 22:59:16.985: DHCPD: there is no address pool for 192.168.64.5.
028973: Oct 25 22:59:16.985: DHCPD: client's VPN is .
028974: Oct 25 22:59:16.985: DHCPD: Sending notification of DISCOVER:
028975: Oct 25 22:59:16.985:   DHCPD: htype 1 chaddr 0026.cbbd.a36b
028976: Oct 25 22:59:16.985:   DHCPD: remote id 020a0000c0a84001f1000000
028977: Oct 25 22:59:16.985:   DHCPD: circuit id 00000000
028978: Oct 25 22:59:16.985: DHCPD: DHCPDISCOVER received from client 0100.26cb.bda3.6b on interface BVI1.
028979: Oct 25 22:59:16.985: DHCPD: Seeing if there is an internally specified pool class:
028980: Oct 25 22:59:16.985:   DHCPD: htype 1 chaddr 0026.cbbd.a36b
028981: Oct 25 22:59:16.985:   DHCPD: remote id 020a0000c0a84001f1000000
028982: Oct 25 22:59:16.985:   DHCPD: circuit id 00000000
028983: Oct 25 22:59:16.985: DHCPD: there is no address pool for 192.168.64.1.
028984: Oct 25 22:59:16.985: DHCPD: there is no address pool for 192.168.64.5.
028985: Oct 25 22:59:16.989: DHCPD: client's VPN is .
028986: Oct 25 22:59:16.989: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbe.11.
028987: Oct 25 22:59:16.989: DHCPD: no subnet configured for 192.168.64.100.
028988: Oct 25 22:59:16.989: DHCPD: Finding a relay for client 0100.26cb.3dbe.11 on interface BVI1.
028989: Oct 25 22:59:16.989: DHCPD: Seeing if there is an internally specified pool class:
028990: Oct 25 22:59:16.989:   DHCPD: htype 1 chaddr 0026.cb3d.be11
028991: Oct 25 22:59:16.989:   DHCPD: remote id 020a0000c0a84001f1000000
028992: Oct 25 22:59:16.989:   DHCPD: circuit id 00000000
028993: Oct 25 22:59:16.989: DHCPD: there is no pool for 192.168.64.1.
028994: Oct 25 22:59:16.989: DHCPD: there is no pool for 192.168.64.5.
028995: Oct 25 22:59:16.993: DHCPD: client's VPN is .
028996: Oct 25 22:59:16.993: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbc.7b.
028997: Oct 25 22:59:16.993: DHCPD: no subnet configured for 192.168.64.117.
028998: Oct 25 22:59:16.993: DHCPD: Finding a relay for client 0100.26cb.3dbc.7b on interface BVI1.
028999: Oct 25 22:59:16.993: DHCPD: Seeing if there is an internally specified pool class:
029000: Oct 25 22:59:16.993:   DHCPD: htype 1 chaddr 0026.cb3d.bc7b
029001: Oct 25 22:59:16.993:   DHCPD: remote id 020a0000c0a84001f1000000
029002: Oct 25 22:59:16.993:   DHCPD: circuit id 00000000
029003: Oct 25 22:59:16.993: DHCPD: there is no pool for 192.168.64.1.
029004: Oct 25 22:59:16.993: DHCPD: there is no pool for 192.168.64.5.
029005: Oct 25 22:59:16.997: DHCPD: client's VPN is .
029006: Oct 25 22:59:16.997: DHCPD: DHCPREQUEST received from client 0100.26cb.bda3.6b.
029007: Oct 25 22:59:16.997: DHCPD: no subnet configured for 192.168.64.114.
029008: Oct 25 22:59:16.997: DHCPD: Finding a relay for client 0100.26cb.bda3.6b on interface BVI1.
029009: Oct 25 22:59:16.997: DHCPD: Seeing if there is an internally specified pool class:
029010: Oct 25 22:59:16.997:   DHCPD: htype 1 chaddr 0026.cbbd.a36b
029011: Oct 25 22:59:16.997:   DHCPD: remote id 020a0000c0a84001f1000000
029012: Oct 25 22:59:16.997:   DHCPD: circuit id 00000000
029013: Oct 25 22:59:16.997: DHCPD: there is no pool for 192.168.64.1.
029014: Oct 25 22:59:16.997: DHCPD: there is no pool for 192.168.64.5.
029015: Oct 25 22:59:17.013: DHCPD: client's VPN is .
029016: Oct 25 22:59:17.017: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbd.8e.
029017: Oct 25 22:59:17.017: DHCPD: no subnet configured for 192.168.64.108.
029018: Oct 25 22:59:17.017: DHCPD: Finding a relay for client 0100.26cb.3dbd.8e on interface BVI1.
029019: Oct 25 22:59:17.017: DHCPD: Seeing if there is an internally specified pool class:
029020: Oct 25 22:59:17.017:   DHCPD: htype 1 chaddr 0026.cb3d.bd8e
029021: Oct 25 22:59:17.017:   DHCPD: remote id 020a0000c0a84001f1000000
029022: Oct 25 22:59:17.017:   DHCPD: circuit id 00000000
029023: Oct 25 22:59:17.017: DHCPD: there is no pool for 192.168.64.1.
029024: Oct 25 22:59:17.017: DHCPD: there is no pool for 192.168.64.5.
029025: Oct 25 22:59:17.017: DHCPD: client's VPN is .
029026: Oct 25 22:59:17.017: DHCPD: Sending notification of DISCOVER:
029027: Oct 25 22:59:17.017:   DHCPD: htype 1 chaddr 0026.cb3d.bd29
029028: Oct 25 22:59:17.017:   DHCPD: remote id 020a0000c0a84001f1000000
029029: Oct 25 22:59:17.017:   DHCPD: circuit id 00000000
029030: Oct 25 22:59:17.017: DHCPD: DHCPDISCOVER received from client 0100.26cb.3dbd.29 on interface BVI1.
029031: Oct 25 22:59:17.017: DHCPD: Seeing if there is an internally specified pool class:
029032: Oct 25 22:59:17.017:   DHCPD: htype 1 chaddr 0026.cb3d.bd29
029033: Oct 25 22:59:17.017:   DHCPD: remote id 020a0000c0a84001f1000000
029034: Oct 25 22:59:17.017:   DHCPD: circuit id 00000000
029035: Oct 25 22:59:17.017: DHCPD: there is no address pool for 192.168.64.1.
029036: Oct 25 22:59:17.017: DHCPD: there is no address pool for 192.168.64.5.
029037: Oct 25 22:59:17.021: DHCPD: client's VPN is .
029038: Oct 25 22:59:17.021: DHCPD: Sending notification of DISCOVER:
029039: Oct 25 22:59:17.021:   DHCPD: htype 1 chaddr 0026.99f0.21e5
029040: Oct 25 22:59:17.021:   DHCPD: remote id 020a0000c0a84001f1000000
029041: Oct 25 22:59:17.021:   DHCPD: circuit id 00000000
029042: Oct 25 22:59:17.021: DHCPD: DHCPDISCOVER received from client 0100.2699.f021.e5 on interface BVI1.
029043: Oct 25 22:59:17.021: DHCPD: Seeing if there is an internally specified pool class:
029044: Oct 25 22:59:17.021:   DHCPD: htype 1 chaddr 0026.99f0.21e5
029045: Oct 25 22:59:17.021:   DHCPD: remote id 020a0000c0a84001f1000000
029046: Oct 25 22:59:17.021:   DHCPD: circuit id 00000000
029047: Oct 25 22:59:17.021: DHCPD: there is no address pool for 192.168.64.1.
029048: Oct 25 22:59:17.021: DHCPD: there is no address pool for 192.168.64.5.
029049: Oct 25 22:59:17.025: DHCPD: client's VPN is .
029050: Oct 25 22:59:17.025: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbd.29.
029051: Oct 25 22:59:17.025: DHCPD: no subnet configured for 192.168.64.115.
029052: Oct 25 22:59:17.025: DHCPD: Finding a relay for client 0100.26cb.3dbd.29 on interface BVI1.
029053: Oct 25 22:59:17.025: DHCPD: Seeing if there is an internally specified pool class:
029054: Oct 25 22:59:17.025:   DHCPD: htype 1 chaddr 0026.cb3d.bd29
029055: Oct 25 22:59:17.025:   DHCPD: remote id 020a0000c0a84001f1000000
029056: Oct 25 22:59:17.025:   DHCPD: circuit id 00000000
029057: Oct 25 22:59:17.025: DHCPD: there is no pool for 192.168.64.1.
029058: Oct 25 22:59:17.025: DHCPD: there is no pool for 192.168.64.5.
029059: Oct 25 22:59:17.029: DHCPD: client's VPN is .
029060: Oct 25 22:59:17.029: DHCPD: DHCPREQUEST received from client 0100.26cb.bd9e.31.
029061: Oct 25 22:59:17.029: DHCPD: no subnet configured for 192.168.64.116.
029062: Oct 25 22:59:17.029: DHCPD: Finding a relay for client 0100.26cb.bd9e.31 on interface BVI1.
029063: Oct 25 22:59:17.029: DHCPD: Seeing if there is an internally specified pool class:
029064: Oct 25 22:59:17.029:   DHCPD: htype 1 chaddr 0026.cbbd.9e31
029065: Oct 25 22:59:17.029:   DHCPD: remote id 020a0000c0a84001f1000000
029066: Oct 25 22:59:17.029:   DHCPD: circuit id 00000000
029067: Oct 25 22:59:17.029: DHCPD: there is no pool for 192.168.64.1.
029068: Oct 25 22:59:17.029: DHCPD: there is no pool for 192.168.64.5.
029069: Oct 25 22:59:17.029: DHCPD: client's VPN is .
029070: Oct 25 22:59:17.029: DHCPD: DHCPREQUEST received from client 0100.2699.f021.e5.
029071: Oct 25 22:59:17.029: DHCPD: no subnet configured for 192.168.64.118.
029072: Oct 25 22:59:17.029: DHCPD: Finding a relay for client 0100.2699.f021.e5 on interface BVI1.
029073: Oct 25 22:59:17.029: DHCPD: Seeing if there is an internally specified pool class:
029074: Oct 25 22:59:17.029:   DHCPD: htype 1 chaddr 0026.99f0.21e5
029075: Oct 25 22:59:17.033:   DHCPD: remote id 020a0000c0a84001f1000000
029076: Oct 25 22:59:17.033:   DHCPD: circuit id 00000000
029077: Oct 25 22:59:17.033: DHCPD: there is no pool for 192.168.64.1.
029078: Oct 25 22:59:17.033: DHCPD: there is no pool for 192.168.64.5.
029079: Oct 25 22:59:17.033: DHCPD: client's VPN is .
029080: Oct 25 22:59:17.033: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbd.8e.
029081: Oct 25 22:59:17.033: DHCPD: no subnet configured for 192.168.64.108.
029082: Oct 25 22:59:17.033: DHCPD: Finding a relay for client 0100.26cb.3dbd.8e on interface BVI1.
029083: Oct 25 22:59:17.033: DHCPD: Seeing if there is an internally specified pool class:
029084: Oct 25 22:59:17.033:   DHCPD: htype 1 chaddr 0026.cb3d.bd8e
029085: Oct 25 22:59:17.033:   DHCPD: remote id 020a0000c0a84001f1000000
029086: Oct 25 22:59:17.033:   DHCPD: circuit id 00000000
029087: Oct 25 22:59:17.033: DHCPD: there is no pool for 192.168.64.1.
029088: Oct 25 22:59:17.033: DHCPD: there is no pool for 192.168.64.5.
029089: Oct 25 22:59:17.045: DHCPD: client's VPN is .
029090: Oct 25 22:59:17.045: DHCPD: DHCPREQUEST received from client 0100.26cb.3dbd.29.
029091: Oct 25 22:59:17.045: DHCPD: no subnet configured for 192.168.64.115.
029092: Oct 25 22:59:17.045: DHCPD: Finding a relay for client 0100.26cb.3dbd.29 on interface BVI1.
029093: Oct 25 22:59:17.045: DHCPD: Seeing if there is an internally specified pool class:
029094: Oct 25 22:59:17.045:   DHCPD: htype 1 chaddr 0026.cb3d.bd29
029095: Oct 25 22:59:17.045:   DHCPD: remote id 020a0000c0a84001f1000000
029096: Oct 25 22:59:17.045:   DHCPD: circuit id 00000000
029097: Oct 25 22:59:17.045: DHCPD: there is no pool for 192.168.64.1.
029098: Oct 25 22:59:17.045: DHCPD: there is no pool for 192.168.64.5.
029099: Oct 25 22:59:17.053: DHCPD: client's VPN is .
029100: Oct 25 22:59:17.053: DHCPD: DHCPREQUEST received from client 0100.26cb.bd9e.31.
029101: Oct 25 22:59:17.053: DHCPD: no subnet configured for 192.168.64.116.
029102: Oct 25 22:59:17.053: DHCPD: Finding a relay for client 0100.26cb.bd9e.31 on interface BVI1.
029103: Oct 25 22:59:17.053: DHCPD: Seeing if there is an internally specified pool class:
029104: Oct 25 22:59:17.053:   DHCPD: htype 1 chaddr 0026.cbbd.9e31
029105: Oct 25 22:59:17.053:   DHCPD: remote id 020a0000c0a84001f1000000
029106: Oct 25 22:59:17.053:   DHCPD: circuit id 00000000
029107: Oct 25 22:59:17.053: DHCPD: there is no pool for 192.168.64.1.
029108: Oct 25 22:59:17.053: DHCPD: there is no pool for 192.168.64.5.
029109: Oct 25 22:59:17.053: DHCPD: client's VPN is .
029110: Oct 25 22:59:17.053: DHCPD: DHCPREQUEST received from client 0100.2699.f021.e5.
029111: Oct 25 22:59:17.053: DHCPD: no subnet configured for 192.168.64.118.
029112: Oct 25 22:59:17.053: DHCPD: Finding a relay for client 0100.2699.f021.e5 on interface BVI1.
029113: Oct 25 22:59:17.053: DHCPD: Seeing if there is an internally specified pool class:
029114: Oct 25 22:59:17.053:   DHCPD: htype 1 chaddr 0026.99f0.21e5
029115: Oct 25 22:59:17.053:   DHCPD: remote id 020a0000c0a84001f1000000
029116: Oct 25 22:59:17.053:   DHCPD: circuit id 00000000
029117: Oct 25 22:59:17.053: DHCPD: there is no pool for 192.168.64.1.
029118: Oct 25 22:59:17.053: DHCPD: there is no pool for 192.168.64.5.
029119: Oct 25 22:59:18.089: %IPPHONE-6-REG_ALARM: 14: Name=SEP002699F021E5 Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029120: Oct 25 22:59:18.129: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CB3DBE11 Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029121: Oct 25 22:59:18.133: %IPPHONE-6-REG_ALARM: 14: Name=SEP002699F021E5 Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029122: Oct 25 22:59:18.209: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CBBDA36B Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029123: Oct 25 22:59:18.209: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-5:SEP002699F021E5 IP:10.1.1.13 Socket:1 DeviceType:Phone has unregistered abnormally.
029124: Oct 25 22:59:18.209: %IPPHONE-6-REGISTER: ephone-5:SEP002699F021E5 IP:192.168.64.118 Socket:8 DeviceType:Phone has registered.
029125: Oct 25 22:59:18.213: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CB3DBE11 Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029126: Oct 25 22:59:18.213: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-1:SEP0026CB3DBE11 IP:10.1.1.10 Socket:7 DeviceType:Phone has unregistered abnormally.
029127: Oct 25 22:59:18.213: %IPPHONE-6-REGISTER: ephone-1:SEP0026CB3DBE11 IP:192.168.64.100 Socket:10 DeviceType:Phone has registered.
029128: Oct 25 22:59:18.213: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CBBDA36B Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029129: Oct 25 22:59:18.221: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CB3DBD29 Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029130: Oct 25 22:59:18.221: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CB3DBD29 Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029131: Oct 25 22:59:18.225: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CB3DBC7B Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029132: Oct 25 22:59:18.241: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-9:SEP0026CBBDA36B IP:10.1.1.12 Socket:5 DeviceType:Phone has unregistered abnormally.
029133: Oct 25 22:59:18.241: %IPPHONE-6-REGISTER: ephone-9:SEP0026CBBDA36B IP:192.168.64.114 Socket:11 DeviceType:Phone has registered.
029134: Oct 25 22:59:18.245: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CB3DBD8E Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029135: Oct 25 22:59:18.249: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-6:SEP0026CB3DBD29 IP:10.1.1.14 Socket:3 DeviceType:Phone has unregistered abnormally.
029136: Oct 25 22:59:18.249: %IPPHONE-6-REGISTER: ephone-6:SEP0026CB3DBD29 IP:192.168.64.115 Socket:12 DeviceType:Phone has registered.
029137: Oct 25 22:59:18.249: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CBBD9E31 Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029138: Oct 25 22:59:18.261: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CB3DBD8E Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029139: Oct 25 22:59:18.269: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CBBD9E31 Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029140: Oct 25 22:59:18.273: %IPPHONE-6-REG_ALARM: 14: Name=SEP0026CB3DBC7B Load= SCCP75.8-4-2S Last=UCM-closed-TCP
029141: Oct 25 22:59:18.289: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-10:SEP0026CB3DBD8E IP:10.1.1.11 Socket:6 DeviceType:Phone has unregistered abnormally.
029142: Oct 25 22:59:18.293: %IPPHONE-6-REGISTER: ephone-10:SEP0026CB3DBD8E IP:192.168.64.108 Socket:7 DeviceType:Phone has registered.
029143: Oct 25 22:59:18.309: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-8:SEP0026CBBD9E31 IP:10.1.1.16 Socket:4 DeviceType:Phone has unregistered abnormally.
029144: Oct 25 22:59:18.309: %IPPHONE-6-REGISTER: ephone-8:SEP0026CBBD9E31 IP:192.168.64.116 Socket:1 DeviceType:Phone has registered.
029145: Oct 25 22:59:18.313: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-7:SEP0026CB3DBC7B IP:10.1.1.15 Socket:2 DeviceType:Phone has unregistered abnormally.
029146: Oct 25 22:59:18.317: %IPPHONE-6-REGISTER: ephone-7:SEP0026CB3DBC7B IP:192.168.64.117 Socket:13 DeviceType:Phone has registered.