No way to do something like it on SPA[35]xx as far as I know. ... View more

We are in Small Business Support Community part of Cisco Community so I assumed SMB phones like SPA3xx or SPA5xx.   One more note - Line key can be configured to invoke internal "browser" - you can request remote page and do something with response (it's not standard HTML but CIsco's custom XML-like format instead). It allows you to craft complex extensions to phone UI according your requirements. Even this solution depends on (API of) PBX you have.   ... View more

is it possible to enable and disable call Forwarding to a specific number with only one line key ? Line Key can have two predefined sequences to dial. It alternates between them. But it's just dumb flip-flop mechanism, no feedback. Thus key state may not be synchronised with the PBX state. I dislike it, but you may consider it acceptable.   Or, if you PBX is smart/configurable enough, you may dial just single sequence - it's up to PBX to turn forwarding on if it has been off and vice versa.   So is there a solution where line key 1 turns red when enabling Forwarding and the turns green again when disabling it with line key 2 ?    It depends. Line key color can be linked with a state provider (SIP SUBSCRIBE method). It's intended to be used as Busy Lamp, but it can display any state published by PBX. Our PBX publishes state of many supplemental services, so I can link a line key not only to state of CFU, but also other flavors of forwarding services, to DND service and many others. So answer to your question depends on features of the PBX you are using ... View more

Partially (log messages are not documented by Cisco, so I'm guessing).   SPA8000 is bundle of 4x (2-line) ATA. According LOG you provided, only (M1, M2, M3) are initializing, there's no message related to module M4. It seems M4 module is dead. Try disable M4 module (lines 7 & 8) and may be even M3 module (lines 5 & 6)  - it may (or may not) help.   Unfortunately, even initialization of M1-M3 modules seems not to be completed and is looping. M1 & M2 claims reboot reason H736c0053, M3 claims reboot reason H737201dc. Meaning of those codes is not documented.   All I know is H means hardware reboot, usually caused by power or code reset.  Nearest known codes are 73720168 (code corruption [recover by performing a factory reset]) and 7372016c (code corruption)   So I suspect your hardware is just broken. You may try to re-flash firmware (may be the firmware image is broken only, not physical hardware) but I don't bet on it.   By the way, consider to delete duplicate thread you created.   Below is the list of reboot reasons indicated by the SPA-Voice products. Copied from former CSC document DOC-9889 now moved to Reboot reason list . C means cold reboot W means warm reboot, won't redo dhcp H means hardware reboot, usually caused by power or code reset 0x00000000 Boot due to power on, reported as "reboot reason:H0" in syslog 0x00000001 DHCP fail 0x00000004 parameter changes (through web, provisioning. For example when device's profile rule is changed...) syslog log will show "reboot reason:W4" 0x00000008 upgraded successfully 0x00000010 reboot requested by IVR or Web 0x00000016 parameter mismatch [example you are changing a parameter that should not be changed such as MWI] 0x00000020 upgrade backoff 0x00000040 reboot requested by SIP 0x00000080 upgrade failed 0x00000100 channel swap detected 0x00000200 Ethernet Link down 0x00000400 SIP Error 0x00000800 Slic Alarm detected 0x00001000 duplicate IP detected 0x00002000 Using last good known IP and reboot after 30 minutes 0x00004000 slic error 0x00008000 slic error 0x00010000 resource exhausted 0x00020000 pppoe failed 0x00040000 WAN and LAN subnet conflict 0x00080000 TDM error 0x00200000 reboot caused by DHCP auto sensing feature 0x00400000 reboot caused by remote customization syslog will show "reboot reason:Hxxxxxxxx" 0x30300010 phone reboot caused by selecting "reboot" on phone's interface  or /admin/reboot 0x633a02d1 out of memory 0x73720168 code corruption [recover by performing a factory reset] 0x7372016c code corruption 0x737202d1 out of memory 0x7372092b IP address change due to DHCP lease expiring   ... View more

Line >=3 status show even no Hook state. So I suspect either broken hardware or internal (saved form of) configuration is broken badly. Reset to factory default and configure from scratch. If it doesn't help, turn on syslog&debug (highest level possible) and capture messages on external syslog server. It may disclose the cause. ... View more

Sorry, so vague description of issue. "it doesn't work" is rather no description at all. Thus only generic advice is possible - your configuration is wrong (while we know nothing about VoIP operator requirements, so we can't advise). Line may not be registered, line may be registered but call gets rejected by operator ... No one knows with no data to analyze. ... View more

Someone is responsible just now. Term "administrator" used in my previous message refers this person. Once more - If you are administrator of your phone system, reset phones to factory default then configure them from scratch. If you are not administrator, ask administrator for help. ... View more

Is there an over ride password to unlock this type of phones? No one currently working here knows what the passwords If you are administrator of your phone system, reset phones to factory default then configure them from scratch. As asministrator you know how to configure them. If you are not administrator, ask administrator for help.   Dumbest thing ever...passwords You are administrator of your phone system. If your system configuration doesn't follow your wishes, complain to self.    ... View more

Phone do no call transfer by self. It just sends call transfer request to upstream proxy (e.g. VoIP.MS). Thus you should ask VoIP.MS for details. ... View more

Release Notes for Cisco Small Business SPA525G2 IP Phone Firmware Version 7.6(2)SR5 mentions no 7.5.2b firmware. ... View more

While I can guess how you have connected analog phone to SPA3102, I have no idea how you are connecting your mobile phone to SPA3102. Neither SPA3102 nor mobile phone have port suitable for interconnection.Assuming you are using term "mobile phone" for a cellular phone like GSM phone or so. Can you describe your topology ? ... View more