OBI110: Disconnect Tone Pattern

[malomyasa]

My OBI110 sometimes suddenly ends calls.
Parameter Line->DisconnectTonePattern = 480-30,620-30;10;(.25+.25)
Can anybody explain me numbers in this string?

[202Owner]

The problem could be anywhere.  Most default OBi settings are fine and should only be changed knowingly.  That particular setting is very likely not your issue.  You can probably read about it in the OBi admin guide.

Ideally, you should ask your VoIP service provider (ITSP) for support.

Otherwise, you will need to explain more about your services (ISP, ITSP) and equipment (phones, ata, router, wiring) and its performance history to aid someone to narrow in on the problem.  And be able to troubleshoot the problem on your end.

It could take much effort only to determine that your OBi might be defective or your phone might be flakey or the cat chewed the cord or the connector is coming undone... it could take much trouble shooting skill.

[malomyasa]

Thank you for answer. But my question is: explain me numbers in "DisconnectTonePattern", please.

[ianobi]

480-30,620-30;10;(.25+.25)

This looks like "Fast Busy Tone":
480Hz mixed with 620Hz both at -30dBm, for a duration of 10seconds. The tones will be on for .25 seconds, then off for .25 seconds.

I'm assuming that we are talking about your PSTN line here. Several conditions can cause false hang-ups. If it is only affecting PSTN calls, then I would disable all of the following:

DetectCPC
DetectPolarityReversal
DetectFarEndLongSilence
DetectDisconnectTone

If both caller and callee hang up after the call, then the call should still disconnect.

If the above solves the problem, then enable each parameter that you think you may need. Personally, I would never enable DetectPolarityReversal or DetectFarEndLongSilence, but this does depend on what country you live in and local PSTN line signals.

[202Owner]

Thank you for answer. But my question is: explain me numbers in "DisconnectTonePattern", please.

Tone patterns are explained in the OBi admin guide on page 163.  The guide is on the website.  Go find it and read it.

[malomyasa]

Thank you very much!

OK.
Then second question: if 10 = "duration of 10seconds", then why my OBI disconnects the line after first beep in busy signal?

PS: If DetectDisconnectTone in disable state, then OBI never disconnects from the line automatically.

[ianobi]

The tone pattern is confusing. I believe the OBi110 will disconnect as soon as it recognises a valid disconnect tone of any duration. Not all countries have the same disconnect tone. For example I live in the UK where the disconnect tone is 400Hz at -30dBm for 3 seconds.

All that is probable not relevant. There are all those other methods of PSTN Disconnect Detection. Your OBi110 may well be seeing a CPC signal from your local telephone exchange. CPC will be a short drop in line voltage to signal that the called party has hung up. In the US this is around 450ms, where I live it can be as low as 90ms.

If you live in the US, then the default settings should be ok for you. If you live anywhere else, then local PSTN signals may be different.

[malomyasa]

I switched off all other detectors in "PSTN Disconnect Detection": DetectCPC, DetectPolarityReversal and DetectFarEndLongSilence. And only if DetectDisconnectTone enabled, then OBI disconnects from the line after first beep in busy signal. If DetectDisconnectTone disabled - never disconnects from line. And my problem exist only if DetectDisconnectTone enabled.

How change duration of detect busy signal?

[ianobi]

It seems that you have done all of the logical testing that can be done! I'm not sure why your OBi110 is so sensitive to the disconnect tone. I cannot test with my OBi110 as the tones are different where I live. Please confirm which country you live in, it might be relevant.

It is hard to imagine that the OBi is receiving a false disconnect tone in the middle of a call. A mix of 480Hz and 620Hz would be hard to simulate with the human voice.

If DetectDisconnectTone disabled - never disconnects from line.

Is this the case even if you hang up?

As DetectDisconnectTone does not seem to working well for you, then maybe you should try disabling it and enabling DetectCPC.

[malomyasa]

It is hard to imagine that the OBi is receiving a false disconnect tone in the middle of a call. A mix of 480Hz and 620Hz would be hard to simulate with the human voice.

I'm sorry that I misled you in my first message.
String "480-30,620-30;10;(.25+.25)" - this is OBI's default parameter - has been used only for example.

In really:
1) OBI110 configured as FXO-gateway for SIP-PBX.
2) OBI's LINE-port is connected to local line of our PBX in office.
3) DisconnectTonePattern = 425-30;10;(.25+.25)
4) PBX in our office can only generate the busy tone to local lines and don't supports CPC or reversing of polarity on local lines.

After some experiments I found: second (30) and third (10) numbers of DisconnectTonePattern may be any and don't affect to detecting busy signal. It was reason of my first question.

[202Owner]

I'm sorry that I misled you in my first message.
String "480-30,620-30;10;(.25+.25)" - this is OBI's default parameter - has been used only for example.

What you said that was misleading is "My OBI110 sometimes suddenly ends calls."

Now it turns out you are quite experienced and are trying to hack the OBi110 into your PBX application, and you are expecting people to waste their time trying to understand your application that you are unwilling to explain in advance of seeking their help.  And you can't be bothered to read the referred admin guide that answers your initial question.  Good luck.

[malomyasa]

1. "My OBI110 sometimes suddenly ends calls" - exactly.
2. Misleading is: "Parameter Line->DisconnectTonePattern = 480-30,620-30;10;(.25+.25)"
3. About what hacks are you saying? FXO-gateway - one of the modes OBI110, implemented by the developers. Why should not I use it?
4. I spent a few days in search of information about the parameter DisconnectTonePattern - to no avail. You have given me the information - where to read. Thanks You. But in the Admin Guide also no information about the parameter DisconnectTonePattern. There is information on how to configure Busy Tone - but it's not the same thing.

And finally - I did not ask me to help. I asked a simple question, expecting to get a simple answer. ianobi gave me an answer. Thanks very much to him.

That's all. Good Luck.

[FabioCarloni]

Hi,
the disconnect tone in Italy is 425 Hz, 0.2s ON + 0,2s OFF.
then
DisconnectTonePattern = 425-30;10;(.2+.2)

Often the calls are cut.

I also tried
425-30;10;5(.2+.2)
425-30;10;1(1/.2+.2,1/.2+.2,1/.2)

the problem still remains!

[azrobert]

The disconnect tone works when the other party hangs up, so it is working correctly.
Why would a disconnect tone of any duration be generated when a call is in session?
I know you said the problem doesn't occur when the disconnect tone is disabled, but it could be another problem.
Are you at the current firmware level on the OBi110?

[FabioCarloni]

The disconnect tone works when the other party hangs up, so it is working correctly.
Why would a disconnect tone of any duration be generated when a call is in session?
I know you said the problem doesn't occur when the disconnect tone is disabled, but it could be another problem.
Are you at the current firmware level on the OBi110?

I know how a tone disconnection. I don't know why the tone is generated during the session. If the disconnect tone is disabled, the problem disappears.
I tried it with 3 different devices obi 110, same problem. I have no problem with Grandstream HT-503 and Cisco SPA3102.

This is the log of the obi

Code Select Expand


2015-05-23 16:30:52 debug 192.168.7.41 kern FXO ONHOOK MONITOR
2015-05-23 16:30:52 debug 192.168.7.41 kern FXO NewTermState:onhook
2015-05-23 16:30:52 debug 192.168.7.41 kern FXO ONHOOK MONITOR
2015-05-23 16:30:52 debug 192.168.7.41 kern call overall status -- peer: 192.168.7.50:10182, local: 192.168.7.41:16810, pkt_tx: 3036, pkt_rx: 3001, bytes_tx: 522192, bytes_rx: 516172, clk_diff: -319 PPM, pkt_in_jb: 9, pkt_ooo: 0, pkt_lost: 0, pkt_late: 0, pkt_loss_rate: 0 %, pkt_drop_rate: 0 %, jb_len: 170 ms, curr_rcvd_jitter: 2 ms, rcvd_digits: 0, underruns: 0, overruns: 0, seq_num_broken: 0, pkt_interp: 67, skew_comp: 0 ms, frm_in_pkt: 2
2015-05-23 16:30:52 debug 192.168.7.41 kern RTP Del Channel
2015-05-23 16:30:52 debug 192.168.7.41 kern FXO tell cc end-call
2015-05-23 16:30:52 debug 192.168.7.41 kern DAA Disc.Tone 0 0
2015-05-23 16:30:52 debug 192.168.7.41 kern DAA Disc.Tone 0 0
2015-05-23 16:29:58 debug 192.168.7.41 kern RTP Del Channel
2015-05-23 16:29:58 debug 192.168.7.41 kern SIP DLG reject: 503
2015-05-23 16:29:58 debug 192.168.7.41 kern FXO make new call
2015-05-23 16:29:51 debug 192.168.7.41 kern FXO ring off
2015-05-23 16:29:51 debug 192.168.7.41 kern RTP Start->c0a80732:10182(80);0;0;0:0:0;0(50)
2015-05-23 16:29:51 debug 192.168.7.41 kern FXO Stop Tone
2015-05-23 16:29:51 debug 192.168.7.41 kern FXO NewTermState:offhook
2015-05-23 16:29:51 debug 192.168.7.41 kern FXO OFFHOOK
2015-05-23 16:29:51 debug 192.168.7.41 kern fxo cp answered
2015-05-23 16:29:51 debug 192.168.7.41 kern RTP DtmfTxMtd:1(1),0
2015-05-23 16:29:49 debug 192.168.7.41 kern DAA CND ,3385800120,,,,
2015-05-23 16:29:49 debug 192.168.7.41 kern DAA CND ,3385800120,,,,
2015-05-23 16:29:49 debug 192.168.7.41 kern ------ caller id (pcm_id: 1) received! ------------
2015-05-23 16:29:48 debug 192.168.7.41 kern FXO NewTermState:ringing
2015-05-23 16:29:48 debug 192.168.7.41 kern Ring On


What is "DAA Disc.Tone 0 0"? Why is it generated?
I tried different codecs, G.729 and G.711, but this is not the solution.

P.S.    OBI 110 Software Version: 1.3.0 (Build: 2872)