AH64Armament
Vendor
A bit of the back history on this. In 2007, we installed a Mitel 3300 ICP (v8 or 9 at the time) in a new hospital. We also deployed 50 or so Spectralink i640 handsets on Wi-Fi. The AP's we used at the time were Cisco 1231's attached to HP ProCurve switches. All parts of this were deployed by us. The Spectralink i640's were replaced in 2013 by 8030's in SIP mode. We had to change the programming from 5020 emulation to Generic SIP.
This upgrade also included creating a file SIP_xxxx.cfg where xxxx = ext#. sip_allusers.cfg, and slnk_cfg.cfg files - these files are on the TFTP server on the 3300.
Late 2015, we started discussions about replacing the Cisco AP's from the 1231's to Aruba AP's. We are finally at the point of deploying them.
So as to limit the customer's down-time, we're turning up the Aruba controller at my office, along with a handset for testing.
With the existing SSID and using the SVP server, the phone comes up all the way.
We added a new SSID for the 5g radios only and to eliminate the SVP server. I cannot get the phone to boot all the way.
I've figured out that the phone will do the following in somewhat of this sequence...
1. power on.
2. register with the AP
3. obtain IP address
4. observe the slnk_cfg.cfg file and reference pd14csi.bin, pd14odsi.bin, pd14shsi.bin, pd14udsi.bin - note that these files were also loaded to the phone via the HAT tool manually.
5. observes the sip_7900.cfg file - I'm assuming it's referencing this since I assigned the phone to use ext 7900 via the HAT tool.
6. the sip_7900.cfg file references the PROXYn server in the sip_allusers.cfg file.
The sip_allusers.cfg file tells it the phone system and various common features.
sometime between 5 and 6, the phone shows "Registering" for a short while, followed by "1 of 1 lines Unregistered"
I've opened a case with Spectralink support. They have told me to go back and read the documentation... it's a fairly simple operation. After a bit of discussion, he realized that I did read the documentation and they need to resolve this with me, not on my own. I'm waiting on them to respond with the case as they're escalating this to another level as the 8030 is nearing end of life.
While waiting, I've gone back to the guides and repeated all my process - with the same results.
Any help would be appreciated.
I can send the files to anyone that would like to review them.
Thanks,
Mark
This upgrade also included creating a file SIP_xxxx.cfg where xxxx = ext#. sip_allusers.cfg, and slnk_cfg.cfg files - these files are on the TFTP server on the 3300.
Late 2015, we started discussions about replacing the Cisco AP's from the 1231's to Aruba AP's. We are finally at the point of deploying them.
So as to limit the customer's down-time, we're turning up the Aruba controller at my office, along with a handset for testing.
With the existing SSID and using the SVP server, the phone comes up all the way.
We added a new SSID for the 5g radios only and to eliminate the SVP server. I cannot get the phone to boot all the way.
I've figured out that the phone will do the following in somewhat of this sequence...
1. power on.
2. register with the AP
3. obtain IP address
4. observe the slnk_cfg.cfg file and reference pd14csi.bin, pd14odsi.bin, pd14shsi.bin, pd14udsi.bin - note that these files were also loaded to the phone via the HAT tool manually.
5. observes the sip_7900.cfg file - I'm assuming it's referencing this since I assigned the phone to use ext 7900 via the HAT tool.
6. the sip_7900.cfg file references the PROXYn server in the sip_allusers.cfg file.
The sip_allusers.cfg file tells it the phone system and various common features.
sometime between 5 and 6, the phone shows "Registering" for a short while, followed by "1 of 1 lines Unregistered"
I've opened a case with Spectralink support. They have told me to go back and read the documentation... it's a fairly simple operation. After a bit of discussion, he realized that I did read the documentation and they need to resolve this with me, not on my own. I'm waiting on them to respond with the case as they're escalating this to another level as the 8030 is nearing end of life.
While waiting, I've gone back to the guides and repeated all my process - with the same results.
Any help would be appreciated.
I can send the files to anyone that would like to review them.
Thanks,
Mark
