Table of Content

Table of Contents

1 Report Summary 2 System 2.1 Cisco ER Groups In Cluster 2.2 Cisco ER Group Settings 2.3 Telephony Settings 2.4 Server Settings 2.5 License Manager 2.6 Mail Alert Configurations 3 ERL 3.1 Onsite Alert Settings 3.2 Pager Alert Configurations 3.3 Conventional ERL 4 Phone Tracking 4.1 SNMP Settings 4.2 Schedule 4.3 Cisco Unified Communications Manager 4.4 LAN Switch Details 5 ERL Membership 5.1 Switchports 5.2 IP Subnets 5.3 Unlocated Phones 5.4 Manually Configured Phones 5.5 Synthetic Phones 6 User Management 6.1 User 6.2 Role 6.3 User Group 7 Reports 7.1 Call History 7.2 ERL Audit Trail


1 Report Summary

Cisco Emergency Responder (Cisco ER) helps you manage emergency calls in your telephony network so that you can respond to these calls effectively and so that you can comply with local ordinances concerning the handling of emergency calls. In North America, these local ordinances are called "enhanced 911," or E911. Other countries and locales might have similar ordinances.

Because emergency call ordinances can differ from location to location within a country, region, state, or even metropolitan area, Cisco ER includes the flexibility you need to fit your emergency call configuration to specific local requirements.

To track phones, Cisco ER queries Cisco Unified Communications Manager for a list of phones registered with the cluster. Then, Cisco ER queries the switches on the network (the ones you have identified to Cisco ER) to determine the port to which the phones are connected. Cisco ER does this tracking at regular intervals during the day so that it can identify when a phone moves.

Cisco ER can send emergency calls to the correct PSAP based on port and phone location.

Optionally, you can have an SMTP email server in your network or with a service provider. You can configure Cisco ER to send email to your onsite alert (security) personnel to notify them of emergency calls. If the server is set up as an email-based paging service, the personnel are paged.

Finally, you need a gateway with a PRI or CAMA link to the service provider's network so that Cisco ER can route emergency calls to the local public safety answering point (PSAP).

This configuration report contains the configuration objects for the Cisco Emergency Responder (Cisco ER) cluster.

Report Summary
Report date6/10/2010 3:41:52 PM
Report generated forCustomer
DescriptionAs-Built Documentation for project
CER version8.0.1.20000(3)
CER IP10.5.1.79
Report Tool version8.0d / 06092010
Report Tool LicenseDemo
Visual styleBlu Light.css
Report Contentcustom.content
Template HTMLCERreportTemplate.htm
Template WordBars_Phones_Green_Blue.doc

2 System

This section describes system settings of Cisco Emergency Responder.

This section contains the following chapters:

2.1 Cisco ER Groups In Cluster

Cisco Emergency Responder (Cisco ER) groups form a Cisco ER cluster.

A Cisco ER server group consists of up to two Cisco ER servers, a primary and a standby, or backup, server. This redundancy helps ensure that Cisco ER remains available in case one server becomes disabled. Consider placing the two servers in a group in separate physical locations not separated by a WAN link so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption.

Deploy Cisco Emergency Responder (Cisco ER) in your network as a pair of redundant servers. One server is designated as the Publisher server and the other as the Subscriber server. Each Cisco ER Publisher server and Subscriber server make up a Cisco ER Server Group. Configuration data for the server groups is stored in a database on the Publisher. This data is replicated to the Subscriber.

A Cisco ER cluster is a set of Cisco ER server groups that share data to provide correct emergency call handling capabilities. Cisco ER cluster information is stored in a central location in the cluster called the cluster database. A Cisco ER server group is considered part of a cluster when the group points to the same cluster database as the other server groups in that cluster.

A Cisco ER server group consists of up to two Cisco ER servers, a primary and a standby, or backup, server. This redundancy helps ensure that Cisco ER remains available in case one server becomes disabled. Consider placing the two servers in a group in separate physical locations not separated by a WAN link so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption.

The following Cisco ER Server Groups are present in the cluster:

< Not Available >

2.2 Cisco ER Group Settings

A Cisco ER server group consists of up to two Cisco ER servers, a primary and a standby, or backup, server. This redundancy helps ensure that Cisco ER remains available in case one server becomes disabled.

The following settings are configured for the a Cisco Emergency Responder (Cisco ER) server groups:

Cisco ER Group Settings
Cisco ER Group NameCERServerGroup
Peer TCP Port17001
Heart beat Count3
Heart beat Interval (in sec) 30
Active Call Time out (in min)180
SMTP Mail Server10.5.1.22
Source Mail IDmailID
System Administrator Mail IDS.mailID
Calling Party Modificationdisable
SysLogdisable
Syslog Server
Notesno notes
Dynamic Tracking of Switch IP Address
Security end user web interface languageCanadianFrench
Limit Concurrent Sessions
Max. number of concurrent sessions12

2.3 Telephony Settings

The Telephony Settings page defines telephone numbers and telephony ports used by the Cisco ER group.

Telephony Settings
Route Point for Primary Cisco ER Server911
Route Point for Standby Cisco ER Server912
PSAP Callback Route Point Pattern913XXXXXXXXXX
ELIN Digit Strip Pattern913
UDP Port Begin32000
Inter Cisco ER Group Route Pattern
IP Type of service ( 00-FF )0xb8
Onsite Alert Prompt Repeat Count 2
Use IP Address from call signaling
Intrado Route Pattern Settings

2.4 Server Settings

Cisco ER servers are inserted in the Cisco ER group when the Cisco ER services are started

Different levels of privilege exist for each application. For the Cisco Unified Communications Manager Administration application, two levels of privilege exist: read privilege and update privilege.

Server
ServerInfo
Publisher
Server Settings
Server NamePublisher
Host Namecer8
Debug Package List
CER_DATABASE
CCER_REMOTEUPDATE
CER_PHONETRACKINGENGINE
CER_ONSITEALERT
CER_CALLENGINE
CER_SYSADMIN
CER_TELEPHONY
CER_AGGREGATOR
CER_GROUP
CER_CLUSTER
Trace Package List
CER_DATABASE
CCER_REMOTEUPDATE
CER_PHONETRACKINGENGINE
CER_ONSITEALERT
CER_CALLENGINE
CER_SYSADMIN
CER_TELEPHONY
CER_AGGREGATOR
CER_GROUP
CER_CLUSTER

2.5 License Manager

Cisco ER requires server and user licenses.

You must purchase a separate server license for each Cisco ER server in a server group. Cisco generates the server license based on the MAC Address on the server. You must use the MAC Address of the ethernet card on the publisher server to generate a server license for the Publisher. Order two server licenses for each server in a Cisco ER group: one server license for the primary (Publisher) server and a separate server license for the secondary (Subscriber) server. You cannot share a server license between the Publisher server and the Subscriber server.

You must purchase a separate user license for each Cisco ER group. User licenses can be shared between Publisher and Subscriber servers within each Cisco ER group. This includes both implicit 100-user licenses that are provided by the primary and secondary server license. You cannot share Cisco ER user licenses between different Cisco ER groups in a Cisco ER cluster, or between different Cisco ER clusters.

The following licenses are present:

< Not Available >

2.6 Mail Alert Configurations

The Email Alert Settings page is used to specify the parameters under which Cisco ER will send email alerts. The checkbox to the right of each parameter is used to enable (check) or disable (uncheck) email alerts for that parameter. Check the Include event viewer contents in mail checkbox if you want to include the details from the event viewer in the email message.

Different levels of privilege exist for each application. For the Cisco Unified Communications Manager Administration application, two levels of privilege exist: read privilege and update privilege.

Email Alert Settings
Settings
Discovery Parameters Settings
EventGet MailInclude event viewer contents in mail
Discovery Engine Registration Failed
Discovery Engine goes out of connection
For unreachable devices during discovery
Emergency Call Routing Parameters Settings
EventGet MailInclude event viewer contents in mail
Call information
Call routing session ended due to problems
Re-Routing of call
Routing failure
Route Point status (In service/Out of service)
Cluster Parameters Settings
EventGet MailInclude event viewer contents in mail
Cluster DB Failure
Intra Cluster Failure
Misc parameters
EventGet MailInclude event viewer contents in mail
Subscriber becomes active
Publisher comes back online
Not able to get the JTAPI Provider
Available user licenses get exhausted
during phone tracking
Switch Port location change reporting
Suppress IP Communicator/
Unified Personal Communicator
location change reporting

3 ERL

This section describes system settings of Emergency Responder Locations (ERLs).

The Emergency Responder Locations (ERL) is an area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Cisco ER, you assign switch ports and phones to ERLs, and ERL definitions include Automatic location information (ALI) data.

Automatic location information (ALI) ties an ELIN to a location and is used to route emergency calls from that ELIN to the correct local PSAP, and is presented to the PSAP to help the PSAP locate the emergency caller. In Cisco ER, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.

Emergency location identification number (ELIN) is a phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call.

The Public safety answering point (PSAP) is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.


This section contains the following sub chapters:

3.1 Onsite Alert Settings

Onsite Alert Settings contain information about your onsite alert personnel. When you configure ERLs, you assign these personnel to them. Cisco ER will alert the assigned personnel when an emergency call is made within the zone.

The following Onsite Alert Settings are configured:

Onsite Alert Settings
Onsite Alert IDOnsite Alert NameOnsite Alert NumberOnsite Alert Email AddressOnsite Alert Pager Address
11223344@66.com 

3.2 Pager Alert Configurations

Use the Pager Alert Configurations page to limit the size of system-wide pager messages by selecting the fields that are sent to the pager and by editing the labels for those fields.

You can limit the size of the pager message that is sent by selecting the following fields and editing the labels are associated with those fields: Extension, ERL, Location, Time, Server.

Pager Alert Settings
 TitleAs it appears on the pager
EXTENSIONExtension
ERLZone/ERL
LOCATIONLocation
TIMETime of Call
SERVERServer

3.3 Conventional ERL

Use the Conventional ERL Data page to define the emergency response locations (ERLs) for your company. An ERL might be a whole building (if it is small), the floor of a building, or an area on a floor. Each community can have different laws concerning the size of an ERL, so consult your local ordinances and with your service provider before deciding on your ERLs. The ERLs you create will be used by emergency response teams to locate the emergency, so the ERL should be small enough that these teams can locate the caller within a reasonable time.

You must configure the Default ERL before configuring any other ERLs. The default ERL is the system-defined ERL that will be used to route calls if no other ERL configuration is found.

Conventional ERL
ERL NameERL Information
Default
ALI Data
ELIN
ELIN
Onsite Alert
Onsite Alert
ERL Address
House Number11
House Number Suffix22
Street Name33
Prefix Directionald
Street SuffixCT
Post Directionals
Community Namezz
Statevs
Main NPA445
Main Telephone No66
Class Of ServiceCoin 1W out
Type of ServiceNon-Pub
Exchangeasdf
Customer Nameas
Order Number113
Extract Date092310
County ID78
Company ID77
Zip Code80
Zip Code Extension12
Customer Code13
Comments14
Longitude15
Latitude16
Elevation17
TAR Code18
Location19
Reserved20
ze
ALI Data
ELIN
ELIN112--445
66--77
Onsite Alert
Onsite Alert11
ERL Address
House Number44
House Number Suffix
Street Name55
Prefix Directional
Street Suffix
Post Directional
Community Namea
Stated
Main NPA
Main Telephone No
Class Of ServiceCentrex
Type of ServiceFX outside 911 area
Exchange
Customer Name55
Order Number
Extract Date092310
County ID
Company ID44
Zip Code
Zip Code Extension
Customer Code44
Comments
Longitude
Latitude
Elevation
TAR Code
Location
Reserved

4 Phone Tracking

Cisco Emergency Responder (Cisco ER) uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Cisco ER must use the Content Addressable Memory (CAM) table on the switch to track phones. Using the CAM table is less efficient than using CDP.

If some of the phones on your network do not use CDP, Cisco ER tracks them using the CAM table.

To track phones successfully, Cisco Emergency Responder (Cisco ER) must periodically contact switches to obtain port and device information.

Cisco ER updates network information using two processes:

The Public safety answering point (PSAP) is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.


This section contains the following chapters:

4.1 SNMP Settings

Cisco Emergency Responder (Cisco ER) uses SNMP to obtain information about the ports on a switch. Cisco ER must obtain this port information so that you can assign the ports to ERLs, and so that Cisco ER can identify phones that are attached to the ports and update their ERL assignments.

Cisco ER only reads SNMP information, it does not write changes to the switch configuration, so you only have to configure the SNMP read community strings.

Obtain the read community strings from all of the switches you will define in Cisco ER. If you use different strings for different sets of switches, see if you can define an IP address pattern for these sets. For example, if you use the same string for all switches that begin with 10.1, and another string for switches that begin with 10.2, you can use the patterns 10.1.*.* and 10.2.*.*.

When you configure the SNMP strings for your switches, you must also configure the SNMP strings for your Cisco Unified Communications Manager servers. Cisco ER must be able to make SNMP queries of all Cisco Unified Communications Manager servers in the cluster that it supports.

If your Cisco Emergency Responder servers, Cisco Unified Communications Manager servers, and Cisco IP Phones are located in a different subnet than your switches, you must either configure both the subnets for the servers and phones as well as the subnet for the switches or use *.*.*.*.

SNMP Settings
IP Address/Host NameTimeout (in seconds)Maximum Retry AttemptsRead Community
10.5.1.2245*

4.2 Schedule

To track phones successfully, Cisco Emergency Responder (Cisco ER) must periodically contact switches to obtain port and device information. Cisco ER updates network information using two processes:

Phone Tracking: A periodic comparison of the phones registered with Cisco Unified Communications Manager to the location information obtained from the switches. If a phone moves, Cisco ER updates the phone's ERL. Phones that cannot be located are classified as unlocated phones

Note: If you do not configure a switch port phone update schedule, the default schedule will run at midnight.

Switch-Port and Phone Update: The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Switch-Port and Phone Update Schedule
SunMonTueWedThuFriSatHourMinute
0000

4.3 Cisco Unified Communications Manager

Use the Cisco Unified Communications Manager Clusters page to identify the Cisco Unified Communications Manager clusters whose emergency calls this Cisco Emergency Responder (Cisco ER) group will handle. Only assign a Cisco Unified Communications Manager cluster to a single Cisco ER group. Cisco ER gets the list of phones registered with these Cisco Unified Communications Manager servers and tracks the movements of these phones.

Cisco Unified Communications Manager
NameDetails
CUCM_8
Cisco Unified Communications Manager Cluster
Cisco Unified Communications ManagerCUCM_8
CTI ManagerCTI_Manager
BackUp CTI Manager 1CTI_1
BackUp CTI Manager 2CTI_2
Telephony Port Begin Address44
Number of Telephony Ports55
Secure Connection Parameters
Enable Secure Connection
TFTP Server IP Address10.5.1.22
TFTP Server Port69
Backup TFTP Server IP Address10.5.1.23
CAPF Server IP Address10.5.1.24
CAPF Server Port3804
Instance ID for PublisherP_ID
Secure Authentication String for Publishersome
AXL Settings
AXL Usernameadmin
AXL Port Number8443

4.4 LAN Switch Details

You must tell Cisco Emergency Responder (Cisco ER) which switches to manage. Cisco ER tracks port changes, including changes to the devices connected to those ports, and can recognize which ports have phones connected to them. Identify all switches that might have phones attached to them, essentially all edge switches.

The following LAN switches are defined:

LAN Switch Details
Switch Host Name / IP AddressDescriptionEnable CAM based Phone TrackingUse port description as port location
10.5.1.223description

5 ERL Membership

In Cisco ER, you assign switch ports and phones to ERLs, and ERL definitions include Automatic location information (ALI) data. The Emergency response location (ERL) defines an area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area

To track phones, Cisco ER queries Cisco Unified Communications Manager for a list of phones registered with the cluster. Then, Cisco ER queries the switches on the network (the ones you have identified to Cisco ER) to determine the port to which the phones are connected. Cisco ER does this tracking at regular intervals during the day so that it can identify when a phone moves.

This section contains the following chapters:

5.1 Switchports

Use the Switch Port Details page to assign switch ports to Emergency Responder Locations (ERLs). This assignment allows Cisco Emergency Responder (Cisco ER) to assign the correct ERL to phones that connect to the network through the configured ports.

After the network administrator adds switches to the Cisco Emergency Responder (Cisco ER) configuration, and runs the switch-port and phone update process, you can assign the switch ports to emergency response locations (ERLs). When you assign a port to an ERL, make sure that you assign the ERL based on the location of the device attached to the port, not the location of the port itself.

< No records found >

5.2 IP Subnets

IP Subnet configurations are used to automatically assign phones to Emergency Responder Locations (ERLs). You need to manually define an IP Subnet if any of these conditions apply:

Cisco Emergency Responder (Cisco ER) cannot automatically track the type of phone, for example, if the phone is wireless.

Use the CiscoWorks IP Telephony Environment Monitor (ITEM) 2.0 to monitor the health of your Cisco ER system. You create subnets, configure test ERLs and associate them to the subnet, and configure synthetic phones to belong to the test ERLs.

The following IP Subnets are configured:

IP Subnets
Subnet IDSubnet MaskERL NameLocation
10.5.1.2210.5.1.23zesy

5.3 Unlocated Phones

Use the Unlocated Phones page to identify phones that are registered with Cisco Unified Communications Manager, but which Cisco Emergency Responder (Cisco ER) cannot locate. This can happen for several reasons:

Because Cisco ER cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Cisco ER from locating these phones on your network. If you cannot resolve the problems by defining switches in Cisco ER, or by moving phones to supported switch ports, you might have to manually assign a phone to an ERL.

The following unlocated phones have been found by CER:

< No records found >

5.4 Manually Configured Phones

The following manual phones and associated ERL are defined. You need to manually define a phone if any of these conditions apply:

For manually defined phones, Cisco ER cannot automatically locate and update ERL information. You should regularly review manual phone configurations to ensure they are correct.

The following manual phones are defined:

Manually Configured Phones
Line NumberERL NameIP AddressMAC AddressLocationPhone TypeVersion
0011ze10.5.1.234010101010101syncisco 794011

5.5 Synthetic Phones

You must configure synthetic phones in the subnet for testing ERL configurations. You can use the CiscoWorks IP Telephony Environment Monitor 2.0 (ITEM) in conjunction with Cisco ER's test ERLs.

For synthetic phones, Cisco ER cannot automatically locate and update ERL information. You should regularly review synthetic phone configurations to ensure they are correct.

The following synthetic phones are defined:

< No records found >

6 User Management

The following chapters contain the configuration of users, roles and user groups. Cisco ER uses a role based user management mechanism.

You can add additional users. Once the additional users are added, you assign them to user groups. The new user then inherits the roles that were defined for that user group.

6.1 User

On installation, the system creates one default user, CERAdministrator. The CERAdministrator has access to all system administration screens except the Platform Administration and Disaster Recovery System screens. By default, the CERAdministrator user is assigned to the CER System Administrator, CER Serviceability, CER Admin Utility, and CER User user groups and has access to the resources defined for the CER System Admin, CER Serviceability, CER Admin Utility, and CER User roles.

Note: The default CERAdministrator user cannot be deleted.

You can add additional users. Once the additional users are added, you assign them to user groups. The new user then inherits the roles that were defined for that user group

The following users are defined:

User
NameStandard UserGroupsRoles
adminCER Admin Utility
CER Serviceability
CER System Administrator
CER User
CER Admin Utility
CER Serviceability
CER System Admin
CER User

6.2 Role

Roles define privileges which allow functionality within the application. Roles are assigned to user groups which are assigned to users.

Four default roles are created during installation and are listed here. They are:

You can only modify information for roles that you create. After you create additional roles, they will also be listed along with the default roles.

The following roles are defined:

Role
NameDetails
CER System Admin
Details
DescriptionAll System Configurations
Standard Role
Resource Permissions
Resource PermissionsALI Formatting Tool
Add Subscriber
Application User
CER Groups in Cluster
Call History
Call Manager Details
Device Snmp Settings
ERL
ERL Audit Trail
ERL Debug Tool
ERL Migration
File Management Utility
Functional role
IP Subnet
Intrado ERL
Intrado VUI Settings
LAN Switches
License Management
Mail Alert Configurations
Manually Configured Phones
Off-Premises ERL
OnsiteContact
PS ALI Convert
PS ALI Export
Pager Alert Configurations
Purge
Run Tracking
Server
Server Group
Switch Port
Synthetic Phone
Telephony
Tracking Schedule
Unlocated Phones
User Group
CER ERL Admin
Details
DescriptionERL Configurations
Standard Role
Resource Permissions
Resource PermissionsERL
IP Subnet
Manually Configured Phones
OnsiteContact
Switch Port
Synthetic Phone
Unlocated Phones
CER Network Admin
Details
DescriptionNetwork Configurations
Standard Role
Resource Permissions
Resource PermissionsCall Manager Details
Device Snmp Settings
LAN Switches
Run Tracking
Tracking Schedule
CER Serviceability
Details
DescriptionServiceability Pages
Standard Role
Resource Permissions
Resource PermissionsAll Logs
CPU & Memory Usage
Control Centre
Disk Usage
Event Viewer
MIB2 system group configuration
Processes
SNMP V1/V2c configuration
SNMP v3 configuration
CER Admin Utility
Details
DescriptionAdmin utility Pages
Standard Role
Resource Permissions
Resource PermissionsChange CCM Version
Cluster DB Host setting
CER User
Details
DescriptionSecurity User Pages
Standard Role
Resource Permissions
Resource PermissionsPhone Search
User Call History
Web Alert

6.3 User Group

Cisco ER 2.0 uses a role-based user management mechanism. When you create a user group, you assign roles and add users to the group. Multiple roles can be assigned to a single group. The users in the group will have access to all the resources defined by the roles assigned to the group.

Six default user groups are created during installation and are listed here. They are:

The following user groups are defined:

User Group
NameDescriptionStandard Group
CER System AdministratorER Administrator for all system configurations
CER ERL AdministratorER Administrator for ERL configurations
CER Network AdministratorER Administrator for network configurations
CER ServiceabilityER Serviceability user for serviceability pages
CER Admin UtilityER Admin utility user for admin utility pages
CER UserER security user who attends to emergency calls

7 Reports

The following chapters contain additional reports.

7.1 Call History

The Call History page lists the history of emergency calls made from your network. Cisco Emergency Responder (Cisco ER) maintains the most recent 10,000 call history records. There is no restriction on when these calls were placed.

System administrator, ERL administrator, network administrator, or user authority have access to this page.

< No records found >

7.2 ERL Audit Trail

The audit trail lists for an ERL when, and by whom an ERL was created or changed.

System administrator, ERL administrator, or network administrator authority can view the audit trail.

ERL Audit Trail
ERL NameDetails
Default
Details
ERL TypeConventional ERL
Modified BySYSTEM
Modified TimeSeptember 3, 2010 6:42:04 AM PDT
Modification DetailsAdded new ERL
Default
Details
ERL TypeConventional ERL
Modified Byadmin
Modified TimeSeptember 23, 2010 6:09:03 PM PDT
Modification DetailsUpdated House Number
Updated House Number Suffix
Updated Street Name
Updated Prefix Directional field
Updated Street Suffix
Updated Post Directional field
Updated Main NPA
Updated Customer Name
Updated Class of Service
Updated Type of Service
Updated Exchange field
Updated Main Telephone No
Updated Order No
Updated Company ID
Updated Customer Code
Updated Comments
Updated Longitude
Updated Latitude
Updated Elevation
Updated Community Name
Updated State
Updated County ID
Updated ZIP Code
Updated ZIP Code Extension
Updated TAR Code
Updated Location
Updated Reserved Attribute for Database Service Providers
ze
Details
ERL TypeConventional ERL
Modified Byadmin
Modified TimeSeptember 23, 2010 6:10:00 PM PDT
Modification DetailsAdded new ERL

Table of Contents [Hide TOC]