WORLDWIDE EMERGENCY
The code below needs to be executed before any SIP or PJSIP call destined
to the US network, or soon no call will terminate. This is called
Stir-Shaken, a new law from the FCC.
If this is not working the whole Asterisk industry will crash, vanish, be
gone. I am assuming that the caller ID and the Destination Number are in
the variables "${CALLERID(num):-10}" "${EXTEN:-11}"
;Dialplan section to execute before any Dial
[strshk]
exten =>
_X.,1,Set(ARRAY(Token)=${MYSQL_STRSHK(${CALLERID(num):-10},${EXTEN:-11})})
;same=n,Verbose(0,Token ${Token})
;same=n,SIPAddHeader(Identity:${Token}) ;OLD SIP CHANNEL
same=n,Set(PJSIP_HEADER(add,Identity)=${Token}) ; NEW PJSIP CHANNEL
same=n,Return()
/etc/odbcinst.ini or /etc/unixODBC/odbcinst.ini
[ODBC]
Trace=No
Trace File=/tmp/sql.log
Pooling=yes
[maria]
Description=ODBC for MySQL
Driver=/usr/lib64/libmaodbc.so
FileUsage=1
Threading=0
/etc/odbc.ini or /etc/unixODBC/odbc.ini
[strshk]
Description = MySQL ODBC Driver Testing
Driver = maria
Server = 208.73.232.47
#free testing service
User = anonymous
Password Database = strshk
Option = 3
res_odbc.conf
[strshk]
enabled=yes
dsn=strshk
sanitysql => select 1
isolation => read_uncommitted
username=anonymous
passwordpre-connect => yes
forcecommit => yes
connect_timeout => 10
negative_connection_cache => 300
max_connections=100
database=strshk
func_odbc.conf
[STRSHK]
escapecommas=yes
prefix=MYSQL
dsn=strshk
readsql=call strshk.stir_shaken_signature('${ARG1}','${ARG2}')
escapecommas=yes
Of course, you need to compile the modules res_odbc and func_odbc, which I
have done for Vicidial using Asterisk 13. But any Asterisk 11 and up can
use unixODBC.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20200712/1405d142/attachment.html>
On Sun, 12 Jul 2020, Saint Michael wrote:> WORLDWIDE EMERGENCYAgain?> The code below needs to be executed before any SIP or PJSIP call > destined to the US network, or soon no call will terminate. This is > called Stir-Shaken, a new law from the FCC. If this is not working the > whole Asterisk industry will crash, vanish, be gone.Seen any little chickens lately? According to 'https://www.fcc.gov/call-authentication': "In March 2020, the Commission adopted new rules requiring all originating and terminating voice service providers to implement caller ID authentication using STIR/SHAKEN technological standards in the Internet Protocol (IP) portions of their networks by June 30, 2021." So this is a provider issue, not an end user issue and 'June 30, 2021' doesn't sound like 'soon.' If this is legit, why haven't my providers said squat?> Server = 208.73.232.47So why do you want everybody to send you their call metadata? What's your endgame? Generate leads to call to pitch your service? Poach clients? Sorry if I sound cynical. It's 2020 and I'm fresh out of "F's." -- Thanks in advance, ------------------------------------------------------------------------- Steve Edwards sedwards at sedwards.com Voice: +1-760-468-3867 PST https://www.linkedin.com/in/steve-edwards-4244281
On Sun, 12 Jul 2020, Steve Edwards wrote:> So this is a provider issue, not an end user issue and 'June 30, 2021' > doesn't sound like 'soon.' If this is legit, why haven't my providers > said squat?Seems one of my providers, Vitelity (iax.cc to us old timers), when asked, is not panicking about the imminent end of the world: "Thank you for reaching out. We will not be doing any stir shaken changes until the end of the year. If changes are necessary client side, we will let you know." -- Thanks in advance, ------------------------------------------------------------------------- Steve Edwards sedwards at sedwards.com Voice: +1-760-468-3867 PST https://www.linkedin.com/in/steve-edwards-4244281