SpectraLink NetLink i640, NetLink e340 Technical Bulletin
Technical Bulletin CS-04-07
Cisco SCCP Registration File Format Requirements
Date:
Software Versions:
July 13, 2004
All
Hardware Revisions: SCCP Protocol
Originator:
Approvers:
Matt Jerger
Wayne McAllister
Gary Bliss
Product Type: NetLink Wireless Telephones
Access Level: General
Status: Approved
Revision: A
Problem
The NetLink i640 or e340 Wireless Telephone does not register to the designated
primary CallManager (in the Device Pool list). Additionally the handset may display the
error “Registration Rejection: Device Mismatch” upon registration.
Description
SpectraLink Wireless Telephones require .cnf formatted configuration files, not .cnf.xml
files. These files instruct the handset as to which CallManager to register to and the
specific phone emulation type. If they are not found the CallManager will download a
default file called SEPDEFAULT.cnf which could be configured to point to the
inappropriate CallManager (or configure it as the wrong phone emulation type) by
default.
Examples of file formats:
(note that each handset has its own specific file (MAC address specific))
What we require: SEP00907A01C291.CNF
What we do not support: SEP00907A01C291.CNF.XML
Resolution
Ensure that the CallManager service “BuildCNFType” is configured for “Build All”
otherwise the CallManager does not provide the SpectraLink Wireless Telephones with
the proper configuration file format during the TFTP process during registration.
THE INFORMATION PROVIDED IN THE SPECTRALINK TECHNICAL BULLETIN IS PROVIDED "AS IS" WITHOUT W ARRANTY OF ANY KIND. NO
OBLIGATION OR LIABILITY WILL ARISE OUT OF, SPECTRALINK RENDERING TECHNICAL OR OTHER ADVICE OR SERVICE IN CONNECTION
SpectraLink Corporation • 5755 Central Avenue • Boulder, Colorado 80301 • 303.440.5330
HEREWITH.
Field Advisory Bulletin CS-04-07
Overview of Registration Process
1. Obtain IP information via Dynamic Host Configuration Protocol (DHCP) if they
have not been statically configured.
a. DHCP broadcast message exchanged from handset to determine DHCP
server.
b. DHCP message exchanged from handset to determine other network
information such as option 150 which details the TFTP server.
2. Obtain the configuration file.
a. Handset should receive via TFTP’d configuration file from TFTP server
specified in option 150 of the DHCP message.
b. Handset expects the SEPxxx.cnf file telling the handset which
CallManager to register to.
3. Handset Registration
a. Handset should register with the specific CallManager information
received in the .cnf file.
THE INFORMATION PROVIDED IN THE SPECTRALINK TECHNICAL BULLETIN IS PROVIDED "AS IS" WITHOUT W ARRANTY OF ANY KIND. NO
OBLIGATION OR LIABILITY WILL ARISE OUT OF, SPECTRALINK RENDERING TECHNICAL OR OTHER ADVICE OR SERVICE IN CONNECTION
HEREWITH.
Loading...