Sip 1 1 4

Firmware Version 9.4(2)SR3 for Cisco Unified IP Phone Models 7942G and 7962G

1. Sip 1 1 4 Riddle
2. Sip 1 1 4 3 8

The 9.4(2)SR3 firmware image within the installation program supports the Session Initiation Protocol (SIP) for the following Cisco Unified IP Phones:

1.3 Schedules Input Program (SIP) SIP is a proprietary software program provided by GSA to assist contract holders with uploading their electronic catalog to GSA Advantage. 1.4 Vendor Support Center (VSC) The VSC supports GSA contract holders that use SIP to upload their data.

1. Filename, size PyQt5sip-12.8.1-cp37-cp37m-manylinux1x8664.whl (283.4 kB) File type Wheel Python version cp37.
2. The 9.4(2)SR3 firmware image within the installation program supports the Session Initiation Protocol (SIP) for the following Cisco Unified IP Phones: Cisco Unified IP Phone 7942G; Cisco Unified IP Phone 7962G; This firmware version is supported on Cisco Unified CallManager Release 5.1.

• Cisco Unified IP Phone 7942G
• Cisco Unified IP Phone 7962G

This firmware version is supported on Cisco Unified CallManager Release 5.1(1b) and later.

Release Notes

For a list of resolved and known problems with any firmware release, view the Release Notes (in English) for your firmware at the following URL:
http://www.cisco.com/en/US/products/hw/phones/ps379/prod_release_notes_list.html

For all phone documentation, click the following URL:
http://www.cisco.com/en/US/products/hw/phones/ps379/tsd_products_support_series_home.html

Image Authentication Support

Cisco provides image authentication with its various IP phone protocols. Image authentication allows the phone to detect if the image has been tampered with before it is programmed into the phone. If the image fails the authentication process then the phone will reject the image. Image authentication occurs through signed files. All Cisco 7942G and 7962G IP Phone loads are signed and can only be upgraded or downgraded to other signed releases.

The 9.4(2)SR3 firmware uses signed (authenticated) files. This step improves IP phone security on the Cisco Unified IP Phone 7942G and 7962G.

Installing the Firmware Load

Before using the Cisco Unified IP Phone 7942G or 7962G with Cisco Unified CallManager release 5.1(1b) or later, you must install the latest firmware on all Cisco Unified CallManager servers in the cluster.

Note: If you have a Cisco Unified CallManager on a Release earlier than 5.1(1b), do NOT install this firmware. You must first upgrade your Cisco Unified CallManager to one of the compatible releases listed in Table 1.

Table 1: Compatible Cisco Call Manager Release for 7942G and 7962G

Cisco Unified CallManager Voice Software download page: http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml

The 9.4(2)SR3 installation programs for the Cisco Unified IP Phone 7942G and 7962G are listed below.

Note: For the Cisco Unified IP phones 7942G and 7962G, you should not add the .loads extension to the firmware version name in the Cisco Unified CallManager database.

Note:To improve software integrity protection, new public keys are used to sign cop files for Cisco Unified Communications Manager Release 10.0.1 and later. These cop files have 'k3' in their name. To install a k3 cop file on a pre-10.0.1 Cisco Unified Communications Manager, consult theREADMEfor the ciscocm.version3-keys.cop.sgn to determine if this additional cop file must first be installed on your specific Cisco Unified Communications Manager version. If these keys are not present and are required, you will see the error 'The selected file is not valid' when you try to install the software package.

Cisco Unified IP Phone Model 7942G/7962G Installation Instructions

Perform the following procedure:

1. Click the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser
2. Download the file that is listed in Table 2 to your hard drive.

Table 2: Cisco Unified IP Phone Models 7942G/7962G Firmware Loads

When using Cisco Unified CallManager Release 5.0 or later

For Cisco Unified CallManager 5.0 (and later), you must do all software installations and upgrades by using the Software Upgrades menu options. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified CallManager with Cisco Unified CallManager 5.0.

• Using your web browser, login to the Cisco IPT Platform Administration web page
• Under the Software Upgrades menu, select Install/Upgrade.
• Fill in the appropriate values in the Software Location section for the file you downloaded above, and click Next.
• In the Available Software drop-down box, select the file you downloaded above, and click Next.
• Enusre that the downloaded file has the same MD5 hash value as listed in Table 2.
• Click Next.
• In the Warning box, verify you have selected the correct firmware, then click Install.
• Ensure that you received a Success message.

Cisco Unified IP Phone Model 7942G/7962G Alternate Firmware format

The Cisco Unified IP Phone Model 7942G/7962G Firmware version 9.4(2)SR3 is also supplied in a zip file, as an alternative in case a Cisco Unified CallManager is not available to load the installer program. The name of this file is: cmterm-7942_7962-sip.9-4-2SR3-1.zip.

After unzipping the firmware files, they should be manually copied to the appropriate directory on the TFTP server.

Copyright© 2011 Cisco Systems, Inc. All Rights Reserved

The Standard Interchange Protocol is a proprietary standard for communication between library computer systems and self-service circulation terminals. Although owned and controlled by 3M, the protocol is published and is widely used by other vendors.^[1] Version 2.0 of the protocol, known as 'SIP2', is a de facto standard for library self-service applications.^[2]

History[edit]

SIP version 1.0 was published by 3M in 1993.^[3] The first version of the protocol supported basic check in and check out operations, but had minimal support for more advanced operations. Version 2.0 of the protocol was published in 2006 and added support for flexible, more user-friendly notifications, and for the automated processing of payments for late fees.

SIP2 was widely adopted by library automation vendors, including ODILO, Bibliotheca, Nedap, Checkpoint, Envisionware, FE Technologies and open sourceintegrated library system software such as Koha and Evergreen. The standard was the basis for the NISO Circulation Interchange Protocol (NCIP) standard which is eventually intended to replace it.

Description[edit]

SIP is a simple protocol in which requests to perform operations are sent over a connection, and responses are sent in return. The protocol explicitly does not define how a connection between the two devices is established; it is limited to specifying the format of the messages sent over the connection.^[4] There are no 'trial' transactions; each operation will be attempted immediately and will either be permitted or not.^[5]

The protocol specifies messages to check books in and out, to manage fee payments, to request holds and renewals, and to carry out the other basic circulation operations of a library.^[6]

Encryption and Authentication[edit]

SIP has no built in encryption, so steps need to be taken to send the connection through some sort of encrypted tunnel. Two common methods are to use either stunnel^[7] or SSH^[8] to add a layer of encryption and/or an extra level of authentication.

References[edit]

Sip 1 1 4 Riddle

1. ^Tedd, L. A. (2007). 'Library management systems'. In Bowman, J. H. (ed.). British librarianship and information work 2001-2005. Ashgate Publishing Group. pp. 431–453. hdl:2160/679. ISBN978-0-7546-4778-2.
2. ^'NISO Circulation Interchange Protocol Implementation Group'. What is NCIP?. NCIP Implementation Group. Retrieved 11 November 2010.
3. ^'3M will Lead Open Development on next release of Standard Interchange Protocol'. Press release. 3M. Retrieved 7 December 2010.
4. ^'3M Standard Interchange Protocol'. 3M. April 11, 2006. p. 15. Retrieved 7 December 2010.
5. ^Vinod, Chachra (August 2003). 'Experiences in Implementing the VTLS RFID Solution in a Multi-vendor Environment'(PDF). World Library and Information Congress: 69th IFLA General Conference.
6. ^'3M Standard Interchange Protocol'. 3M. April 11, 2006. pp. 3–13. Retrieved 7 December 2010.
7. ^'Encrypting SIP2 Traffic with Koha'. jsn4lib. 2012-02-06. Retrieved 2018-10-30.
8. ^Scott), dan@coffeecode.net (Dan (2010-04-16). 'Setting up secure self-check connections using SIP tunneled through SSH'. Coffee|Code: Dan Scott's blog. Retrieved 2018-10-30.

Sip 1 1 4 3 8