FOOD FOR THOUGHT Continued Support for 13-12.x?

[kyle95wm]

I have a question best suited for @wardmundy.

Will the installers for 13-12 continue to be supported? I'm in a unique situation that prevents me from moving to 13-13 due to incompatibilities.

The last thing I would want is to wake up one day and find that the 13-12 installer broke. For reference, I'm using this tutorial as my install template

 

[wardmundy]

We no longer are maintaining 13-12, but you're more than welcome to use it as long as it works. No plans to keep updating it, however. What is it about 13-13 that is problematic??

 

[phonebuff]

@wardmundy

RentPBX is not supporting 13-13, I am told because it is 64b only.

 

[kyle95wm]

@wardmundy

I understand your stand on no longer maintaining the installer for 13-12.

Below are the following concerns or problems I've encountered during my short time with 13-13.

Does your SMTP Gmail relay guide work with 13-13? I've noticed that VM to email doesn't work, from when I've tried to use it. Maybe that issue was fixed at some point?

I use a special blacklist check context (code below), and because of 13-13's massive difference with blacklisting, the code I use is not compatible and makes Asterisk crash:

[app-blacklist-check]
exten => s,1(check),Set(CDR(did)=${FROM_DID})
;Original first line of context with line number changed
exten => s,n,GotoIf($["${BLACKLIST()}"="1"]?blacklisted)
;Blacklist Caller ID names found in custom Asterisk database BLISTNAME if used
exten => s,n,GotoIf($["${DB_EXISTS(BLISTNAME/${TOUPPER(${CALLERID(name)})})}"="1"]?blacklisted)
;Blacklist Caller ID names of single letter followed by 9 or more digits
exten => s,n,Set(regx=^[A-Z][0-9]{9}[0-9]* *$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(name)})} = 1]?blacklisted)
;Blacklist numbers where first digit of 7 digit local number is 0 or 1
exten => s,n,Set(regx=^[+]?1?[0-9]{3}[01][0-9]{6}$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(num)})} = 1]?blacklisted)
;Blacklist numbers where first digit of area code is 0 or 1
exten => s,n,Set(regx=^[+]?1?[01][0-9]{9}$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(num)})} = 1]?blacklisted)
;Blacklist numbers where first three digits of 7 digit local number are 555
exten => s,n,Set(regx=^[+]?1?[0-9]{3}555[0-9]{4}$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(num)})} = 1]?blacklisted)
;Blacklist numbers that start with 1 but are longer than 11 digits total
exten => s,n,Set(regx=^[+]?1[0-9]{11}[0-9]*$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(num)})} = 1]?blacklisted)
;Blacklist numbers of less than 7 digits in length
exten => s,n,GotoIf($[${LEN(${CALLERID(num)})} < 7]?blacklisted)
;Blacklist numbers of 8 digits in length
exten => s,n,GotoIf($[${LEN(${CALLERID(num)})} = 8]?blacklisted)
;Next line is from the original blacklist context
exten => s,n,Set(CALLED_BLACKLIST=1)
;Special CallerID name lookup; should not really be here but works
exten => s,n,ExecIf($["${DB_EXISTS(cidname/${CALLERID(num)})}"!="1″]?Return())
exten => s,n,Set(CALLERID(name)=${DB(cidname/${CALLERID(num)})})
exten => s,n,Set(__SKIPCIDLOOKUP=1)
;More original blacklist context
exten => s,n,Return()
exten => s,n(blacklisted),Answer
;Prepend *BL* to Caller ID name of blacklisted numbers so they can be distinguished in CDR
exten => s,n,Set(CALLERID(name)=*BL*${CALLERID(name)})
;Set Call Detail Record Userfield to Blacklisted
exten => s,n,Set(CDR(userfield)=Blacklisted)
;Still more original blacklist context
exten => s,n,Wait(1)
exten => s,n,Zapateller()
exten => s,n,Playback(ss-noservice)
exten => s,n,Hangup
;–== end of [app-blacklist-check] ==–;

The next concern (purely for aesthetics) is my workflow for installing the Pat Fleet voice.

I usually wget the zip archive, unzip, and copy the "pa" folder to "/var/lib/asterisk/sounds."

In FreePBX, I would be able to set the "language" code under the SIP settings. In 13-13, this whole part has changed, and I am unable to set the language code, like in 13-12.

My last concern is that 13-13 is still marked as "pioneers" and therefore, is considered unstable for production.

I would appreciate any answers you can provide me with to my concerns or questions.

 

[kyle95wm]

Okay, so I tried setting up the Gmail SMTP relay. The test message line works, however voicemail to email refuses to work in 13-13. What's going on?

 

[kyle95wm]

Okay, a little update. I somehow fixed the VM to email issue by running the Enchilada Upgrade. For some reason, these notifications work now. Any ideas why this is? Now it's only a matter of addressing my other concerns. Once I get those fixed, I'll test 13-13 at my house before considering it for business use.

 

[kyle95wm]

Okay, another update. I installed the Pat Fleet voice in the following way:

Went to Admin>Sound Languages

After that, I clicked the "custom" button on the top. After which, I added a new custom language with the code of "pa" and name of "Pat Fleet."

On the command line, I ran the following commands:

cd /tmp
git clone https://github.com/hharte/PatFleet-asterisk.git
cd PatFleet-asterisk
cp -R pa/ /var/lib/asterisk/sounds/

After this, I went back to the main Sound Languages screen and clicked "Settings." In here, I set the default language. All is going well so far.

The only concerns left to address are the following:

- Custom blacklist checker script - somehow adapt it to the original context's code

I think that's the only concern left. I still don't understand why the sendmailmp3 binary was not included with the Lean installation since that's what I wanted to begin. Oh well, it's better than nothing I say.

 

[wardmundy]

If I'm not mistaken, sendmailmp3 should be in the /usr/local/sbin folder already.

 

[kyle95wm]

It wasn't, not on my LEAN build anyways. I'll do another LEAN build and update if I find out anything. To get sendmailmp3, I had to run the Enchilada Upgrade script. I looked it over, and there's no mention in there about sendmailmp3.

 

[kyle95wm]

UPDATE:

Just built a LEAN install and issued the following command and got the following error:

root@lab:~ $ which sendmailmp3
/usr/bin/which: no sendmailmp3 in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)

 

[kyle95wm]

UPDATE: Ran the upgrade and now I have sendmailmp3 in the correct folder:

root@lab:~ $ which sendmailmp3
/usr/local/sbin/sendmailmp3

 

[kyle95wm]

@wardmundy Please check the section at like 1071 of the main installer. I noticed a bunch of lines for sendmailmp3 were commented out. Was this intentional?

 

[kyle95wm]

Alright, started working on the last piece of the puzzle.

On the old 13-12.x system I opened /etc/asterisk/extensions_additional.conf and search for app-blacklist-check context and found the following context:

[app-blacklist-check]
include => app-blacklist-check-custom
exten => s,1(check),GotoIf($["${BLACKLIST()}"="1"]?blacklisted)
exten => s,n,Set(CALLED_BLACKLIST=1)
exten => s,n,Return()
exten => s,n(blacklisted),Answer
exten => s,n,Wait(1)
exten => s,n,Zapateller()
exten => s,n,Playback(ss-noservice)
exten => s,n,Hangup

;--== end of [app-blacklist-check] ==--;

I then wrote the code above in the original post.

On the new 13-13 system:
I opened /etc/asterisk/extensions_additional.conf and search for app-blacklist-check context and found the following context:

[app-blacklist-check]
include => app-blacklist-check-custom
exten => s,1(check),GotoIf($["${BLACKLIST()}"="1"]?blacklisted)
exten => s,n,Set(CALLED_BLACKLIST=1)
exten => s,n,Return()
exten => s,n(blacklisted),Answer
exten => s,n,Set(BLDEST=${DB(blacklist/dest)})
exten => s,n,GotoIf(${LEN(${BLDEST})}?${BLDEST}:app-blackhole,zapateller,1)

;--== end of [app-blacklist-check] ==--;

Going from that logic, I wrote this:

[app-blacklist-check]
exten => s,1(check),Set(CDR(did)=${FROM_DID})
;Original first line of context with line number changed
exten => s,n(check),GotoIf($["${BLACKLIST()}"="1"]?blacklisted)
;Blacklist Caller ID names found in custom Asterisk database BLISTNAME if used
exten => s,n,GotoIf($["${DB_EXISTS(BLISTNAME/${TOUPPER(${CALLERID(name)})})}"="1"]?blacklisted)
;Blacklist Caller ID names of single letter followed by 9 or more digits
exten => s,n,Set(regx=^[A-Z][0-9]{9}[0-9]* *$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(name)})} = 1]?blacklisted)
;Blacklist numbers where first digit of 7 digit local number is 0 or 1
exten => s,n,Set(regx=^[+]?1?[0-9]{3}[01][0-9]{6}$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(num)})} = 1]?blacklisted)
;Blacklist numbers where first digit of area code is 0 or 1
exten => s,n,Set(regx=^[+]?1?[01][0-9]{9}$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(num)})} = 1]?blacklisted)
;Blacklist numbers where first three digits of 7 digit local number are 555
exten => s,n,Set(regx=^[+]?1?[0-9]{3}555[0-9]{4}$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(num)})} = 1]?blacklisted)
;Blacklist numbers that start with 1 but are longer than 11 digits total
exten => s,n,Set(regx=^[+]?1[0-9]{11}[0-9]*$)
exten => s,n,GotoIf($[${REGEX("${regx}" ${CALLERID(num)})} = 1]?blacklisted)
;Blacklist numbers of less than 7 digits in length
exten => s,n,GotoIf($[${LEN(${CALLERID(num)})} < 7]?blacklisted)
;Blacklist numbers of 8 digits in length
exten => s,n,GotoIf($[${LEN(${CALLERID(num)})} = 8]?blacklisted)
;Next line is from the original blacklist context
exten => s,n,Set(CALLED_BLACKLIST=1)
;Special CallerID name lookup; should not really be here but works
exten => s,n,ExecIf($["${DB_EXISTS(cidname/${CALLERID(num)})}"!="1″]?Return())
exten => s,n,Set(CALLERID(name)=${DB(cidname/${CALLERID(num)})})
exten => s,n,Set(__SKIPCIDLOOKUP=1)
;More original blacklist context
exten => s,n,Return()
exten => s,n(blacklisted),Answer
;Prepend *BL* to Caller ID name of blacklisted numbers so they can be distinguished in CDR
exten => s,n,Set(CALLERID(name)=*BL*${CALLERID(name)})
;Set Call Detail Record Userfield to Blacklisted
exten => s,n,Set(CDR(userfield)=Blacklisted)
;Still more original blacklist context
exten => s,n,Set(BLDEST=${DB(blacklist/dest)})
exten => s,n,GotoIf(${LEN(${BLDEST})}?${BLDEST}:app-blackhole,zapateller,1)
;–== end of [app-blacklist-check] ==–;

Does my code look right for 13-13?

 

[wardmundy]

Here's how to test it. Copy your modified contexts to extensions_override_freepbx.conf and restart Asterisk. You can't modify extensions_additional because they will get overwritten the first time you make any change in the GUI.

 

[kyle95wm]

Yeah, I actually wound up doing that. The new code works, so I'll be saving it for future use. Would you mind looking into why sendmailmp3 doesn't come with the LEAN install? The line number I mentioned had all of that stuff commented out.

 

[wardmundy]

Hi @kyle95wm. The Lean version was intended to be just that. I misunderstood you initially thinking you were using the Full Enchilada. With the Lean version, adding desired components is completely up to you. We have published a list of the add-ons with tutorials on Nerd Vittles:

INCREDIBLE PBX 13-13

• Incredible PBX in the Cloud: A $10/Year VoIP Cloud Platform
• Happy New ISO: Incredible PBX 13-13 ISO Is Here!
• Now Serving: The Incredible PBX 13-13 Whole Enchilada
• Back to Basics: Configuring Extensions, Trunks, and Routes
• 300 New Wholesale Providers Make Incredible PBX Shine
• Incredible PBX 13-13 Application User's Guide
• Virtual Paradise: Incredible PBX 13-13 for VMware & VirtualBox
• Incredible PBX Backup & Restore for Cloud-Based Servers
• The Ultimate Voice Dialer for Asterisk and Incredible PBX
• Game Changer: Hooking Up Facebook with Incredible PBX
• VoIP Security: Installing SSL Certificates with Incredible PBX
• Creating Free IBM Voice Prompts for Asterisk and 3CX
• Free Asterisk Voicemail Transcription with IBM Watson STT

 

[kyle95wm]

@wardmundy so I took a look at the "application guide" and nowhere in there does it mention "sendmailmp3". Am I missing something?

 

[wardmundy]

See last item in list above.