Fresh install of 1.6-12 is dropping calls on ring

[agidi1]

Dear Gurus

I just provisioned a box with 1.6-12 with 8 FXO lines.

This box is dropping incoming calls. The line rings, the ext rings, the call gets dropped.
I have recording enabled, and I can "listen" to the calls drop.

Any ideas? suggestions? all appreciated

Is there a safe update for this install?

thanks, best regards.

 

[jgutierrez]

I might think that you have busy detention issues.
Edit /etc/asterisk/chan_dahdi.conf
And uncomment busydetect, busycount, leave busycount on 8 instead of 3.
Then execute from console: asterisk -rx "module reload"

 

[agidi1]

Mr Gutierrez, I appreciate your input.

In no way questioning your knowledge, just bouncing ideas around.

Why would busydetect? on incoming calls?

I have enabled them, i will increase the count as per your suggestion.

It was my understanding the busy detect works for hanging lines after a call is ended, and did not play a role on incoming calls.

thanks

 

[jgutierrez]

Busydetect, analizes busy patterns during a call, that means inbound/outbound, it just doesn't do it when hangup, because if so, asterisk would know that the call was hangup, so there would be no point on checking busy patterns if it was already hangup.

http://www.voip-info.org/wiki/view/Aste ... apata.conf
Check the information for busydetect

 

[agidi1]

Mr Gutierrez

I've yum updated elastix, and enabled busy detect, to 8 rings.

I have been watching FOP and CLI, and calling the PBX in question.

Interesting.. I can see the line ring, and count 4 rings on my side, then the CLI drops the call, but It keeps ringing on my side, about a second later, it starts ringing the exts again as if it got a new call.

it does not actually hang up the line, just stops ringing the exts with CLI showing


-- Called 101
-- Called 102
-- Called 103
-- Called 104
-- Called 105
-- SIP/104-08aa4ee8 is ringing
-- SIP/101-08a94e98 is ringing
-- SIP/103-08aa38c0 is ringing
-- SIP/102-08a8fe50 is ringing
-- SIP/105-08aad830 is ringing
-- Starting simple switch on 'DAHDI/4-1'
== Spawn extension (macro-dial, s, 7) exited non-zero on 'DAHDI/2-1' in macro 'dial'
== Spawn extension (ext-group, 600, 13) exited non-zero on 'DAHDI/2-1'
-- Executing [h@macro-dial:1] Macro("DAHDI/2-1", "hangupcall") in new stack
-- Executing [s@macro-hangupcall:1] GotoIf("DAHDI/2-1", "1?noautomon") in new stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] NoOp("DAHDI/2-1", "TOUCH_MONITOR_OUTPUT=") in new stack
-- Executing [s@macro-hangupcall:4] GotoIf("DAHDI/2-1", "1?noautomon2") in new stack
-- Goto (macro-hangupcall,s,6)
-- Executing [s@macro-hangupcall:6] NoOp("DAHDI/2-1", "MONITOR_FILENAME=") in new stack
-- Executing [s@macro-hangupcall:7] GotoIf("DAHDI/2-1", "1?theend") in new stack
-- Goto (macro-hangupcall,s,9)
-- Executing [s@macro-hangupcall:9] Hangup("DAHDI/2-1", "") in new stack
== Spawn extension (macro-hangupcall, s, 9) exited non-zero on 'DAHDI/2-1' in macro 'hangupcall'
== Spawn extension (macro-dial, h, 1) exited non-zero on 'DAHDI/2-1'
-- Hungup 'DAHDI/2-1'
== MixMonitor close filestream
== End MixMonitor Recording DAHDI/2-1
-- Executing [s@from-pstn:1] Set("DAHDI/4-1", "__FROM_DID=s") in new stack
-- Executing [s@from-pstn:2] Gosub("DAHDI/4-1", "app-blacklist-check|s|1") in new stack
-- Executing [s@app-blacklist-check:1] LookupBlacklist("DAHDI/4-1", "") in new stack


To get things more fun.

This server crashed last week due to a power outage.
Got new HD and re installed the distro, form the same CD. same hardware nothing got touched
The previous install did not do this.

Any takers on the ides?
more hints?
all appreciated.

 

[jgutierrez]

Hmmm... this is very odd.
Another weird thing that I can see from your logs is that when a call arrives, it gets hangup and then comes in through another line... On you example it comes in through DAHDI/4, then on DAHDI/2, and then on DAHDI/4... And I assume that on that momment, there was just a single inbound call.
Once I have had one customer, that had a similiar issue, and it was related to his analog provider that was meesing around with all lines.

So why dont you just connect your lines into several analog phones and try the same test? Leave it ring a couple times to see if it gets the same behaviour or not.