Asterisk phone cisco 7. SIPCisco's latest 7. G)Introduction. Cisco recently released a new series of IP phones, the 7. G, 7. 91. 1G, 7. 94. G, 7. 96. 1G and 7. G series. The 7. 94. G- GE model which has gigabit copper connectivity through the phone, the others have just standard 1.
Скачивание документа 'Инструкция пользователя на IP-телефон Cisco CP-7911G на русском языке' бесплатно, но в коммерческих целях разрешено только с письменного согласия владельцев. IP-телефон Cisco Unified 7911G (Cisco Unified IP Phone 7911G) предназначен для работников в офисе, магазинах розничной торговли и цехах. Этот IP-телефон, представляющий собой базовую модель, дополненную определенными усовершенствованиями.
PC port. All these new phones sport new cool features, mostly along the lines of newer and better display units, initial support for SIP, but additionally - and this is a major change - config file management, which is now XML based rather than plain (name,value) text pairs. These phones supposedly will, in the future, support an enhanced range of features compared to the 7. Some product documentation on them can be found here.
Note that the 7. 94. G and 7. 96. 1G have been superseded by the 7. The End- Of- Sale and End- Of- Life announcement for the hardware of the 7.
Unfortunately the format of the config files has never been well documented on CCO and Google searching shows up a limited amount of content on "cisco SIP and cnf. SIP compliant phone services such as Asterisk. I recently opened a TAC case to find out more information about the format of the config files but Cisco were unwilling to assist - as as far as they are concerned if the phones are run in a Call.
Manager environment (which is what they were intended for) there is no need to manually edit the config files therefore they were not willing to give help running them in a non CM environment. It's a real shame really because these phones really are very nice handsets, and even if cisco did not want to support third party SIP servers, they could at least make information available so that others could do so. Here's a sample config file, documented tags are listed below. Note there is a minor error in this file as noted below. If you are aware of how to fix it please do so.
Cisco 7911G 4.0. Ряд функций (кроме базовых) работает корректно только с АТС на базе CISCO. Русский язык понимает только с прошивкой SCCP. (не смог настроить SIP + русский язык).
Please DO read this file in detail. You must change instances of things like YOURNTPSERVER and replace them either with an NTP server IP address, or remove the statement altogether. Leaving them in will confuse your phone, and at the very least cause it to reject parts of the config, if it loads it at all. Config File Editing. Note that the config file contents appear to be case sensitive, and most of the parameters start with a small letter after the opening bracket.< ? This line is strictly not needed, but is useful to have if you're trying to use characters not in the US- ASCII character range. Not sure what encodings Cisco phones supports, maybe UTF- 8 is supported?
Note: Be sure that your text editor is actually using the same encoding as the one you specify).< device xsi: type="axl: XIPPhone" ctiid="1. Note that there is a small syntax error of sorts in the statement above, the phone spits out a message: NOT 2. JVM: - XML unknown element or attribute name ("xsi: no. Namespace. Schema.
Location") (line=2) however it seems harmless.< device. Protocol> SIP< /device.
Protocol> Define these if you want to be able to ssh to the phone. After ssh'ing you can log in with debug/debug, or log/log to get some basic idea of what is going on, force the phone to re- register etc, or default/user to drop to a basic non- root shell.< ssh.
User. Id> username< /ssh. User. Id> < ssh.
- Скачивание документа 'Инструкция пользователя на IP-телефон Cisco CP-7911G на русском языке' бесплатно, но в коммерческих целях разрешено только с письменного согласия владельцев..
- Инструкции пользователя, руководства по эксплуатации и мануалы: Инструкция пользователя на IP-телефон Cisco CP-7911G на русском языке.
- Инструкции пользователя, руководства по эксплуатации и мануалы: Инструкция пользователя на IP-телефон Cisco CP- 7911G на русском языке.
Password> password< /ssh. Password> These next settings are for time related configuration, setting the timezone etc. If you do not specify an NTP server, the phone picks the date and time up from the SIP registration headers from the SIP server. On a LAN this should result in your phone getting sub millisecond accuracy to a local NTP server. You can find appropriate settings for the time. Zone parameter at http: //www.
If you copy and paste the relevant entry from the Description field into the < time. Zone> < /time. Zone> field in your config, then your phone should then display the correct local time on the phone.< date. Template> can be D- M- Y M- D- Y or Y- M- DYou can also use either dashes, dots, or forward slashes as separators in your date.
Template, these will be reflected in the date shown on the phone. There is probably also a way to get the phone to display either 1. I'm unsure how just yet (possibly a < time. Format> tag?)There is also 'a'/'A' attribute that sets if it's 1. D/M/Ya) (set for 1. Example: D- M- Y - -> 2.
D- M- Ya - -> 1. Note: if your using chan_sccp, you have to also set it on the server. For the times zones, you can use your local time zone, example: Pacific Standard/Daylight Time or New Zealand Standard/Daylight Time. Edit > > The following time zones are also for the 7.
UTC Standard/Daylight Time for your local time zone but must be written precisely as follows including caps and punctuation (any deviation from the following will result in the time being automatically returned to UTC): Dateline Standard Time. Samoa Standard Time. Hawaiian Standard Time.
Alaskan Standard/Daylight Time. Pacific Standard/Daylight Time. Mountain Standard/Daylight Time. US Mountain Standard Time. Central Standard/Daylight Time.
Mexico Standard/Daylight Time. Canada Central Standard Time. SA Pacific Standard Time. Eastern Standard/Daylight Time. US Eastern Standard Time. Atlantic Standard/Daylight Time.
SA Western Standard Time. Newfoundland Standard/Daylight Time. South America Standard/Daylight Time. SA Eastern Standard Time. Mid- Atlantic Standard/Daylight Time. Azores Standard/Daylight Time.
GMT Standard/Daylight Time. Greenwich Standard Time. W. Europe Standard/Daylight Time. GTB Standard/Daylight Time.
Egypt Standard/Daylight Time. E. Europe Standard/Daylight Time. Romance Standard/Daylight Time. Central Europe Standard/Daylight Time. South Africa Standard Time. Jerusalem Standard/Daylight Time. Saudi Arabia Standard Time.
Russian Standard/Daylight Time. Iran Standard/Daylight Time. Caucasus Standard/Daylight Time. Arabian Standard Time.
Afghanistan Standard Time. West Asia Standard Time. Ekaterinburg Standard Time.
India Standard Time. Central Asia Standard Time.
SE Asia Standard Time. China Standard/Daylight Time. Taipei Standard Time. Tokyo Standard Time. Cen. Australia Standard/Daylight Time. AUS Central Standard Time.
E. Australia Standard Time. AUS Eastern Standard/Daylight Time. West Pacific Standard Time. Tasmania Standard/Daylight Time. Central Pacific Standard Time. Fiji Standard Time.
New Zealand Standard/Daylight Time< device. Pool> < date. Time. Setting> < date. Template> D- M- YA< /date.
Template> < time. Zone> UTC Standard/Daylight Time< /time.
Zone> < ntps> < ntp> < name> YOURNTPSERVERIPADDRESS< /name> < ntp. Mode> Unicast< /ntp. Mode> < /ntp> < /ntps> < /date. Time. Setting> This next part is required, otherwise the phone claims to be unprovisioned. It just requires your SIP server's DNS name. It also appears that the phone will not pick up some XML configuration changes if the < call.
Manager. Group> element is not present.< call. Manager. Group> < members> < member priority="0"> < call.
Manager> < ports> < ethernet. Phone. Port> 2. Phone. Port> < sip.
Port> 5. 06. 0< /sip. Port> < secured. Sip. Port> 5. 06. Sip. Port> < /ports> < process. Node. Name> PUTYOURSIPSERVERNAMEINHERE< /process. Node. Name> < /call.
Manager> < /member> < /members> < /call. Manager. Group> < /device. Pool> Generally don't need to specify these, but maybe you will want to put in the register line. Note that the opening and closing tags of these elements must be on the same line, or else it won't be able to do integer conversion (I think this is a bug).< sip.
Profile> < sip. Proxies> < backup. Proxy> < /backup.
Proxy> < backup. Proxy. Port> < /backup.
Proxy. Port> < emergency. Proxy> < /emergency.
Proxy> < emergency. Proxy. Port> < /emergency. Proxy. Port> < outbound. Proxy> < /outbound. Proxy> < outbound.
Proxy. Port> < /outbound. Proxy. Port> < register. With. Proxy> true< /register. With. Proxy> < /sip. Proxies> Some basic features and settings.< sip.
Call. Features> < cnf. Join. Enabled> true< /cnf. Join. Enabled> < call. Forward. URI> x- cisco- serviceuri- cfwdall< /call. Forward. URI> < call. Pickup. URI> x- cisco- serviceuri- pickup< /call. Pickup. URI> < call.
Pickup. List. URI> x- cisco- serviceuri- opickup< /call. Pickup. List. URI> < call. Pickup. Group. URI> x- cisco- serviceuri- gpickup< /call. Pickup. Group. URI> < meet. Me. Service. URI> x- cisco- serviceuri- meetme< /meet. Me. Service. URI> < abbreviated.
Dial. URI> x- cisco- serviceuri- abbrdial< /abbreviated. Dial. URI> < rfc. Hold> false< /rfc.
Hold> < call. Hold. Ringback> 2< /call.
Hold. Ringback> < local. Cfwd. Enable> true< /local. Cfwd. Enable> < semi. Attended. Transfer> true< /semi. Attended. Transfer> < anonymous. Call. Block> 2< /anonymous.
Call. Block> < caller. Id. Blocking> 2< /caller. Id. Blocking> < dnd. Control> 0< /dnd. Control> < remote. Cc. Enable> true< /remote. Cc. Enable> < /sip.
Call. Features> These are to do with SIP connection control.< sip. Stack> < sip. Invite. Retx> 6< /sip. Invite. Retx> < sip. Retx> 1. 0< /sip. Retx> < timer. Invite. Expires> 1.
Invite. Expires> < timer. Register. Expires> 3. Register. Expires> < timer. Register. Delta> 5< /timer. Register. Delta> < timer.
Keep. Alive. Expires> 1. Keep. Alive. Expires> < timer. Subscribe. Expires> 1.
Subscribe. Expires> < timer. Subscribe. Delta> 5< /timer.
Subscribe. Delta> < timer. T1> 5. 00< /timer.
T1> < timer. T2> 4. 00. 0< /timer.
T2> < max. Redirects> 7. Redirects> < remote.
Party. ID> false< /remote. Party. ID> < user. Info> None< /user. Info> < /sip.