| Summary: | ASTERISK-01873: tdm fxo does not sense broken pstn line (no battery) | ||
| Reporter: | radamson (radamson) | Labels: | |
| Date Opened: | 2004-06-23 09:51:08 | Date Closed: | 2004-09-25 02:40:24 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | If a pstn line is disconnected (or broken), * happily sends calls to the line. Disconnecting the rj11 and placing a call produces the equivalent. RH9, CVS-HEAD-06/17/04 and all previous since release of the tdm-fxo card. ****** ADDITIONAL INFORMATION ****** Extensions.conf entry: exten => _77.,1,Dial,Zap/1/${EXTEN:2} exten => _77.,2,Congestion CLI output: -- Executing Dial("SIP/3000-2f79", "Zap/1/4") in new stack -- Called 1/4 and the call stays there forever. No indication the call didn't go through, just silence. | ||
| Comments: | By: Mark Spencer (markster) 2004-06-23 14:01:50 There is no such thing as a state for an FXO line which says "I'm not connected" in the RBS world. On the X100P we simulated the situation by considering the port to be in alarm, but that's not appropritate on a multiport card -- and we received a great deal of flak for that behavior from many TDM traditionalists. The "correct" behavior is not to consider whether the line has battery before sending the call, so I am told. | ||