Guest

Cisco Unified IP Phone 7900 Series

Cisco IP Phone 7905G/7912G (SIP) Release Notes for Firmware Release 1.2.0

  • Viewing Options

  • PDF (310.8 KB)
  • Feedback
Cisco IP Phone 7905G/7912G (SIP) Release Notes for Firmware Release 1.2.0

Table Of Contents

Cisco IP Phone 7905G/7912G (SIP) Release Notes for Firmware Release 1.2.0

Installing Required Firmware for the Cisco IP Phone

Related Documentation

What's New in this Release

Additional Time Zones Support

D Rule for Displaying Caller ID

Example

Log Information

R Rule for Enhanced Prefix

Examples

Log Information

Advanced Syntax for Dial Plan Rules

G.729 Annex B Support

Selectable Host Target for Forwarded Calls

EncryptKeyEx Parameter

Syntax

Description

Tool Required

Examples

New cfgfmt Tool

Resolved Defects

Known Defects

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


Cisco IP Phone 7905G/7912G (SIP) Release Notes for Firmware Release 1.2.0


These release notes are for use with the Cisco IP Phone models 7905G and 7912G running under the Session Initiation Protocol (SIP) and running software release 1.2.0.

These release notes include the following sections:

Installing Required Firmware for the Cisco IP Phone

Related Documentation

What's New in this Release

Resolved Defects

Known Defects

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Installing Required Firmware for the Cisco IP Phone

Before using a Cisco IP Phone model 7905G or 7912G with SIP, you must install the appropriate firmware on the phone. Refer to the Readme.txt file that is included with the phone software package for more information.

Related Documentation

For more information about Cisco IP Phones, refer to the following publications, which are available at this URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/index.htm

Cisco IP Phone 7905G/7912G User Guide for Cisco CallManager

Cisco IP Phone Models 7905G and 7912G Administrator Guide (SIP)

Regulatory Compliance and Safety Information for the Cisco IP Phone 7900 Series

What's New in this Release

The following sections describe new and enhanced features in this release:

Additional Time Zones Support

D Rule for Displaying Caller ID

R Rule for Enhanced Prefix

Advanced Syntax for Dial Plan Rules

G.729 Annex B Support

Selectable Host Target for Forwarded Calls

EncryptKeyEx Parameter

New cfgfmt Tool

Additional Time Zones Support

The TimeZone parameter has been enhanced to provide support for time zones that are offset by increments of 30 minutes and 45 minutes. This parameter continues to support the integers 0 through 24 for time zones that are offset by 60 minute increments, as shown in Table 1.

Table 1 TimeZone Parameter Values for 60-Minute Offsets 

Value
Meaning

0

GMT

1

GMT + 1

2

GMT + 2

3

GMT + 3

4

GMT + 4

5

GMT + 5

6

GMT + 6

7

GMT + 7

8

GMT + 8

9

GMT + 9

10

GMT + 10

11

GMT + 11

12

GMT + 12

13

GMT - 12

14

GMT - 11

15

GMT - 10

16

GMT - 9

17

GMT - 8

18

GMT - 7

19

GMT - 6

20

GMT - 5

21

GMT - 4

22

GMT - 3

23

GMT - 2

24

GMT - 1


With this release, the TimeZone parameter can also accept the integers -720 through -60 and 60 through 780. These integers specify the time zone offset in minutes from GMT and are used for locations with time zone offsets of 30 minutes and 45 minutes increments.

The formula for calculating the TimeZone parameter value in minutes is:

(offset hours * 60 minutes/hour) + offset minutes = total minutes

For example, for the Darwin time zone of GMT + 9:30, the calculation is:

(9 hours * 60 minutes/hour) + 30 minutes = 570 minutes

Table 2 shows examples of TimeZone parameter values for time zones with offsets of 30 minutes and 45 minutes increments.

Table 2 TimeZone Parameter Values for 30- and 45-Minute Offsets 

Value
Meaning
Location

210

GMT + 3:30

Tehran

270

GMT + 4:30

Kabul

330

GMT + 5:30

Calcutta, Chennai, Mumbai, New Delhi

345

GMT + 5:45

Kathmandu

390

GMT + 6:30

Rangoon

570

GMT + 9:30

Darwin, Adelaide

-210

GMT - 3:30

Newfoundland


D Rule for Displaying Caller ID

The D rule has been added to the DialPlan parameter. This rule lets you specify a called number for which caller ID is always displayed, even if you have blocked caller ID.

The syntax for the D rule is:

Dnnnn

where nnnn is a called number to which caller ID is always displayed. The D rule is checked before the R rule.

The called number nnnn can be specified using negation, subrule matching, and range. For more information, see the "Advanced Syntax for Dial Plan Rules" section.

Example

The following dial plan rule causes caller ID to always be displayed when the called number is 911:

D911

Log Information

The following lines will be written to the prserv log file when the dialed number matches the the number specified for the D rule.


Note The first line will always appear if you do not have caller ID blocked. The second line will appear only if the D rule is specified.


SCC Cmd[0,call_id]:CLIP 
CLIP: num

where:

call_id is 0 for the first leg of a call or 1 for the second leg of a call

num is the telephone number dialed

R Rule for Enhanced Prefix

The R rule has been added to the DialPlan parameter. This rule is for automatically prepending a specified prefix to the dialed string. If more than one R rule matches, the first matched R rule is used.

The syntax for the R rule is:

R[-]nnnn(tttt)


where:

- is one or more dashes (-). The number of dashes is the number digits preceding the prefix that will be removed.

nnnn is the dial string to prepend.

tttt is a trigger string. If the dialed numbers match this string, this match triggers the prepending of a variable-length prefix (as specified by nnnn) to the dial string. The triggered string is not removed from the dial string.

The trigger string tttt can be specified using negation, subrule matching, and range. For more information, see the "Advanced Syntax for Dial Plan Rules" section

Examples

Table 3 shows three examples of the R dial plan rule.

Table 3 R Rule Examples 

Dial Plan Rule
Effect

R1212([2_9]-)

Prepends 1212 to dial strings that have a leading digit of 2 through 9.

R-0033(0[1-9].r7)

Removes the first dialed digit, then prepends 0033 to the dialed string. For example, if the number 0148336134 is dialed, the resulting string becomes 0033148336134.

R----0(0033[1-9].r7)

Removes the first four dialed digits, then prepends 0 to the dialed string. For example, if the number 0033148336134 is dialed, the resulting string becomes 0148336134.


Log Information

The following line will be written to the prserv log file when the dialed string matches the R rule:

Call Prefix prefix+num

where:

prefix is the number that is prepended to the dialed string

num is the telephone number dialed

Advanced Syntax for Dial Plan Rules

You can use the commands shown in Table 4 to specify the called number (nnnn) in the D dial plan rule and the trigger string (tttt) in the R dial plan rule.


Note You can also use these commands with other dial plan rules.


Table 4 Dial Plan Rules Advanced Syntax 

Command Name
Command Format
Description

Negation

^

Match any character except the character immediately following the ^. Can also be used as a negation instruction before the Subrule matching or Range commands.

Subrule matching

(subrule0| subrule1| 
... |subruleN)

Specifies multiple subrules within a dial plan rule. A subrule match is made if the entered digits fit one of the subrules. You can use subrules to reduce the length of a dial plan rule by concatenating subrules with the common rule.

Range

[ ]

Match any single digit in the list. Use an underscore (_) to indicate a range of digits. For example, [135] matches the digits 1, 3, and 5. Similarly, [1_5] matches the digits 1, 2, 3, 4 and 5.

The Range command does not allow pound (#) or asterisk (*).

The Range command does not allow the repeat (r) command.

The Range command does not allow subrule matching. For example, [(1|5)] is not a valid command. Use [15] instead.


Examples

Table 5 shows examples of the dial plan rules advanced syntax.

Table 5 Dial Plan rules Advanced Syntax Examples 

Syntax
Effect

^[1_5]

Match only 0, 6, 7, 8, 9 (do not match 1 through 5)

^(1900|1800|17..)

Match anything other than 1900, 1800 and 17..

(1[23]5|345)

Match 125, 135, and 345

(1^[23]5|^345)

Match 105, 115, 145, 155, 165, 175, 185, 195, 045, 145, 245, 445, 545, 645, 745, 845, and 945


G.729 Annex B Support

The Cisco IP Phone models 7905G and 7912G for SIP indicate G.729 Annex B codec support by using a=fmtp and a=rtpmap attribute in the SDP body of outgoing INVITE requests and 183 and 200 responses to INVITE requests. For the G.729 codec, the value of a=ftmp is 18 and the annexb value is either yes or no. The default for annexb is yes.

Table 6 lists the possible G.729 codec configuration and resulting negotiated codec.

Table 6 G.729 Codec Negotiation Process

TXCodec, RxCodec (G.729)
AudioMode bit 0 or 16 (Silence Suppression)
Remote End Supports Annex B
Negotiated Codec

3

1

No fmtp line or annexb=no

G.729

1

Annexb=yes

G.729 Annex B

0

No fmtp line or annexb=no

G.729

0

Annexb=yes

G.729


The following partial SDP body shows the media m= field and attribute a= field for a phone with G.729 codec and Annex B specified:

m=audio 16384 RTP/AVP 18 101
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=yes

Selectable Host Target for Forwarded Calls

You can now set bit 0 in the ConnectMode parameter to designate the destination of the new INVITE request that results from a forwarded call.

You can set bit 0 to 0 or 1, where:

0=Send the new INVITE request via the SIP proxy server regardless of the destination that is specified in the Contact header of the 302 response. (0 is the default value.)

1=Send the new INVITE request to the destination that is specified in the Contact header of the 302 response.

EncryptKeyEx Parameter

EncryptKeyEx is a new configuration parameter for the Cisco IP Phones models 7905G and 7912G (SIP). This parameter provides a stronger configuration file encryption key than the previously used EncryptKey parameter.

Syntax

The syntax of the EncryptKeyEx parameter is:

EncryptKeyEx:rc4KeyInHex_n[/macInHex_12]

where:

rc4KeyInHex_n is the encryption key, specified as a hexadecimal string of 1 to 64 characters.

/macInHex_12 is an optional extension consisting of a forward slash (/) followed by the six-byte MAC address of the Cisco IP phone to which the configuration file will be downloaded. If you use this option, only the phone with the MAC address that you specify will be able to decrypt the file.

Description

When the EncryptKeyEx parameter is set to 0, the Cisco IP Phone TFTP configuration file name is ldMAC_address (for the Cisco IP Phone 7905G) or gkMAC_address (for the Cisco IP Phone 7912G). MAC_address is the lowercase hexadecimal representation of the phone's MAC address. For example, if the Cisco IP Phone 7905G has a MAC address of 102030405060, the TFTP configuration file name is ld102030405060


Note If the the DHCP bootfile option field specifies a value, that value is used instead of ldMAC_address or gkMAC_address.


When the value of EncryptKeyEx is 0, the value of EncryptKey (if nonzero) is used to encrypt the Cisco IP phone configuration file.

If the EncryptKeyEx parameter is set to value other than 0, the configuration file name is ldMAC_address.x (for the Cisco IP Phone 7905G) or gkMAC_address.x (for the Cisco IP Phone 7912G), and the value of the EncryptKeyEx parameter is used to encrypt the Cisco IP phone profile file.


Note You can configure the EncryptKeyEx parameter by using the Cisco IP Phone web configuration page or by using the TFTP configuration method.


Tool Required

You must use release 2.3 of the cfgfmt tool with the new EncryptKeyEx parameter. This tool is bundled with the Cisco IP Phone models 7905G and 7912G software release 1.2.0 and later. This tool creates two configuration files, one file named ldMAC_address format (for the Cisco IP Phone 7905G) or gkMAC_address (for the Cisco IP Phone 7912G), as the previous release of the cfgfmt tool created, and one with the .x extension.

See the "New cfgfmt Tool" section for information about using the cfgfmt tool with the EncryptKeyEx parameter.

Examples

The following examples use the TFTP configuration method to illustrate how to use the EncryptKeyEx parameter.

Example 1

This example assumes that a Cisco IP Phone 7912G starts with a firmware release earlier than 1.2.0 and that phone needs to upgrade to firmware release 1.2.0 so that it can use the EncryptKeyEx parameter to encrypt its configuration file.

The Cisco 7912G IP phone in this example has a MAC address of 102030405060.

Procedure


Step 1 Create a file called gk102030405060.txt by using the applicable example.txt file provided with the Cisco 7912G IP phone software.

(The example.txt file is called sipexample.txt.)

Step 2 Modify the gk102030405060.txt file with desired parameter values.

The value of the EncryptKey parameter should be 0.

Step 3 Set the value of the EncryptKeyEx parameter to the desired encryption key for gkMAC_address.x.

You can also restrict the EncryptKeyEx value to apply only to the Cisco IP Phone 7912G with a particular MAC address. For example, if the EncryptKeyE value is 231e2a7f10bd7fe, you can specify EncryptKeyEx as:

EncryptKeyEx:231e2a7f10bd7fe/102030405060

With this setting, only the phone with the MAC address 102030405060 will be allowed to use the EncryptKeyEx value specified.

Step 4 Update the upgradecode parameter to instruct the Cisco IP Phone to upgrade to firmware release 1.2.0.

In this example, you would modify this parameter as follows for the Cisco 7912G IP phone:

upgradecode:3,0x601,0x0400,0x0100,0,69,0x030909a,CP7912010200SIP040101.zup

Step 5 Run the cfgfmt tool as follows:

cfgfmt -g -tsip_ptag.dat gk102030405060.txt gk102030405060

This command will generate the following files:

gk102030405060

gk102030405060.x

The file gk102030405060 is unencrypted.


Note Some parameters specified in the sip_ptag.dat file used by the cfgfmt tool are marked as sensitive information. (These parameters include UIPassword, UID, PWD0). These parameters are not included in the resulting ldMAC_address file (for the Cisco IP Phone 7905G) or the gkMAC_address file (for the Cisco IP Phone 7912G) if you specify -g when you run cfgfmt. For more information, see the "New cfgfmt Tool" section.


The file gk102030405060.x is encrypted with EncryptKeyEx value.

Step 6 Place the gk102030405060 and the gk102030405060.x files on the TFTP server that the phone will contact for its configuration files.

When the phone powers up, it will obtain its IP address from the DHCP server. If the DHCP server specifies the TFTP server address, the phone will contact the TFTP server obtained from DHCP because the phone is not preconfigured with a TFTP server address. The boot process is as follows:

1. The phone downloads the configuration file gk102030405060 from the TFTP server.

2. The phone applies parameter values in the file gk102030405060 to its internal configuration while ignoring the EncryptKeyEx parameter (because the older release of the Cisco 7912G IP phone does not yet recognize the EncryptKeyEx parameter).

3. The phone upgrades to the 1.2.0 firmware load.

4. The phone reboots.

5. The phone downloads the configuration file gk102030405060.

6. The phone applies the value of the EncryptKeyEx parameter to its internal configuration.

7. The phone reboots.

8. The phone EncryptKeyEx value is provisioned, so from this point forward the phone will download the gk102030405060.x file at each reboot and each time the value configured in the CfgInterval parameter expires.



Note Although EncryptKeyEx is encrypted in the profile file, which does not contain other sensitive information, Cisco recommends that for absolute security you pre-provision the Cisco IP phone as described in this example for a private network. Alternatively, you should remove the profile file after EncryptKeyEx is provisioned.


Example 2

This example assumes that a Cisco IP Phone 7912G is already deployed (with the EncryptKey value set) with firmware release earlier than 1.2.0 and that the phone needs to upgrade to release 1.2.0 firmware to use EncryptKeyEx to encrypt its configuration file.

To upgrade the phone, follow the same procedure as in Example 1, except set the EncryptKey value to the previously provisioned EncryptKey value (instead of to 0). In this way, the gkMAC_address file will be encrypted with EncryptKey as the phone expects. The phone can then begin using the gkMAC_address.x file encrypted with EncryptKeyEx.

New cfgfmt Tool

You use the cfgfmt tool to generate a Cisco IP Phone configuration file. Release 2.3 of the cfgfmt tool supports a stronger encryption method than the previous release of this tool.

The syntax of the new cfgfmt tool is:

cfgfmt [options] input-text-file output-binary-file

Table 7 describes the cfgfmt tool options.


Note Entering cfgfmt with no options or arguments displays a list and brief description of options for the command.


Table 7 Options for the cfgfmt Tool, Release 2.2 

Option
Description
Usage Notes

-eRc4Passwd

Use the Rc4Passwd specified to encrypt or decrypt the input text file

-E

Do not use the EncryptKey parameter's value in the input text file to encrypt the output binary file

-xRc4Passwd

Use stronger Rc4Passwd specified to encrypt or decrypt the input text file

The RC4Passwd entered must be in hexadecimal format.

This option is used to decrypt .x profile files and useful only for debugging purposes to check the content of a binary profile.

This example

cfgfmt -sip -x0ab52123476231233a3 
ld000102030405.x

means to treat ld00102030405.x as the binary profile file encrypted with the stronger encryption key 0ab52123476231233a3, then decrypt the file and display its textual content

-X

Do not use the EncryptKeyEx parameter's value in the input text file to encrypt the output binary file

-tPtagFile

Specifies an alternate path for the ptag.dat file

-sip

Limit processing to SIP parameters

These options are not used for Cisco IP Phones

-h323

Limit processing to H.323 protocol parameters

-mgcp

Limit to processing MGCP parameters

-sccp

Limit to processing SCCP parameters

-g

Omit sensitive parameters in old profile file

Useful for provisioning the stronger EncryptKeyEx parameter using the old profile file while keeping sensitive information from being available from the old profile file. The ptag.dat file controls sensitive information.


Resolved Defects

Table 8 describes Severity 1, 2, and 3 defects that were resolved in this release.

Table 8 Defects Resolved in this Release 

Identifier
Headline

CSCed81744

MWI does not work with 7905 and Sylantro

CSCed52057

For attended transfer Proxy-Auth does not get escaped

CSCec49960

Call Waiting Issues occur when Re-INVITE for HOLD fails

CSCec32309

SIP: Increase the length of USER value in FROM and TO headers

CSCec34888

SIP: Change 4XX response from RING TIMEOUT expiration on 7905 & 7912

CSCec04474

SIP: Increase the length of NONCE value in Auth header to 128

CSCec72447

Incorrect RTP statistics header names

CSCec32078

SDP o= field sess. & version cannot be longer than 10 digits

CSCed84083

Treat 180 with SDP response like a 183


Known Defects

Table 9 describes Severity 1, 2, and 3 defects in this release.

If you have an account with Cisco.com, you can use the Bug Toolkit to find defects of any severity for any release.

To access the Bug Toolkit, perform either of these actions:

Go to this URL: http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

Log in to Cisco.com, click Technical Support, then click Tools & Utilities, then click Software Bug Toolkit under Troubleshooting Tools

Table 9 Open Defects in this Release 

Identifier
Headline and Bug Toolkit Link

CSCeb73369

Simultaneous Hold/UnHold does not work with 7912G/7905G SIP IP phones

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeb73369


Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco TAC Website

The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

http://www.cisco.com/tac/caseopen

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

http://www.cisco.com/go/marketplace/

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html