login | register
Sat 17 of May, 2008 [06:38 UTC]

voip-info.org

Search with Google
Search this site with Google. Results may not include recent changes.
 
Google Ads
Shoutbox
  • Juan Ortega, Thu 15 of May, 2008 [10:33 UTC]: Hi everybody, I'm Juan, an ITCom student, and I need to know what basic elements I need to create a VoIP network. Can anybody helpme, please?,Thank you very much
  • gineta, Wed 14 of May, 2008 [03:58 UTC]: any here not fine the configuration of firewall juniper -screem for VOIP asterisk????
  • Anoop Prabhakaran, Tue 13 of May, 2008 [12:16 UTC]: I am developing Asterisk IVR, Whenever i make a internation call to the IVR system, the DTMF is not getting detected properly, this happens only for the first time, second call onwards system works fine. why this is happening
  • joe, Mon 12 of May, 2008 [04:27 UTC]: Is there an opensource browser based softphone, or a system like Busta where everything is not manages through their website?
  • Nick Barnes, Fri 09 of May, 2008 [11:36 UTC]: Christopher - yesterday I tried an Asterisk install on a CentOS 5.1 box with stock GUI and it all worked fine. Sorry I can't help.
  • aero, Fri 09 of May, 2008 [08:20 UTC]: can someone help me out on this, i tried to play some sound files on my asterisk box and this is the error message i got. WARNING[4429]: format_wav.c:169 check_header: Unexpected freqency 22050 May 8 11:17:39 WARNING[4433]: codec_gsm.c:194 gsmtolin_fra
  • Christopher Faust, Thu 08 of May, 2008 [14:15 UTC]: I beleive that I may have to change something in the xserver configuration. Please advise
  • Christopher Faust, Thu 08 of May, 2008 [14:14 UTC]: Everything was perfect. In the bios I have increased the memory allocated Still receive input not supported on my display.
  • Christopher Faust, Thu 08 of May, 2008 [14:13 UTC]: This would not be my main box. I am doing some testing to see if I can install zaptel and asterisk 1.4 on a full centos 5.1 box with development software Its bizzare, because before I went through the asterisk and zaptel installation everything was perfe
  • Nick Barnes, Thu 08 of May, 2008 [13:44 UTC]: Christopher - I can't see any way in which an Asterisk installation would muck your GUI, but remember that it is advised not to use a GUI on an Asterisk box anyway.
Server Stats
  • Execution time: 0.51s
  • Memory usage: 2.37MB
  • Database queries: 28
  • GZIP: Disabled
  • Server load: 0.33

Cisco 7905/7912 IP Phones

Basic Config


The 7905/7912 series phones from Cisco use a different style of config files when configuring from TFTP. One composes the configuration file and then converts it to a binary format the phone can read. This conversion is done using the cfgfmt utility which you can find in the .zip file of your firmware image.

The filenames of the config files are gkdefault.cnf for the default settings and gk<$mac_address> for the phone-specific configuration, for the 7912. For the 7905, change "gk" to "ld".

It is also possible to configure the phone from the lcd screen, for this press the globe button, select settings, go to network or SIP settings and press **# to unlock the settings (if you don't do this you won't be able to edit them).
If your phone asks for a password you might want to reset it to the factory defaults. The default password (for the 7912) is 1234.

the administration guide can be found at:
http://www.cisco.com/en/US/products/hw/phones/ps379/products_administration_guide_book09186a00801b178c.html

firmware and other software can be found at:
http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml if you have a Cisco CCO login. Otherwise you need to buy a service contract, $8-15 a year.

Audio Parameters

The default SIP software load results in an odd fault, no receive audio on many calls except if you dial a digit after the call connects. This is due to silence suppression being on by default. This can be changed in the web configuration under Audio Parameters, be sure that AudioMode is set to 0x00000010 rather than 0x00000011.

Note that the bits of the Audio Parameters also set the DTMF method used, as follows:

Bit 0: G.711 silence suppression:

–0=Disable.

–1=Enable.

Bits 1-3: Reserved.

Bits 4-5: DTMF transmission method:

–0=Always inband.

–1=Negotiated via SDP.

–2=Always out-of-band.

Bits 6-31: Reserved.

CODEC

Choice of CODEC is set via the RxCodec and TxCodec parameters as follows:

1 = G.711A-law

2 = G.711u-law

3 = G.729a


Further details for some of the less obvious settings can be found on this Cisco Web page

Upgrading the software


Download the firmware package, copy the upgradecode line from the gkdefault.txt file in the package, paste it into your SIP config textfile and run the cfgfmt program (cfgfmt.exe for windows, cfgfmt.linux for linux and dfgfmt.sun for sun) to convert it to binary. Upload the firmware .sbin (or .zup with older 7905's) and the new gkdefault.cnf to your tftp server and reboot the phone.
A shortcut to reboot / restart Cisco 7905G phones is **#**.


Changing the logo


It is also possible to change the logo on these phones, but a different approach is needed than with the 7940/60 series.
First one has to make a monochrome .bmp of 88 by 27 pixels, and save this somewhere.
Then you have to get the bmp2logo.exe program (included in firmware release zip files or separately downloadable at cisco.com).

bmp2logo download

syntax: bmp2logo.exe <imageid> <infile> <outfile>

image id: a unique integer identifier for this image
infile: the input .bmp file (make sure it's monochrome and not grayscale)
outfile: the output cisco logo file, any file extension will do

example: bmp2logo.exe 10 newlogo.bmp newlogo.logo

and then in your config txt file you have to add:
upgradelogo:$imageid,0,$logo_filename

so in this case it would be:
upgradelogo:10,0,newlogo.logo

And naturally you have to convert this to binary again with the cfgfmt program and upload the binary config and logo file to your tftp server and you should be all set.

For those without Windows systems, Pontus Freyhult has implemented the same functionality in Python, which should run fine on most systems (does require Python Imaging Library though). http://soua.net/img2logo.py

Resetting to factory defaults

Read the next section before doing this!

Step 1 Press the Menu button.

Step 2 Use the Navigation button to select Settings, and then press the Select softkey.

Step 3 Use the Navigation button to select Network Configuration, and then press the Select softkey.

Step 4 Perform either of these procedures:

Procedure A:

  • Press **2. The phone displays "Do you want to reset all system settings to default values?"

  • Press the Yes softkey.

Procedure B:

  • Press **#. If your phone displays "Enter Admin Password," enter your password and then press the Enter softkey. Make sure that an unlocked padlock icon appears in the upper-right corner of your LCD.

  • Scroll to Erase Configuration.

  • Press the Yes softkey and then press the Save softkey.

The phone cycles through normal startup procedures.

Problems if no default password set

If you do set your phone back to factory defaults, it may have a blank admin password (the 'UIPassword'), in which case you can no longer change the phone's settings from the Web interface! The only way to re-setup the UIPassword is via TFTP, which means you need to have a tftp server running on your network. A very useful, free, Windows-based TFTP server can be found here: TFTPD32

In order to re-setup the UIPassword, your TFTP server must present the file gkdefault.cfg (7912) or lddefault.cfg (7905) to the phone as it boots (in fact, the parameters placed in these files are picked up by ANY 7912/7905 as they boot.) The contents of the .cfg file start out as a text file containing something similar to the following:


 # Set the GUI/Web config password to 1234; the password must NOT be 0 
 # (disabled) if configuring via the phone's web interface is desired.

 UIPassword:1234

Unfortunately, the actual .cfg file is made by using a Cisco software tool to compile the text file into the desired .cfg file - and this tool is only available to users with support contracts. If you do obtain the official software kit then there is a sample .cfg containing the required text that can just be copied to your TFTP root folder.

if you do not have the ability to re-setup your UIPassword then you may want to carefully consider whether resetting your phone completely is a good idea!

Footnote: All of this hassle seems to be Cisco's way of 'punishing' those who dare to use SIP on these phones!

Rebooting the phone


The phone can be reset through the keypad by scrolling into Settings, then pressing **#** and answering "yes" to the prompt "do you wish to reboot the phone?"

SIP Software Limitations (please add)


So far I have come by the following limitations (software 1.3)

  • XML services are not supported

Cisco Announcement of End of Sale/End of Life for the 7905G


Cisco has recently announced that the 7905G phone will become End of Sale on 01-JUN-2006, end of software maintenance on 01-JUN-2007 and End of Support on 01-JUN-2011.

Customers are encouraged to migrate to the Cisco IP Phone 7906G when available (approximately May '06). The Cisco IP Phone 7906G will offer a greater feature set than the current Cisco IP Phone 7905G. When ready, information about the replacement product will be found at: http://www.cisco.com/en/US/products/hw/phones/ps379/index.html.




Created by Wence Van der Meersch, Last modification by Pontus on Fri 17 of Aug, 2007 [14:59 UTC]

Comments Filter

Re: Example gkMAC.cfg file

by Elias Aggelidis on Saturday 13 of January, 2007 [14:16:35 UTC]
  1. txt
  2. -----------------------------------------------------------------------------
  3. Example Profile for Cisco 7905G/7912G IP Phones (SIP)
  4. -----------------------------------------------------------------------------
  5. IMPORTANT: File must begin with "#txt" (without the quotes) for the
  6. formating tool (cfgfmt.exe) to treat it as a text file.
  7. NOTE: 1. A hash (#) at the beginning of the line is a comment. The
  8. formatting tool ignores any line beginning with the token.
  9. 2. All parameter/value pairs are OPTIONAL; however, they may be
  10. needed nevertheless for the phone to function properly
  11. if no prior value had been programmed.
  12. 3. Parameter values can be one of the following:
  13. a. Alphanumeric string
  14. Ex: SIP-4-Ever$#, 1234, #012-34la$!-
  15. b. Numeric digit string
  16. Ex: 593, 960135, 19690489
  17. c. Array of comma-separated short integer
  18. Ex: {395,65534,20,32768,105} (without brackets)
  19. d. IP address
  20. Ex: 192.168.2.170, 64.15.243.3
  21. e. Extended IP address — IP address with Port
  22. Ex: 192.168.2.170.9001, 174.10.232.53.10364
  23. f. Boolean
  24. Ex: 0 or 1
  25. g. Bitmap value — unsigned hex integer (32-bit)
  26. Ex: 0x00060400, 0x125f0431
  27. h. Integer (32-bit)
  28. Ex: 2147483647, 56, 65342
  29. ========================== UI Parameters ==============================
  30. -----------------------------------------------------------------------------
  31. Parameter: UIPassword
  32. Type: Alphanumeric string (9 characters max)
  33. Description: Control access to the web page and some protected phone menus.
  34. If set to non-zero, then every access to the web page will
  35. require the value of UIPassword being entered.
  36. Default: 0 = Web interface is restricted to viewing of device
  37. information and network configuration and statistics.
  38. Parameter changes are not allowed via the web interface.

UIPassword:cisco

  1. =================== Firmware Upgrade Parameters ====================
  2. -----------------------------------------------------------------------------
  3. Parameter: upgradecode
  4. Description: Special parameter to provide information on how to upgrade
  5. firmware code.
  6. Syntax: upgradecode:3,hw_type,0x0400,0x0100,tftp_ip_addr,69,image_id,
  7. image_filename
  8. Options: hw_type
  9. - IP Phone hardware type
  10. Use For
  11. ----- --------------------
  12. 0x501 Cisco 7905G IP phone
  13. 0x601 Cisco 7912G IP phone
  14. tftp_ip_addr
  15. - TFTP server IP address where the image_filename is located
  16. image_id
  17. - A unique 32-bit integer value different from upgrade to
  18. upgrade. A simple way to derive this 32-bit integer value
  19. is to use the build date on the image file name and
  20. prepending it with "0x" (e.g. if the image_filename is
  21. CP7905010100SIP030807A.zup, then the build date is 030807A,
  22. and the image_id is 0x030807A)
  23. image_filename
  24. - Firmware upgrade image file name. The file name has the
  25. following syntax:
  26. CP79{XX}{MM}{NN}{PP}{protocol}{yymmdd}{a-f}.{ext}
  27. XX - IP phone model number
  28. MM - Major version number
  29. NN - Minor version number
  30. PP - Build version number
  31. protocol - h323, sip or sccp
  32. yymmdd - Year, month, day
  33. a-f - Build letter
  34. ext - File extension name - .zup or .sbin
  35. yymmdd and a-f together form the build date of the image.
  36. Examples: For Cisco 7905G IP phone
  37. ------------------------
  38. upgradecode:3,0x501,0x0400,0x0100,192.168.2.170,69,
  39. 0x030807a,CP7905010100SIP030807A.zup
  40. For Cisco 7912G IP phone
  41. ------------------------
  42. upgradecode:3,0x601,0x0400,0x0100,192.168.2.170,69,
  43. 0x030807a,CP7912010100SIP030807A.sbin
  44. NOTE: The default values listed below for a Cisco 7905G IP phone
  45. will not trigger any upgrade. Please make sure the correct
  46. HARDWARE TYPE is specified for your Cisco IP phone.

upgradecode:3,0x601,0x0400,0x0100,10.19.140.13,69,0x060412A,CP7912080001SIP060412A.sbin

  1. ==================== Logo Upgrade Parameter =====================
  2. -----------------------------------------------------------------------------
  3. Parameter: upgradelogo
  4. Description: Special parameter to provide information on how to upgrade the
  5. logo on the main LCD screen
  6. Syntax: upgradelogo:<image_id>,<tftp_ip_addr>,<logo_filename>
  7. Options: image_id
  8. - A unique number that is logically associated with the logo
  9. file and must be incremented for each new logo upgrade;
  10. the factory logo is assigned '1'. Upgrading the firmware
  11. resets this value to '1'.
  12. tftp_ip_addr
  13. - TFTP server IP address where logo_filename is located
  14. logo_filename
  15. - Name of logo file
  16. Example: upgradelogo:4,192.168.3.105,logo.dat
  17. NOTE: The default values listed below will not trigger any upgrade.

  1. upgradelogo:0,0,none

  1. =============== Network Configuration Parameters ===================
  2. -----------------------------------------------------------------------------
  3. Parameter: Dhcp
  4. Type: Boolean
  5. Options: 1 = Use DHCP to obtain IP, route, netmask, DNS, NTP, TFTP, etc.
  6. 0 = Don't use DHCP, instead use hard coded parameter values for
  7. IP, route, netmask, DNS, NTP, TFTP, etc.

dhcp:1

  1. -----------------------------------------------------------------------------
  2. Parameters: staticIp
  3. staticRoute
  4. staticSubNetMask
  5. Type: IP address
  6. Description: If Dhcp parameter is set to 0, use these parameters to
  7. assign a static IP address, route IP address, and subnet mask

StaticIp:10.19.140.21
StaticRoute:10.19.140.1
StaticNetMask:255.255.255.192

  1. ==================== SIP Configuration Parameters =====================
  2. -----------------------------------------------------------------------------
  3. Parameter: Proxy
  4. Type: Alphanumeric string (31 characters max)
  5. Description: IP address or domain name of SIP proxy server

Proxy:sip.awmn

  1. -----------------------------------------------------------------------------
  2. Parameter: Proxy2
  3. Type: Alphanumeric string (31 characters max)
  4. Description: Second SIP proxy server
  5. NOTE: FOR USE WITH CISCO CALL MANAGER ONLY

  1. Proxy2:0

  1. -----------------------------------------------------------------------------
  2. Parameter: Proxy3
  3. Type: IP address
  4. Description: Third SIP proxy server
  5. NOTE: FOR USE WITH CISCO CALL MANAGER ONLY

  1. Proxy3:0

  1. -----------------------------------------------------------------------------
  2. Parameter: Proxy4
  3. Type: IP address
  4. Description: Fourth SIP proxy server
  5. NOTE: FOR USE WITH CISCO CALL MANAGER ONLY

  1. Proxy4:0

  1. -----------------------------------------------------------------------------
  2. Parameter: AltProxyTimeOut
  3. Type: Integer (0 - 4294967295 seconds)
  4. Description: Timeout in seconds for switching from backup proxy to primary
  5. proxy. If this parameter is set to 0, the phone will remain
  6. with the backup proxy indefinitely until it fails.

AltProxyTimeOut:0

  1. -----------------------------------------------------------------------------
  2. Parameter: UID
  3. Type: Alphanumeric string (31 characters max)
  4. Description: User ID (i.e. phone number) for the line

UID:27641

  1. -----------------------------------------------------------------------------
  2. Parameter: PWD
  3. Type: Alphanumeric string (31 characters max)
  4. Description: Password used for authentication

PWD:0

  1. -----------------------------------------------------------------------------
  2. Parameter: LoginID
  3. Type: Alphanumeric string (51 characters max)
  4. Description: User ID used for authentication, if different from UID.

LoginID:0

  1. -----------------------------------------------------------------------------
  2. Parameter: UseLoginID
  3. Type: Boolean
  4. Description: Indicate user ID to use for authentication
  5. Options: 0 = Use UID as user ID for authentication
  6. 1 = Use LoginID as user ID for authentication

UseLoginID:0

  1. -----------------------------------------------------------------------------
  2. Parameter: SIPPort
  3. Type: Integer (1 - 65535)
  4. Description: Port to listen for incoming SIP requests.
  5. The same port is used for sending outgoing SIP requests.

SIPPort:5060

  1. -----------------------------------------------------------------------------
  2. Parameter: SIPRegInterval
  3. Type: Integer (1 - 86400 seconds)
  4. Description: Interval between registration renewal

SIPRegInterval:3600

  1. -----------------------------------------------------------------------------
  2. Parameter: SIPRegInterval2
  3. Type: Integer (1 - 4294967295 seconds)
  4. Description: Interval between Keep-Alives sent to backup SIP proxies.
  5. NOTE: FOR USE WITH CISCO CALL MANAGER ONLY

  1. SIPRegInterval2:120

  1. -----------------------------------------------------------------------------
  2. Parameter: SIPRegOn
  3. Type: Boolean
  4. Description: Enable or disable SIP registration
  5. Options: 0 = Disable registration
  6. 1 = Enable registration

SIPRegOn:1

  1. -----------------------------------------------------------------------------
  2. Parameter: MAXRedirect
  3. Type: Integer (0 - 10)
  4. Description: Maximum number of times to try redirection
  5. Note: If set to greater than 10, default is 10 times.

MaxRedirect:5

  1. -----------------------------------------------------------------------------
  2. Parameter: OutBoundProxy
  3. Type: IP address or alphanumeric string (31 characters max)
  4. Description: Outbound proxy server that processes all outbound SIP requests.
  5. It can be an IP address with or without a port parameter such
  6. as 123.123.110.45, 123.123.110.45.5060, or 123.123.110.45:5061,
  7. or URL such as sip.cisco.com, sip.komodo.cisco.com:5061. For
  8. IP address, a '.' or ':' can be used to delimit a port
  9. parameter. For URL, a ':' must be used to delimit the port
  10. parameter.
  11. Note: If this parameter is configured, all SIP requests will be
  12. sent to this outbound proxy and then forwarded to the
  13. destination specified in the Request-URI of the SIP message.
  14. An outbound proxy may or may not be the same SIP proxy server.

OutBoundProxy:0

  1. -----------------------------------------------------------------------------
  2. Parameter: RxCodec
  3. Type: Integer (1 - 3)
  4. Description: Preferred receiving audio codec
  5. Options: 1 — g711a
  6. 2 — g711u
  7. 3 — g729a

RxCodec:2

  1. -----------------------------------------------------------------------------
  2. Parameter: TxCodec
  3. Type: Integer (1 - 3)
  4. Description: Preferred transmitting audio codec
  5. Options: 1 — g711a
  6. 2 — g711u
  7. 3 — g729a

TxCodec:2

  1. -----------------------------------------------------------------------------
  2. Parameter: MsgRetryLimits
  3. Type: Bitmap
  4. Description: Specify number of times SIP requests and final responses to
  5. INVITE request are retransmitted to the current SIP user agent.
  6. Options: Bit Values
  7. ----- --------------------------------------------------------
  8. 0-3 Number of times to retransmit SIP requests, except
  9. those listed below, and final response to INVITE
  10. Range: 0-15
  11. Default: 0 = NOTIFY retransmitted 6 times
  12. PRACK restransmitted 5 times
  13. Response to INVITE retransmitted 7 times
  14. 4-7 Number of times to retransmit REGISTER request
  15. Range: 0-15 Default: 0 (= 10 times)
  16. 8-11 Number of times to retransmit INVITE request
  17. Range: 0-15 Default: 0 (= 2 times)
  18. 12-15 Number of times to retransmit BYE request
  19. Range: 0-15 Default: 0 (= 4 times)
  20. 16-19 Number of times to retransmit CANCEL request
  21. Range: 0-15 Default: 0 (= 4 times)
  22. 20-23 Number of times to retransmit REFER request
  23. Range: 0-15 Default: 0 (= 5 times)
  24. 24-31 RESERVED

MsgRetryLimits:0x00000000

  1. =================== Audio Configuration Parameters ====================
  2. -----------------------------------------------------------------------------
  3. Parameter: AudioMode
  4. Type: bitmap value
  5. Description: Used for controlling or fine-tuning certain audio features
  6. Options: Bit Values
  7. ----- --------------------------------------------------------
  8. 0 Silence Suppression
  9. 0 = Disable silence suppression
  10. *1 = Enable silence suppression
  11. 1-3 RESERVED. Must be set to 0.
  12. 4-5 DTMF Transmission Method
  13. 0 = Always inband
  14. *1 = Negotiated via SDP
  15. 2 = Always out-of-band
  16. 6-31 RESERVED. Must be set to 0.
  17. Defaults are marked with *.

AudioMode:0x00000011

  1. ------------------------------------------------------------------------
  2. Parameter: NumTxFrames
  3. Type: Integer (1 - 6)
  4. Description: Transmit frames per packet.
  5. Note: G.711 and G.729 frame sizes are 10 ms per frame.
  6. Cisco recommends that you use only the default value 2.

NumTxFrames:2

  1. ------------------------------------------------------------------------
  2. Parameter: ConnectMode
  3. Type: bitmap value
  4. Description: Connection mode of the protocol used
  5. Options: Bit Values
  6. ----- --------------------------------------------------------
  7. 0 Send INVITE requests (due to call forwarding, call
  8. transfer, etc.) to the URL specified in the
  9. corresponding header value, i.e. 302's Contact,
  10. Refer-To, etc.
  11. *0 = Disable. INVITE is sent via local proxy.
  12. 1 = Enable. INVITE is sent via specified URL.
  13. 1-3 RESERVED. Must be set to 0.
  14. 4 Include +sip.instance=... in REGISTER's Contact:
  15. 0 = Disable
  16. *1 = Enable
  17. 5-15 RESERVED. Must be set to 0.
  18. 16 Registration Removal Prior To Re-Registration
  19. *0 = Disable
  20. 1 = On power up, "Contact: *" is used to remove all
  21. registrations. On subsequent registration cycles,
  22. "Contact: <CURRENT_SIP_URL>;expires=0" is used.
  23. 17 RESERVED. Must be set to 0.
  24. 18 SIP Proxy Type
  25. *0 = Standard or no SIP proxy
  26. 1 = Cisco Call Manager
  27. 19 IP Ringback and Early Media
  28. *0 = Do not send ringback tone to the caller
  29. 1 = Send ring back tone to the caller
  30. 20 Include "action=proxy" in REGISTER request
  31. *0 = Disable
  32. 1 = Enable
  33. 21 Include "action=redirect" in REGISTER request
  34. *0 = Disable
  35. 1 = Enable
  36. 22 Process "received=" tag in VIA header to automatically
  37. detect if phone is behind a NAT and use specified WAN IP
  38. *0 = Disable
  39. 1 = Enable
  40. 23 RESERVED. Must be set to 0.
  41. 24 Include RTP statistics in BYE and 200 response to BYE
  42. *0 = Disable
  43. 1 = Enable
  44. 25-31 RESERVED. Must be set to 0.
  45. Defaults are marked with *.
  46. Note: Setting both bits 20 & 21 is forbidden; setting both to 0
  47. causes the phone to not include the "action" parameter in
  48. the REGISTER request and leaves it up to the proxy server
  49. to decide what action to take.

ConnectMode:0x00000010

  1. -----------------------------------------------------------------------------
  2. Parameter: TimeZone
  3. Type: Integer (0 - 24)
  4. Description: Timezone offset from GMT for time-stamping incoming calls with
  5. the local time (for caller-id display, etc.)
  6. Use the following table to select the correct TimeZone value.
  7. 0 = GMT 9 = GMT + 9 18 = GMT - 7
  8. 1 = GMT + 1 10 = GMT + 10 19 = GMT - 6
  9. 2 = GMT + 2 11 = GMT + 11 20 = GMT - 5
  10. 3 = GMT + 3 12 = GMT + 12 21 = GMT - 4
  11. 4 = GMT + 4 13 = GMT - 12 22 = GMT - 3
  12. 5 = GMT + 5 14 = GMT - 11 23 = GMT - 2
  13. 6 = GMT + 6 15 = GMT - 10 24 = GMT - 1
  14. 7 = GMT + 7 16 = GMT - 9
  15. 8 = GMT + 8 17 = GMT - 8
  16. Type: Integer ( -720 thru -60, 60 thru 780)
  17. Description: Timezone offset (in minutes) from GMT used for cities/countries
  18. that fall on 30 and 45 minutes zones.
  19. Use the following table to select the correct TimeZone value.
  20. 210 = GMT + 3:30 Tehran
  21. 270 = GMT + 4:30 Kabul
  22. 330 = GMT + 5:30 Calcutta, Chennai, Mumbai, New Delhi
  23. 345 = GMT + 5:45 Kathmandu
  24. 390 = GMT + 6:30 Rangoon
  25. 570 = GMT + 9:30 Darwin, Adelaide
  26. -210 = GMT - 3:30 Newfoundland
  27. Formula for calculating TimeZone in Minutes:
  28. (#hr * 60min/hr) + #min = total #min
  29. Sample calculation for Darwin (GMT + 9:30):
  30. (9hr * 60min/hr) + 30min = 570min

TimeZone:2

  1. -----------------------------------------------------------------------------
  2. Parameter: NTPIP
  3. Type: IP address
  4. Description: NTP IP address. This is an OPTIONAL parameter; however, if
  5. this parameter value is not configured and the DHCP server
  6. does not provide the value, then the time and caller ID time
  7. information will be incorrect.

NTPIP:10.19.140.1

  1. -----------------------------------------------------------------------------
  2. Parameter: AltNTPIP
  3. Type: IP address
  4. Description: Alternate NTP IP address (if redundancy is desired)

AltNTPIP:0.0.0.0

  1. -----------------------------------------------------------------------------
  2. Parameters: DNS1IP
  3. DNS2IP
  4. Type: IP address
  5. Description: Primary and secondary DNS server IP addresses
  6. If the DHCP server does not provide them or Dhcp parameter is
  7. set to 0, you must provide at least the primary DNS server IP
  8. address; otherwise, domain names cannot be resolved.

DNS1IP:0.0.0.0
DNS2IP:0.0.0.0

  1. -----------------------------------------------------------------------------
  2. Parameter: UseTftp
  3. Type: Boolean
  4. Description: Indicate whether TFTP server is used for provisioning
  5. Options: 1 = Use TFTP for provisioning
  6. 0 = TFTP is not used for provisioning

UseTftp:1

  1. -----------------------------------------------------------------------------
  2. Parameter: TftpURL
  3. Type: Alphanumeric string (31 characters max)
  4. Description: IP address or URL of TFTP server to use.
  5. This value is required if the DHCP server will not provide
  6. the TFTP address. You can optionally include the path prefix
  7. to the Tftp file to download. Example: If the TFTP server IP
  8. address is 192.168.2.170 or wwww.cisco.com, and the path to
  9. download the Cisco phone profile is in /IP_phones, then you
  10. can specify the URL as 192.168.2.170/IP_phones or
  11. www.cisco.com/IP_phones.

TftpURL:0

  1. -----------------------------------------------------------------------------
  2. Parameter: CfgInterval
  3. Type: Integer (60 - 4294967295 seconds)
  4. Description: Interval (in seconds) between each configuration update.
  5. When TFTP is used for provisioning, at every such interval
  6. expiration, the box will perform a TFTP get of its
  7. configuration file at the earliest possible time — when the
  8. box is idle). CfgInterval can be set to some random value to
  9. achieve random contact interval from individual phone to the
  10. TFTP server.
  11. Note: If set to less than 60, default is 60 seconds.

CfgInterval:3600

  1. -----------------------------------------------------------------------------
  2. Parameter: EncryptKey
  3. Type: Hexadecimal string (8 Hex digits max)
  4. Description: Key to use to decrypt the configuration profile
  5. Options: *0 = Configuration profile is not encrypted
  6. non-zero = Configuration profile is encrypted with this key,
  7. and the phone will decrypt the profile with this
  8. key.
  9. Default is marked with *.
  10. Note: The cfgfmt.exe program will automatically encrypt the binary
  11. file when this parameter value is non-zero.

EncryptKey:0

  1. -----------------------------------------------------------------------------
  2. Parameter: EncryptKeyEx
  3. Value Type: Hexadecimal string (64 Hex digits max)
  4. Description: Stronger encryption key to use to decrypt the configuration
  5. profile. When this parameter is set to a non-zero value, the
  6. phone will request a profile with the name <phone_id><MAC>.x,
  7. where
  8. <phone_id> = "ld" for Cisco 7905 IP phone
  9. "gk" for Cisco 7912 IP phone
  10. <MAC> = MAC address of the Cisco IP phone
  11. x = extension indicating profile w/strong encryption
  12. If this parameter is set to 0, the phone will operate as if it
  13. only possessed the EncryptKey parameter, i.e. it will request
  14. its profile as <phone_id><MAC> without the "x" extension.
  15. Syntax: <RC4_Key>/MAC
  16. RC4_Key = Hexadecimal string from 1 to 64 hex digits
  17. MAC = (Optional) MAC address of the Cisco IP phone
  18. If this is specified, only the phone with the
  19. specified MAC address will be able to decrypt
  20. the profile.
  21. Options: *0 = EncryptKey parameter value is used.
  22. The phone will request <phone_id><MAC> file and
  23. decrypt it using the EncryptKey parameter value.
  24. non_zero = Configuration profile is encrypted with this
  25. stronger key, and the phone will request and
  26. decrypt the profile with this key.
  27. Default is marked with *.
  28. Note: If this parameter is specified, the cfgfmt.exe (version 2.1a
  29. or later) program will create two profiles. The
  30. <phone_id><MAC>.x profile will be encrypted with EncryptKeyEx
  31. while <phone_id><MAC> profile will be encrypted with
  32. EncryptKey.

  1. EncryptKeyEx:0

  1. -----------------------------------------------------------------------------
  2. Parameter: NPrintf
  3. Type: Extended IP value
  4. Syntax: <HOST_IP>.<HOST_PORT>
  5. Description: For diagnostic use. Use this parameter to specify the IP
  6. address and port number where the phone will send its
  7. debug output information.
  8. The program "prserv.exe", which is included in every software
  9. upgrade package, is need to capture the debug information.
  10. For example, to send message to the host at 192.168.2.170 and
  11. port number 9001, you would run "prserv 9001" on a PC and
  12. specify "192.168.2.170.9001" as the value of this parameter.

NPrintf:0

  1. -----------------------------------------------------------------------------
  2. Parameter: TraceFlags
  3. Type: Bitmap value
  4. Description: For diagnostic use. Use this parameter to turn ON specific
  5. trace features.
  6. Options: Bit Values
  7. ----- --------------------------------------------------------
  8. 0 SIP Messages Log
  9. *0 = Disable
  10. 1 = Enable
  11. 1-7 RESERVED. Must be set to 0.
  12. 8 RTP Statistics Log
  13. *0 = Disable
  14. 1 = Enable
  15. RTP statistics log is in the following format:
  16. Recvchannel number: <call duration in seconds>
  17. <number of recv packets> <number of recv octets>
  18. <number of late packets> <number of lost packets>
  19. <avg network jitter in 1/8 ms>
  20. <counts in speeding up local clock
  21. (adjustment for 10 ms each time)>
  22. <counts in slowing down local clock
  23. (adjustment for 10 ms each time)>
  24. Txchannel number: <call duration in seconds>
  25. <number of transmit packets>
  26. <number of transmit octets>
  27. 9-31 RESERVED. Must be set to 0.

TraceFlags:0x00000000

  1. -----------------------------------------------------------------------------
  2. Parameter: IPDialPlan
  3. Type: Integer (0 - 2)
  4. Description: Allow for detection of IP-like destination address in dial
  5. plan.
  6. Options: 0 = Disable IP dialing detection.
  7. 1 = If two '.' is seen, then the phone assumes that an
  8. IP address is being entered.
  9. 2 = If three '.' is seen, then the phone assumes that an
  10. IP address is being entered.

IPDialPlan:1

  1. -----------------------------------------------------------------------------
  2. Parameter: DialPlan
  3. Type: Alphanumeric string (199 characters max)
  4. Description: Dial plan rules.
  5. Note: No syntax check is performed by the actual implementation.
  6. It is the responsibility of the provisioner to make sure that
  7. the dial_plan is syntatically valid.
  8. Programmable strings of dial plan that allow one to specify:
  9. o special rule — I{timeout} to control default inter-digit
  10. timeout - specifying this rule also has the side effect
  11. of preventing non-matching dial string from being sent out.
  12. o optional send character to use (e.g. '#' or '*')
  13. o how many digits before auto send
  14. o send after timeout at any specified number of digits
  15. (time out can be changed as digits are entered).
  16. in the following:
  17. o . means match any digits
  18. o - means more digits can be entered, this (if needed) must
  19. appear at the end of the individual rule
  20. (i.e. e.g. 1408t5- is legal, but 1408t5-3...
  21. is illegal).
  22. o ># means terminating key to send is #, and termination
  23. can be applied only after matching hits ># (So >*
  24. means terminating char is *, i.e. terminating key
  25. must follow >)
  26. o rules applied in the order of listed (whichever matched
  27. completely first will cause trigger the send).
  28. o tn means timeout is n seconds (note: n is 0-9 and
  29. a-z — which ranges 0 to 26).
  30. o more than one rules are separated by |.
  31. o rn means repeat last pattern n times (note: 1. ># or tn are
  32. modifier, they are not pattern; 2. n is 0-9 and a-z --
  33. which ranges 0 to 26). Use the repeat modifier to specify
  34. more rules in less space.
  35. You can also use the modifier 'S' to sieze the rule matching
  36. (i.e. if a rule matches and the modifier 'S' is seen, all other
  37. rules after that matching rule will not be used for matching).
  38. Examples 1: The set of dial plan rules:
  39. ".t7>#......t4-|911|1t7>#..........t1-|0t4>#.t7-"
  40. or equivalently
  41. ".t7>#r6t4-|911|1t7>#.r9t1-|0t4>#.t7-"
  42. consists of the following rules:
  43. .t7>#......t2- — at least one digit need to be
  44. entered, after that, time out is 7 seconds
  45. before send, and terminating char # can also
  46. be applied after the first digit is entered,
  47. and after 7 digits are entered, time out
  48. change to 2 seconds. * means further digits
  49. can be entered as long as not terminated by
  50. timeout or #.
  51. 911 — send out immediately
  52. 1t7>#..........t1- — at least one digit need to be
  53. entered, after that, time out is 7 seconds
  54. before send, and terminating char # can also
  55. be applied after the first digit is entered,
  56. and after 10 digits are entered, time out
  57. change to 1 second. * means further digits can be
  58. entered as long as not terminated by timeout
  59. or #.
  60. 0t4>#.t7- — after entering 0, if no other digit is
  61. entered, it will timeout and send in 4 seconds,
  62. otherwise, time out change to 7 seconds after
  63. another key is entered. again # is terminating
  64. digit.
  65. Examples 2: The set of dial plan rules:
  66. "911|1>#.r9t3.t5-|0t411t9-"
  67. if 911 entered, it will be sent out immediately.
  68. if 14088713344 is entred, after 3 seconds, it will
  69. be sent out but if another digit is entered (say
  70. 140887133445, the timeout chaned to 5 seconds).
  71. if 0 is entered, after 4 seconds, it will be send out.
  72. if 011 is entered, the time out changed to 9 seconds.

DialPlan:911|1>#t8.r9t2-|0>#t811.rat4-|^1t4>#.-

  1. -----------------------------------------------------------------------------
  2. Parameter: RingOnOffTime
  3. Type: Array of three short integers
  4. Description: Control phone ring characteristic.
  5. Note: Values specified below are recommended for the U.S.

RingOnOffTime:2,4,25

  1. -----------------------------------------------------------------------------
  2. Parameters: DialTone
  3. DialTone2
  4. BusyTone
  5. ReorderTone
  6. RingBackTone
  7. CallWaitTone
  8. Type: Array of short integers
  9. Description: Playback tones
  10. Format: For DialTone, DialTone2, BusyTone, RingBackTone, CallWaitTone
  11. NumOfTone,Freq0,Level0,Freq1,Level1,NumOfCadence,
  12. OnTime0,OffTime0,OnTime1,OffTime1,TotalToneTime
  13. For ReorderTone
  14. SequentialTone,NumOfTone,Freq0,Level0,Freq1,Level1,
  15. Freq2,Level2,NumOfCadence,OnTime0,OffTime0,
  16. OnTime1,OffTime1,OnTime2,OffTime2,NumOfRepeat,
  17. TotalToneTime
  18. Options: - NumOfTone:
  19. Number of frequency components (1 or 2)
  20. For Reorder Tone, value range is 1 to 3.
  21. - Freqx (Hz):
  22. Transformed frequency (-32768 to 32767)
  23. - Levelx (dBm):
  24. Transformed amplitude (-32768 - 32767)
  25. - NumOfCadence:
  26. Number of cadence pairs (0 - 2).
  27. For Reorder Tone, value range is 0 to 3.
  28. To specify a steady tone, set value to 0.
  29. - OnTimex (s):
  30. Length of time tone is ON (0 - 65535)
  31. - OffTimex (s):
  32. Length of time tone is OFF (0 - 65535)
  33. - SequentialTone:
  34. Juxtoposed tones or sequential tones
  35. 0 = Juxtoposed tone, 1 = Sequential tone
  36. - NumOfRepeat:
  37. Number of times (OnTimex, OffTimex) cadence pair is
  38. repeated before proceeding to the (OnTimex, OffTimex).
  39. - TotalToneTime:
  40. The total length of time the tone is played. If set to 0,
  41. tone will play continously until other call events stop
  42. the tone. For DialTone, BusyTone, ReorderTone, and
  43. RingBackTone, the unit is in number of 10 ms. For other
  44. tones, the unit is the number of samples.
  45. Note: 1. If NumOfCadence is set to 0, OnTimex and OffTimex must
  46. be set to 0.
  47. 2. Values specified below are recommended for the U.S.

DialTone:2,31538,814,30831,2032,0,0,0,0,0,0
DialTone2:2,30743,1384,29864,1252,0,0,0,0,0,0
BusyTone:2,30467,1104,28959,1404,1,4000,4000,0,0,0
ReorderTone:0,2,30467,1104,28959,1404,0,0,1,2000,2000,0,0,0,0,0,0
RingBackTone:2,30831,2032,30467,1104,1,16000,32000,0,0,0
CallWaitTone:1,30831,2412,0,0,1,2400,2400,0,0,4800

  1. -----------------------------------------------------------------------------
  2. Parameter: NATIP
  3. Type: IP address
  4. Description: WAN IP address of the attached router/NAT

NATIP:0.0.0.0

  1. -----------------------------------------------------------------------------
  2. Parameter: MediaPort
  3. Type: Integer (1 - 65535)
  4. Description: Base port to receive RTP media

MediaPort:16384

  1. -----------------------------------------------------------------------------
  2. Parameter: TOS
  3. Type: Bitmap value
  4. Description: ToS (Type of Service) bits. This bitmap value specifies the
  5. precedence and delay of Audio and Signaling IP packets.
  6. Options: Bit Values
  7. ----- --------------------------------------------------------
  8. 0-7 ToS Value For Audio Data Packets
  9. Range: 0-255 Default: 184 (0xb8)
  10. 8-15 ToS Value For Signaling Data Packets
  11. Range: 0-255 Default: 96 (0x60)
  12. 16-31 RESERVED

TOS:0x000060b8

  1. -----------------------------------------------------------------------------
  2. Parameter: SigTimer
  3. Type: Bitmap value
  4. Description: Timeout values to start/stop the following signalling events
  5. Options: Bit Values
  6. ----- --------------------------------------------------------
  7. 0-7 CALL WAITING PERIOD
  8. Period between each burst of call waiting tone
  9. Range: 0 - 255
  10. Factor: 0.1 second
  11. Note: 0 defaults to 100 (or 10 sec)
  12. Default: 100 (0x64 = 10 sec)
  13. 8-13 RESERVED. Must be set to 0.
  14. 14-19 RING TIMEOUT
  15. Timeout in ringing the phone after which the incoming
  16. call is rejected
  17. Range: 0 - 63
  18. Factor: 10 seconds
  19. Note: 0 means ring never times out
  20. Default: 6 (60 sec)
  21. 20-25 NO ANSWER TIMEOUT
  22. Time to declare no answer and initiate call forwarding
  23. on no answer
  24. Range: 0 - 63
  25. Factor: 1 second
  26. Default: 20 (0x14 = 20 sec)
  27. 26-27 RESERVED. Must be set to 0.
  28. 28-29 FIRST KEY REPEAT INTERVAL
  29. The minimum time required initially for the Volume or
  30. Navigation key to be pressed before the highlight bar
  31. begins to move automatically.
  32. Range: 0 to 3
  33. Default: 0 (1 second)
  34. 0 = 1 sec 1 = Disable Key Repeat
  35. 2 = 2 sec 3 = 3 sec
  36. 30-31 SUBSEQUENT KEY REPEAT INTERVAL
  37. The minimum time required subsequently for Volume or
  38. Navigation key to be pressed to keep the highlight bar
  39. moving automatically.
  40. Range: 0 to 3
  41. Default: 0 (0.25 second)
  42. 0 = 0.25 sec 1 = 0.5 sec
  43. 2 = 0.75 sec 3 = 1 sec

SigTimer:0x01418064

  1. -----------------------------------------------------------------------------
  2. Parameter: OpFlags
  3. Type: Bitmap value
  4. Description: Turn ON/OFF various operational features
  5. Options: Bit Values
  6. ----- --------------------------------------------------------
  7. 0 TFTP CONFIGURATION FILE NAME
  8. *0 = Do not use internally generated TFTP configuration
  9. file name
  10. 1 = Always use the internally generated TFTP
  11. configuration file name
  12. 1 NETWORK PROBING ON POWER UP
  13. 0 = Probe the static network router on power up
  14. *1 = Do not perform static network router probing at
  15. power up
  16. 2 RESERVED. Must be set to 0.
  17. 3 DHCP OPTION 150
  18. *0 = Ask for DHCP option 150 in DHCP DISCOVERY message
  19. 1 = Do not ask for DHCP option 150 in DHCP DISCOVERY
  20. message (some DHCP server will not respond if
  21. option 150 is requested)
  22. 4 NETWORK OPERATION
  23. *0 = Assume normal operation without VLAN
  24. 1 = Assume operation under VLAN (the VLAN ID is
  25. specified in VLANSetting, see VLANSetting parameter)
  26. Multicast is disabled
  27. 5 VLAN ENCAPSULATION
  28. *0 = Use VLAN IP encapsulation
  29. 1 = Do not use VLAN IP encapsulation, i.e. force
  30. turning OFF VLAN IP encapsulation
  31. 6 Cisco Discovery Protocol (CDP)
  32. *0 = Use CDP discovery
  33. 1 = Do not perform CDP discovery. Multicast is disabled
  34. 7 WEB CONFIGURATION ACCESS
  35. *0 = Allow web configuration
  36. 1 = Do not allow web configuration
  37. 8 TFTP REFRESH ACCESS
  38. *0 = Allow force profile update via http://ip/refresh
  39. 1 = Do not allow http://ip/refresh
  40. 9 REMOTE RESET ACCESS
  41. *0 = Allow reset of the phone via http://ip/reset
  42. 1 = Do not allow reset of the phone via http://ip/reset
  43. 10-14 RESERVED. Must be set to 0.
  44. 15 UDP CHECKSUM GENERATION
  45. *0 = Generate UDP checksum in outgoing UDP packets
  46. 1 = Do not generate UDP checksum in outgoing UDP packets
  47. 16-31 RESERVED. Must be set to 0.

OpFlags:0x00000002

  1. -----------------------------------------------------------------------------
  2. Parameter: VLANSetting
  3. Type: Bitmap value
  4. Description: Control various VLAN settings
  5. Options: Bit Values
  6. ----- --------------------------------------------------------
  7. 0-2 Specify 802.1Q priority for Signalling IP packets
  8. 3-5 Specify 802.1Q priority for Audio Voice IP packets
  9. 6-17 RESERVED. Must be set to 0.
  10. 18-29 Specify 802.1Q VLAN ID
  11. 30-31 RESERVED. Must be set to 0.

VLANSetting:0x0000002b

  1. -----------------------------------------------------------------------------
  2. Parameter: NatServer
  3. Type: Alphanumeric string (47 characters max)
  4. Description: IP address or domain name of a server to which a dummy,
  5. single-byte UDP packet is sent to maintain a NAT during
  6. a session.
  7. Syntax: <NAT_SERVER_IP | FQDN>:port
  8. If port number is not specified, 5060 is assumed.

NatServer:0

  1. -----------------------------------------------------------------------------
  2. Parameter: NatTimer
  3. Type: Bitmap value
  4. Description: This parameter provides control over the transmission interval
  5. and destination server of Keep Alive packets.
  6. Options: Bit Values
  7. ----- --------------------------------------------------------
  8. 0-11 SIP/RTP Keep Alive (KA) period in seconds (0-2047)
  9. Specify the interval in which a dummy packet is sent
  10. out through the specified SIP and RTP ports to keep
  11. the port bindings on the NAT/firewall open
  12. 12-17 RESERVED. Must be set to 0.
  13. 18 SIP KA destination:
  14. 0 = NatServer
  15. 1 = ProxyServer
  16. 19 RESERVED. Must be set to 0.
  17. 20 Enable KA for SIPPort (send to either NatServer or
  18. Proxy)
  19. 21 Enable KA for MediaPort (send to NatServer)
  20. 22 Enable KA for MediaPort + 4 (send to NatServer)
  21. 23-31 RESERVED. Must be set to 0.
  22. Note: 1. If NatServer is not specified (0) or invalid, then the
  23. only available option is to enable SIP KA to Proxy Server.
  24. 2. If KA period is 0, all KA are disabled; but still can
  25. do NATIP mapping.

NatTimer:0

  1. ========================= Caller Preferences ==========================

  1. -----------------------------------------------------------------------------
  2. Parameter: CallForwardNumber
  3. Type: Numeric digit string (31 digits max)
  4. Description: Phone number to forward all calls
  5. Note: Set value to zero (0) to disable this feature.

CallForwardNumber:0

  1. -----------------------------------------------------------------------------
  2. Parameter: VoiceMailNumber
  3. Type: Numeric digit string (31 digits max)
  4. Description: Phone number to access voice mail
  5. Note: Set value to zero (0) to disable this feature.

VoiceMailNumber:9999

  1. -----------------------------------------------------------------------------
  2. Parameter: CallFwdBusyNumber
  3. Type: Numeric digit string (31 digits max)
  4. Description: Phone number to forward busy calls
  5. Note: Set value to zero (0) to disable this feature.

CallFwdBusyNumber:0

  1. -----------------------------------------------------------------------------
  2. Parameter: DisplayName
  3. Type: Alphanumeric string (31 characters max)
  4. Description: Display Name used in outgoing Caller ID
  5. Note: Set value to zero (0) to disable this feature.

DisplayName:Elias Aggelidis

  1. -----------------------------------------------------------------------------
  2. Parameter: ShortName
  3. Type: Alphanumeric string (31 characters max)
  4. Description: Name to be displayed on phone's LCD screen.
  5. Note: Set value to zero (0) to disable this feature and display
  6. the value in "DisplayName", if any, on the LCD screen.

ShortName:eaggel

  1. -----------------------------------------------------------------------------
  2. Parameters: TimeFormat
  3. DateFormat
  4. Type: Alphanumeric string (15 characters max)
  5. Description: Strings to controls the Time and Date format as appear
  6. on the top line of the LCD display.
  7. Special characters are:
  8. h = 12 hour format
  9. H = 24 hour format
  10. i = Minute
  11. I = Minute
  12. a = AM
  13. A = AM
  14. p = PM
  15. P = PM
  16. m = Month in number (1 - 12)
  17. M = Month in abbreviation (Jan - Dec)
  18. d = Day in number (1 - 31)
  19. D = Day in number (1 - 31)
  20. y = Year in 2 digits (00 - 99)
  21. Y = Year in 4 digits (0000 - 9999)
  22. : = Colon blinks every second
  23. 0 = Time or date is not displayed
  24. All other characters are shown as is.
  25. Examples: TimeFormat Sample Display
  26. ---------- --------------
  27. h:ia 2:00p or 11:00a
  28. H:i 14:00
  29. 0 Time is not displayed
  30. DateFormat Sample Display
  31. ---------- --------------
  32. m-d-y 04-20-05
  33. M d, Y Apr 20, 2005
  34. M. D, y Apr. 20, 05
  35. Y/m/d 2005/04/20
  36. Y M. D 2005 Apr. 20
  37. 0 Date is not displayed

TimeFormat:H:i
DateFormat:d-M-Y

  1. -----------------------------------------------------------------------------
  2. Parameter: DoNotDisturb
  3. Type: Boolean
  4. Description: Enable or disable "Do Not Disturb"
  5. Options: 0 = Deactivate "Do Not Disturb" feature
  6. 1 = Activate "Do Not Disturb" feature

DoNotDisturb:0

  1. -----------------------------------------------------------------------------
  2. Parameter: BlockCallerId
  3. Type: Boolean
  4. Description: Enable or disable blocking of outgoing Caller ID
  5. Options: 0 = Do not block outgoing Caller ID
  6. 1 = Block outgoing Caller ID

BlockCallerId:0

  1. -----------------------------------------------------------------------------
  2. Parameter: CallWaiting
  3. Type: Boolean
  4. Description: Enable or disable call waiting for every call
  5. Options: 0 = Disable call waiting for every call
  6. 1 = Enable call waiting for every call

CallWaiting:1

  1. -----------------------------------------------------------------------------
  2. Parameter: AttendedTransfer
  3. Type: Boolean
  4. Description: Enable or disable attended call transfer
  5. Note: If attended call transfer is disabled, the "Trnsfer"
  6. softkey will not be shown on the LCD screen.
  7. Options: 0 = Disable attended call transfer
  8. 1 = Enable attended call transfer

AttendedTransfer:1

  1. -----------------------------------------------------------------------------
  2. Parameter: BlindTransfer
  3. Type: Boolean
  4. Description: Enable or disable blind transfer
  5. Note: If blind transfer is disabled, the "BlndXfr" softkey
  6. will not be shown on the LCD screen.
  7. Options: 0 = Disable blind transfer
  8. 1 = Enable blind transfer

BlindTransfer:1

  1. -----------------------------------------------------------------------------
  2. Parameter: Conference
  3. Type: Boolean
  4. Description: Enable or disable 3-way conference
  5. Note: If 3-way conference is activated, "Confrn" softkey
  6. will not be shown on the LCD screen.
  7. Options: 0 = Deactivate 3-way conference
  8. 1 = Enable 3-way conference

Conference:1

  1. -----------------------------------------------------------------------------
  2. Parameter: BlockAnonymous
  3. Type: Boolean
  4. Description: Enable or disable blocking of anonymous incoming calls
  5. Note: If enabled, anonymous incoming calls will be rejected.
  6. Options: 0 = Deactivate blocking of anonymous incoming call
  7. 1 = Activate blocking of anonymous incoming call

BlockAnonymous:0

  1. -----------------------------------------------------------------------------
  2. Parameter: ForwardToVMDelay
  3. Type: Integer (1 - 4294967295 seconds)
  4. Description: Number of seconds before forwarding a call to the
  5. VoiceMailNumber, if configured.
  6. Note: This setting has no effect if VoiceMailNumber is not
  7. provisioned OR the value is 0 or greater than the ring timeout
  8. value (see SigTimer bits 14-19).

ForwardToVMDelay:20

  1. -----------------------------------------------------------------------------
  2. Parameters: CallPrefGuiShow
  3. CallPrefGuiSet
  4. Type: Bitmap value
  5. Description: CallPrefGuiShow provides the ability to control whether a
  6. call preference option is displayed on the LCD screen.
  7. CallPrefGuiSet provides the ability to control whether a
  8. call preference option can be set by an end user if it is
  9. displayed on the LCD screen.
  10. Options: Bit Values
  11. ----- --------------------------------------------------------
  12. 0 Do Not Disturb (DND)
  13. 1 Call Waiting
  14. 2 Block Caller ID
  15. 3 Call Forward All
  16. 4 RESERVED
  17. 5 RESERVED
  18. 6 Display Name
  19. 7 Time Format
  20. 8 Date Format
  21. 9 Voice Mail
  22. 10 Call Transfer
  23. 11 Blind Transfer
  24. 12 Conference
  25. 13 Short Name
  26. 14-23 RESERVED
  27. 24 Block Anonymous Calls
  28. 25 RESERVED
  29. 26 Forward to Voice Mail Delay
  30. 27 Call Forward On Busy
  31. 28 Show Registration Status Icon
  32. (If set in CallPrefGuiShow, registration status icon
  33. will be displayed on LCD screen. This bit has no
  34. effect in CallPrefGuiSet.)
  35. 29-31 RESERVED

CallPrefGuiShow:0xffffffff
CallPrefGuiSet:0xffffffff

Example gkMAC.cfg file

by angelo m on Sunday 19 of November, 2006 [07:48:54 UTC]
Can anyone post their cfg file for the 7912. I have spent countless hours trying to figure out how to make a proper cfg file for this phone.

Found the info i needed!

by Petter Nikklas on Friday 17 of November, 2006 [21:26:00 UTC]
Configure the Phone Network Settings via DHCP

You can also configure the phone network settings from the Dynamic Host Configuration Protocol (DHCP) server. For SIP phones, make sure that the DHCP server uses Option 66 for the TFTP server. These DHCP options are usually configured from the DHCP server:

   *

     IP Address (DHCP Option 50)
   *

     Subnet Mask (DHCP Option 1)
   *

     Default IP Gateway (DHCP Option 3)
   *

     DNS Server Address (DHCP Option 6)
   *

     TFTP Server (DHCP Option 66)
   *

     Domain Name (DHCP Option 15)

Note: Cisco CallManager uses Option 150 for the TFTP server, while SIP phones expect Option 66 for the TFTP server.

So, using the option 66 insted of 150 it started to ask for a software via tftp :)

7912G

by Petter Nikklas on Friday 17 of November, 2006 [20:05:00 UTC]
I've got a 7912G where the green and the red led is light up all the time, i failed to upgrade it to sip.
Now what? Option 150 seams not to work with the 7912G, any other idéas?

by Dean Ashby on Tuesday 24 of October, 2006 [22:17:39 UTC]

Cisco 7912g with SIP 8.0.1 image doesn't request RingList.xml

by Tyoma Sarukhanov on Friday 18 of August, 2006 [07:55:54 UTC]
Hallo.
We have Cisco 7912g IP-phone with SIP image version 8.0.1. This version supports only one Ringtone - Chirp 1. Other ringtones can from TFTP taken via RingList.xml file (so said in Cisco's Call Manager Guides). But we have no CCM. And the IP-phone doesn't request RingList.xml from our Asterisk server with TFTP.
Can someone say, possible it new ringtones from TFTP server to download or not. If yes, how to do it.
Thanks.

Cisco 7912g with SIP 8.0.1 image doesn't request RingList.xml

by Tyoma Sarukhanov on Friday 18 of August, 2006 [07:54:56 UTC]
Hallo.
We have Cisco 7912g IP-phone with SIP image version 8.0.1. This version supports only one Ringtone - Chirp 1. Other ringtones can from TFTP taken via RingList.xml file (so said in Cisco's Call Manager Guides). But we have no CCM. And the IP-phone doesn't request RingList.xml from our Asterisk server with TFTP.
Can someone say, possible it new ringtones from TFTP server to download or not. If yes, how to do it.
Thanks.

Re: 7905 does not start

by Tony on Monday 17 of July, 2006 [18:56:06 UTC]
This one is for Razametal or anyone else who's having the red and green steady LED's and no display on a 7905/12:

This is usually caused by a part-blown firmware upgrade which failed part way through.

The phone itself appears useless, but it is actually locked in a startup loop, and as Raza correctly identified it's requesting a DHCP address.

In order to solve the issue a bit of work is necessary:

Firstly a DHCP server is required, and a TFTP server.

Setup option 150 in the DHCP scope to point to the IP address of the TFTP server (the phone is looking for a TFTP server address via DHCP option 150 - I won't go into details about how to do this as there's so many different DHCP servers around, but if you're not sure, google it).

Make sure the TFTP server is running, and check your DHCP server logs to ensure the phone is requesting, and receiving a DHCP address.

Personally, I prefer to use Solarwinds' free TFTP server (I'm a windows user) as it has a real-time log window which gives plenty of information about what the phone is actually requestin if you do use this version, ensure you've set it to both transmit and receive files, as by default it will only receive).

Now for what was a bit odd for me - my failed firmware was the version 8.0 SIP firmware, and the phone was apparently looking for a file called CP7912080000SIP060111A.zup <-- Notice the ZUP not ZIP extension! Hmm...I only had a CP7912080000SIP060111A.sbin in my tftp folder and I could find no info on a ZUP file.

Out of sheer desperation I changed the extension of the .SBIN to .ZUP and the TFTP server sent it down to the phone and hey presto it came back to life!!

Sweet.

I hope this helps others - It kept me up to 1.30 am trying to work out what was wrong (I know - sad geek!).

Cheers

Tony

7905 does not start

by razametal on Tuesday 06 of June, 2006 [05:30:35 UTC]
I've one 7905 phone that can not start. I've connected the phone to the power and get blank screen and the two leds (red and gren) in the front are turned on. How can I recover my phone? I'm trying to recover it using one dhcp server connected to the phone with a crossover cable, the phone is requesting one ip address, but I can ping it, after a few seconds, the network inteface is becoming down and the process starts again. Take a look to the log:

Jun 6 00:27:42 localhost kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x00.
Jun 6 00:27:42 localhost kernel: eth0: link up.
Jun 6 00:27:42 localhost kernel: eth0: Setting full-duplex based on negotiated link capability.
Jun 6 00:27:43 localhost kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x21.
Jun 6 00:27:43 localhost kernel: eth0: Setting half-duplex based on negotiated link capability.
Jun 6 00:27:47 localhost dhcpd: DHCPDISCOVER from 00:14:f2:6a:83:58 (SEP0014F26A8358) via eth0
Jun 6 00:27:47 localhost dhcpd: DHCPOFFER on 172.16.1.50 to 00:14:f2:6a:83:58 (SEP0014F26A8358) via eth0
Jun 6 00:27:47 localhost dhcpd: DHCPREQUEST for 172.16.1.50 (172.16.1.1) from 00:14:f2:6a:83:58 (SEP0014F26A8358) via eth0
Jun 6 00:27:47 localhost dhcpd: DHCPACK on 172.16.1.50 to 00:14:f2:6a:83:58 (SEP0014F26A8358) via eth0
Jun 6 00:28:07 localhost kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x00.
Jun 6 00:28:07 localhost kernel: eth0: link down.
Jun 6 00:28:09 localhost kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x00.
Jun 6 00:28:09 localhost kernel: eth0: link up.
Jun 6 00:28:09 localhost kernel: eth0: Setting full-duplex based on negotiated link capability.
Jun 6 00:28:09 localhost kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x21.
Jun 6 00:28:09 localhost kernel: eth0: Setting half-duplex based on negotiated link capability.


Register broken on firmware 8.0.0?

by Luca Corti on Wednesday 17 of May, 2006 [16:29:55 UTC]
Switched from SCCP and Cisco CallManager to SIP with SER. I've tried both 1.3.1 and 8.0.0 firmwares. It seems the phone tries to register as user@domain.com@1.2.3.4 where 1.2.3.4 is the ip address of the SIP proxy. So registration does not succeed. Does this happen to anyone else?

thanks

Please update this page with new information, just login and click on the "Edit" or "Add Comment" button above. Get a free login here: Register Thanks! - support@voip-info.org

Page Changes | Comments

Sponsored by:

Terms of Service Privacy Policy
© 2003-2008 VOIP-Info.org LLC

Powered by bitweaver