Our facility uses a well-entrenched NEC DSX key telephone system. The system supports up to 32 VoIP extensions in addition to a few dozen analog and key handsets. I have successfully deployed 18 VoIP extensions using three SPA8000 units with great success. This was required because part of our campus is reachable only by fiber-optic network. We have no copper connectivity to this structure.
I recently purchased a Cisco VG224 unit, expecting to be able to integrate it into the DSX and move all the analog-over-VoIP extensions into one gateway rather than three SPA8000 units.
The VG224 requires usernames for the dial-peer authentication to be a minimum of 4 characters.
The DSX system uses the extension number as the username. Only 3-digit extensions are allowed.
The DSX does not allow the username to be configured in any way, it is always the 3-digit extension number.
The VG224 does not allow 3-digit usernames.
Is there anything I can do on the VG to work around the 4-character minimum username?
For clarity the command I'm issuing is show below, with the system's response to the command:
VG224-01(config-dial-peer)#authentication username 291 password 291291 realm 192.168.75.24
Username MUST be atleast 4 characters
The VG224 is running IOS 15.1(4)M7 [vg224-i6k9s-mz.151-4.M7.bin].
The NEC DSX-80 system is fully up to date with their latest code, version 3.47 GA.
I'm not calling this a bug, but it certainly is a significant mistake in the code as far as I'm concerned.
Thanks in advance.
It appears the sunset date for new service attachment on the VG224 is already past, April 23, 2016.
It's extremely unfortunate that I have essentially no option other than to attempt to return the device to the vendor when the issue seems to be very clearly an error in the device code. I suppose this is a risk taken when purchasing equipment without a service contract. However, even in the case of SmartNet coverage, I highly doubt Cisco would write a new firmware image for this outdated, albeit very expensive, device.
Just a bit of additional information, in the case this may help close the loop or assist somebody else. Here is how the Cisco SPA8000 ATA is configured, per NEC's documentation, to work with my 3rd party key system (NEC DSX-80).
Again, I was able to adapt this information and configured some Cisco 7912 IP handsets and they work very well on the DSX system, using the SIP based firmware on the handset and a simple TFTP server on the LAN for the phones to grab their config files from.
None of this really matters, other than to show clear examples of two other devices (Cisco 7912 handset and Cisco SPA8000 ATA) which happily allow 3-char usernames to be configured for SIP authentication.
SPA8000 example config shown below:
|The Cisco SPA8000 and PAP2T ATAs have been tested on the DSX. Use System Software Version 3.2 or higher.
Unlike the DSX IP Keyset, the Cisco SAP8000 and PAP2T ATAs require some basic setup programming to make them work correctly on the DSX. If you don't understand the following options, refer to the Cisco documentation for additional instruction.
To have access to these options, you must log onto the ATA as admin and run in the advanced mode.