This will usually happen if you either
1) Have not set disconnect supervision
2) Have telephone company lines that do not support disconnect supervision
3) Both
The easiest quick fix is to reboot the PBX.
The long term fix is to set disconnect supervision on the PBX for all of the lines and make sure that the lines form the phone company are set to provide disconnect supervision.
The exact way to set it up on the PBX varies by PBX.
Exactly, a transfer is what usually causes this. when you transfer an incoming call to an external number, that uses both the incoming call's line and the outgoing cal's line. (2 lines). Since you don't hang up the call when you transfer, you rely on some signal from the phone company to know when those two parties are done talking. This is called "disconnect supervision." Usually, as a human, when you hear the dialtone, you know to hang up. Your PBX can't "hear" a dial tone and relies on a signal from the phone company to "hang up" the line.
If both of your lines are stuck as used, that signal has never come, or was not interpreted.
The short term easiest fix is to reboot the PBX. But to prevent it from happening again, you either need to ban internal-to-external transfers or configure disconnect supervision.
×
Follow this instructions to reset the Administrator password.
Press Feature 985 and dial 9 even though it is not listed as an option.
The display will show Pswd: dial 73738767793
The display will show Reset pswd? Press YES.
You should now be able to enter the default password.
2 digit extensions use 120000
3 digit extensions use 1020000
4 digit extensions use 10020000
541 views
Usually answered in minutes!
To give for information:
Basically, someone tried to do transfer a call but transfer it to our other line. Now I can't connect to both. I just want to 'flush' those line so we can use them back
×