So I upgraded the Dahdi drivers from 2.3.0 to 2.4.1.2 and Asterisk from 1.4.35 to 1.4.41.
The first problem was that our intercom system started to give a fast busy when the page was over with. I had fixed this by changing the signaling for that port to fxo_gs, even though fxo_ks worked fine on the previous version(s).
Second issue is that our “Door Phone” now only partially works. Normally someone pushes the door speaker, it rings to the two receptionist phones and they put in a code and it opens the door lock.
For a long while it worked about 90% of the time. Now it works 0.1% of the time. It seems as if dialing the ** now just causes a single beep through the door speaker and then hangs up without disengaging the lock. Some times they can’t even hit more than a single * before it hangs up. I have tried tweaking the options.
Anyone know why upgrading would break these that already worked?
For the intercom;
context=from-internal
group=2
;echocancel=yes
signalling = fxo_gs
hanguponpolarityswitch=yes
channel => 60
Hangup polarity switch didn’t make any difference. The intercom itself says that it needs the Disconnect Supervisor, which was working previously as stated. It’s a simple setup where the actual intercom is at extension 255, and I created just a Dial at 8888 to dial 255, wait for a bit, dial 0, wait, 0 and then the intercom beeps through (yeah, I know, it’s kind of retarded, but that’s the way the boss wanted it… accidental company wide pages are fun.)
exten => 8888,1,Dial(Local/255@ext-local,,D(wwwwwww0w0))
exten => 8888,n,Hangup
;;;;;;[255]
signalling=fxo_gs
pickupgroup=
mailbox=255@device
immediate=no
echotraining=800
echocancelwhenbridged=no
echocancel=no
context=from-internal
callprogress=no
callgroup=
callerid=device <255>
busydetect=yes
busycount=6
accountcode=
channel=>60I tried callprogress=yes as well, with no luck.
For the Door Phone
context=from-doorbell
group=3
;echocancel=yes
;toneduration=300
signalling = fxs_ks
channel => 65[from-doorbell]
immediate=yes
exten => s,1,Answer()
exten => s,n,Set(CALLERID(name)="Doorbell")
exten => s,n,Set(CALLERID(num)="Doorbell")
exten => s,n,SIPAddHeader(Alert-Info: info=<Bellcore-dr2>)
exten => s,n,Dial(SIP/100&SIP/101,20)
exten => s,n,Macro(hangupcall,)
;exten => s,n,Hangup()As you can see, I was testing various hangup methods. Still nothing worked. I haven’t tested it since I just added the immediate=yes. Also not sure how I can make this one dahdi channel use pulse dials instead, since there is a 3 through pulse the system says it’ll use.
Any help would be very much appreciated! This looks like a code regression somewhere, I’m just not sure where. I was about to downgrade Dahdi again, but unfortunately since I (after it was already broken) had updated to a newer CentOS kernel, and now older versions of Dahdi (even 2.4.0) won’t compile.
jfergus.