[cisco-voip] Phone in CCME 7.1 buttons do not work....
Jonathan Charles
jonvoip at gmail.com
Mon Jan 25 13:06:42 EST 2010
We do have 20 phones with the same hardware and config... 18 are fine... all
are 7962s with 7915s... I have swapped phone and sidecar and the problem
always follows the configured device...
Jonathan
On Mon, Jan 25, 2010 at 8:54 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
> Any of the features in 7.1.3 that require sccp version 17 won't work
> correctly but otherwise it will be ok.
>
> You just want to do one phone anyway just to confirm this is the issue.
>
> -Ryan
>
> On Jan 25, 2010, at 9:33 AM, Jonathan Charles wrote:
>
> This is CCME as SRST, with CUCM 7.1.3-31900... won't that break the phone
> in normal mode?
>
> On Mon, Jan 25, 2010 at 8:27 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
>
>> Try downgrading to 8.4 phone firmware and see if that helps. Your phone
>> is on 8.5 which uses sccp 17, and only supported in the latest IOS (15).
>> Even then there are still bugs related to sccp 17 phones registering.
>>
>> -Ryan
>>
>> On Jan 24, 2010, at 9:06 PM, Jonathan Charles wrote:
>>
>> Here is a debug ephone:
>>
>>
>> HTANYC505a#
>> HTANYC505a#
>> HTANYC505a#htsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPhtsp->cdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at SkinnyIsPeerNonSCCP
>> HTANYC505a#peer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at
>> SkinnyIsPeerNonSCCPpeer_vdb is NULL for DN 20, chan 1 at SkinnyIsPeerNonSCCP
>> HTANYC505a#
>> *Jan 25 01:52:04.975: %IPPHONE-6-REG_ALARM: 14: Name=SEP0024C40BC4A7 Load=
>> SCCP42.8-5-3S Last=UCM-closed-TCP
>> *Jan 25 01:52:05.039: %IPPHONE-6-REGISTER: ephone-21:SEP0024C40BC4A7
>> IP:10.5.2.61 Socket:12 DeviceType:Phone has registered.
>> HTANYC505a#
>> *Jan 25 01:52:12.751: socket 12 fatal error 11! can't write with size
>> 1087465692, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 0
>> *Jan 25 01:52:12.751: socket 12 fatal error 11! can't write with size
>> 1087465692, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 0
>> *Jan 25 01:52:12.755: socket 12 fatal error 11! can't write with size
>> 1087465692, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 0
>> *Jan 25 01:52:12.755: socket 12 fatal error 11! can't write with size
>> 1087465692, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 0
>> *Jan 25 01:52:12.755: socket 12 fatal error 11! can't write with size
>> 1087465692, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 0
>> *Jan 25 01:52:12.755: socket 12 fatal error 11! can't write with size
>> 1087465692, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 0
>> *Jan 25 01:52:12.755: socket 12 fatal error 11! can't write with size
>> 1087465692, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 0
>> *Jan 25 01:52:12.755: socket 12 fatal error 11! can't write with size
>> 1087474220, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 0
>> *Jan 25 01:52:12.755: socket 12 fatal error 11! can't write with size
>> 1087474220, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 0
>> HTANYC505a#
>> *Jan 25 01:52:12.755: socket 12 fatal error 11! can't write with size 0,
>> fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 0
>> HTANYC505a#
>> *Jan 25 01:52:15.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 4
>> *Jan 25 01:52:15.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 4
>> *Jan 25 01:52:15.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 4
>> *Jan 25 01:52:15.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 4
>> HTANYC505a#
>> *Jan 25 01:52:27.103: %IPPHONE-6-REG_ALARM: 20: Name=SEP0023EBC7EE7C Load=
>> SCCP42.8-5-3S Last=Phone-Keypad
>> *Jan 25 01:52:27.163: %IPPHONE-6-REGISTER: ephone-24:SEP0023EBC7EE7C
>> IP:10.5.2.39 Socket:32 DeviceType:Phone has registered.
>> HTANYC505a#
>> *Jan 25 01:52:45.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 34
>> *Jan 25 01:52:45.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 34
>> *Jan 25 01:52:45.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 34
>> *Jan 25 01:52:45.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 34
>> HTANYC505a#
>> *Jan 25 01:52:47.235: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> *Jan 25 01:52:47.235: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> *Jan 25 01:52:47.235: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> *Jan 25 01:52:47.235: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> *Jan 25 01:52:47.239: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> *Jan 25 01:52:47.239: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> *Jan 25 01:52:47.239: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> *Jan 25 01:52:47.239: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> *Jan 25 01:52:47.239: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> HTANYC505a#
>> *Jan 25 01:52:47.239: socket 32 fatal error 11! can't write with size 0,
>> fd 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 0
>> HTANYC505a#
>> *Jan 25 01:53:12.511: socket 12 fatal error 0! can't write with size
>> 1087474228, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 61
>> HTANYC505a#
>> *Jan 25 01:53:15.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 64
>> *Jan 25 01:53:15.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 64
>> *Jan 25 01:53:15.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 64
>> *Jan 25 01:53:15.523: socket 12 fatal error 0! can't write with size 0, fd
>> 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive 64
>> *Jan 25 01:53:15.527: socket 32 fatal error 0! can't write with size 0, fd
>> 32
>> HTANYC505a# phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 29
>> *Jan 25 01:53:15.527: socket 32 fatal error 0! can't write with size 0, fd
>> 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 29
>> *Jan 25 01:53:15.527: socket 32 fatal error 0! can't write with size 0, fd
>> 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 29
>> *Jan 25 01:53:15.527: socket 32 fatal error 0! can't write with size 0, fd
>> 32 phone tag 24 device name SEP0023EBC7EE7C state 1 keepalive 29
>> HTANYC505a#
>> *Jan 25 01:53:22.507: socket 12 fatal error 0! can't write with size
>> 1087474228, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 71
>> HTANYC505a#
>> *Jan 25 01:53:32.507: socket 12 fatal error 0! can't write with size
>> 1087474228, fd 12 phone tag 21 device name SEP0024C40BC4A7 state 1 keepalive
>> 81
>> HTANYC505a#un all
>> All possible debugging has been turned off
>>
>>
>> It is weird, the phone takes forever to register to CCME (CCME as SRST)
>> and once it does register the buttons don't work, it cannot make or receive
>> calls.
>>
>> This is a 7962 with a 7915 attached, there are 15 phones configured the
>> same way in the bull pen, two do not work, the other 13 are fine.
>>
>> Here is the ephone config:
>>
>>
>> ephone 24
>> device-security-mode none
>> description Jane Doe
>> mac-address 0023.EBC7.EE7C
>> max-calls-per-button 4
>> type 7962 addon 1 7915-12
>> button 1:24 2:29 3:25 4:22
>> button 5:13 7:28 8:31 9:23
>> button 10:20 11:26 12:21 13:19
>> button 14:27 15:10 16:18 17:30
>> button 18:45
>> pin 12345
>> !
>>
>> This is an exemplar of the ephone-dn config"
>>
>>
>> ephone-dn 24 octo-line
>> number 2773 secondary 2125552773
>> description 212-555-2773
>> name Jane Doe
>> allow watch
>> no huntstop
>> !
>> !
>>
>>
>> Any ideas?
>>
>> BTW, we have swapped the phone, sidecar, and cabling with known good and
>> the problem always follows the configuration...
>>
>> NOTE, if the sidecar is disconnected, the phone works fine... it also
>> works fine while the sidecar is booting...
>>
>>
>>
>> Jonathan
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100125/66fc0ce8/attachment.html>
More information about the cisco-voip
mailing list