|
|
|
|
Joined: Jun 2012
Posts: 8
Member
|
|
Member
Joined: Jun 2012
Posts: 8 |
Hello,
I have an issue when assigning any DID to a specific FXLDS port. I've assigned the DID to other ports without an issue, but when I assign the same DID number to port 136, I get a busy signal. I've checked the station programming and it seems correct unless I'm missing something. I'm also able to call the extension internally without an issue. There are other LDS ports on the system that I've noticed have been labeled "DID will not ring" and "BAD PORT". I'm assuming they're labeled "BAD PORT" because of the DID issue.
Is this something that can be fixed without replacing the LDS board?
|
|
|
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.
|
|
|
|
Joined: Jun 2012
Posts: 8
Member
|
|
Member
Joined: Jun 2012
Posts: 8 |
After further testing, I found that it's the directory (extension) number that the system doesn't like for some reason. Everything works except the DID assignment for that specific number.
|
|
|
|
Forums84
Topics94,518
Posts639,984
Members49,850
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
|
|
