Asterisk1.Local
From KnLC
ns34wo <a href="http://ycxiieygijni.com/">ycxiieygijni</a>, [url=http://qztebyuqqweb.com/]qztebyuqqweb[/url], [link=http://rkqzsthwudic.com/]rkqzsthwudic[/link], http://wlfwqpcpbrfw.com/
Contents |
10-30-2008
Updated firmware for all phones.
All got 6.5.18 except mine (it's on the v7 level) it got 7.1.35
All updated fine except the warehouse phone. It developed an odd issue where it would not allow you to call and toll free numbers...It was the only phone affected in this way.
Per Exordium, I downgraded then repatched the firmware - reset the phone to defaults and reprogrammed it. No change. I got it working by enabling the inbound DID for this line. It never had it before but that is what fixed it.
I checked the other phones in the office with no DID and they are working fine.
11-18-2008
Made some changes to the SugarCRM installation.
Added SugarNoteIn Beta for caller id pop-ups in sugar. It works but not automatically yet. I need to make some config changes to the asterisk server itself to strip off the +1 that BW.com adds to all the inbound caller id's.
Working on that part now to see what the rammifications are to that change. My main hitch is that I cannot find whether or not the context= setting in the inbound trunk params will affect the DID settings on the inbound routes.
Will post here when I figure it out.
11-19-2008
Figured it out. I hedged. Instead of trimming both the CallerID and DID - I just trim the CallerID.
Here's the info:
Line in original Asterisk Conf for inbound was: context=from-pstn
Add this to the end of /etc/asterisk/extensions_custom.conf (new section - beware linewraps)
[from-bandwidth-custom]
exten => _+1.,2,Set(CALLERID(num)=${IF($[ "${CALLERID(num):0:2}" = "+1" ]?${CALLERID(num):2}:${CALLERID(num)})} ;removes +1 from CID if it exists
include => from-pstn
Change line asterisk conf to: context=from-bandwidth-custom
Doing it this way trims only in the event that the CallerID begins with +1. So far, everything is working nicely.
The remaining 5 DID's ported today. We are now officially completely converted over to Bandwidth.com.
Finally, I changed all the passwords on the server today. This was necessary to keep everything firmly under our control. I do not want the old company to be able to access our setup (at least without me knowing about it).
11-20-2008
Big day.
Installed Samba and configured for internal remote access and ultimately backup purposes. Since the box is now under our supervision we need to get that rolling. Samba is only listening on the internal nic. No outside access this way. Locked down as best as I can make it.
Also enabled and configured IPTABLES. I have set to simply block certain ranges right now. I haven't tried blocking all and only allowing the pertinant traffic yet. We need the phones working right now. No interruptions. This way I can block the major offenders and deal with the rest as needed for now.
All is working properly.
1-22-2009
Added CRON job to automatically delete all call monitor recordings older than thirty days from the /var/spool/asterisk/monitor/ directory. The managers were using this tool with asterisk and were not deleting the files after they were done training (natch).
Cron runs monthly on the first with the following command:
find /var/spool/asterisk/monitor/ -mtime +30 -exec rm -f {} \;
2-2-2009
Finished up converting the firewalling over to block everything and just allow asterisk traffic. Much better this way. This box needs no external access except asterisk so that is what it gets.
2-4-2009
Finally got an ongoing problem fixed. One of our Grandstream HT-286 ATA's was not working properly. It is connected to our postage and credit card machines. Now VOIP is notorious for not playing well with modems but it was working fine.
After nearly a month and a half it just hit me today that the firmware was a different version than our other ATA's. I swapped one out and it is working again. When I get around to it I will downgrade this ATA back to the earlier version as well.
