|
|
Joined: Feb 2005
Posts: 194
Member
|
OP
Member
Joined: Feb 2005
Posts: 194 |
I mentioned once before that I didn't trust PCDBA F17 and I lost three days fighting it...it wasn't my system or programming, rather it was the F17 causing the problems.
To prove to myself what was happening, I programmed two cabinets with the K17 firmware loaded using the phone and downloaded the data to two laptops running PCDBA F17.
I set the bottom row of buttons for 816 ~ 821, set some T1 DID translation tables, and directory swapped port 124 with 148. Both systems worked as expected.
I download the data to PCDBA and the buttons showed 824 ~ 829, all the translations tables were blank, and port 30 was mapped to ext. 124 and port 80 was mapped to ext. 148. When I uploaded it back into the cabinets without changing anything, it messed up what I programmed in by hand.
Found out this afternoon this was a known issue with F17 and was told to use the new L18 firmware and PCDBA L18.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
Forums84
Topics94,284
Posts638,772
Members49,765
|
Most Online5,661 May 23rd, 2018
|
|
|
|
|