Stir Shaken Is Upon Us

Home » Asterisk Users » Stir Shaken Is Upon Us
Asterisk Users 10 Comments

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_connections0
database=strshk

func_odbc.conf
[STRSHK]
escapecommas=yes prefix=MYSQL
dsn=strshk readsql

10 thoughts on - Stir Shaken Is Upon Us

  • Again?

    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?

    So 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@sedwards.com Voice: +1-760-468-3867 PST
    https://www.linkedin.com/in/steve-edwards-4244281

    —

  • As well support will go into Asterisk 16 and 17 as well. It’s just been under active development so we’ve been waiting for that to finish before bringing it back into those versions.

  • Thanks for clarifying that Josh. I only had 5 min on the CommCon presentation so I focused more on the Asterisk 18 side of things rather than clarifying a lot of that 🙂

    Matthew Fredrickson

    —

  • One more question, what about the pjsip pcap support? Will it be backported to Asterisk 16, too? Would be absolutely cool! Debugging encrypted SIP is really a pain.

    BTW: what about the (encrypted) RTP packets? Will they be dumped, too?

    Thanks Michael

    —

  • It can’t be backported … because it already is. 😀 This support is actually in the latest releases of 13, 16, and 17.

    Not yet supported but certainly something we’d like to see as well as the RTCP, ICE, STUN, TURN, and DTLS packets.

  • Thanks Josh for clarifying! I’d assumed it would be backported but didnt want to just assume 🙂 Thanks Matt for doing the video! (hint hint theres a load of good content THIS WEEK over on the commcon youtube channel but that’s all I’ll say about that here)

  • This is perfectly good news! How often would I have it already needed in the past! Thanks!

    Just to be sure:

    pjsip set logger pcap (written to /var/lib/asterisk/)
    pjsip set logger on (switches on logging to file and console)
    pjsip set logger off (switches off logging to file and console)

    Is it possible to log only to the file and not to the console?

    Would be absolutely necessary to debug broken encrypted packets.

    Thanks Michael

    —

  • The “pjsip set logger verbose off” CLI command can be used to disable verbose messages to the console.

  • 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@sedwards.com Voice: +1-760-468-3867 PST
    https://www.linkedin.com/in/steve-edwards-4244281

    —