Latest update to 5.211.65-14 broke Motif

I am still using Motif for Google Voice and up until yesterday it was working fine. After automatic update to 5.211.65-14 I starting having problems with Dahdi Config (solved on another thread, but seems a bug) and now with Motif. Whenever a call is routed through Motif trunk this is what I get:

– Executing [[email protected]:2] Set(“SIP/110-0000000f”, “ROUTEUSER=110”) in new stack
– Executing [[email protected]:3] GotoIf(“SIP/110-0000000f”, “1?restrictedroute-1-2-3-4-5,0019208868130,2:outbound-allroutes,0019208868130,2”) in new stack
– Goto (restrictedroute-1-2-3-4-5,0019208868130,2)
[2014-06-17 15:43:14] WARNING[9216][C-00000010]: pbx.c:6640 __ast_pbx_run: Channel ‘SIP/110-0000000f’ sent to invalid extension but no invalid handler: context,exten,priority=restrictedroute-1-2-3-4-5,0019208868130,2
echo*CLI>

Seems the route is restricted but can’t seem to find where/how to unrestrict it. Any help?

This is not a problem with motif but with Extension Routes. It’s misconfigured.

Well, somehow the update messed up my outbound routes so the prefix was missing in the Google Voice trunk. After correcting it, this is what I am getting:
– Executing [[email protected]:29] Set(“SIP/110-00000015”, “the_num=19208868130”) in new stack
– Executing [[email protected]:30] Dial(“SIP/110-00000015”, “Motif/googlevoice/[email protected],300,r”) in new stack
– Called Motif/googlevoice/[email protected]
[2014-06-17 16:06:45] ERROR[7542][C-00000016]: chan_motif.c:821 jingle_add_google_candidates_to_transport: Unable to add Google ICE candidates as ICE support not available or no candidates available
– Motif/[email protected] is proceeding passing it to SIP/110-00000015
== Everyone is busy/congested at this time (1:0/0/1)
– Executing [[email protected]:31] NoOp(“SIP/110-00000015”, “Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 42”) in new stack
– Executing [[email protected]:32] GotoIf(“SIP/110-00000015”, “0?continue,1:s-CHANUNAVAIL,1”) in new stack
– Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
– Executing [[email protected]:1] Set(“SIP/110-00000015”, “RC=42”) in new stack
– Executing [[email protected]:2] Goto(“SIP/110-00000015”, “42,1”) in new stack
– Goto (macro-dialout-trunk,42,1)
– Executing [[email protected]:1] Goto(“SIP/110-00000015”, “continue,1”) in new stack
– Goto (macro-dialout-trunk,continue,1)
– Executing [[email protected]:1] NoOp(“SIP/110-00000015”, “TRUNK Dial failed due to CHANUNAVAIL HANGUPCAUSE: 42 - failing through to other trunks”) in new stack
– Executing [[email protected]:2] Set(“SIP/110-00000015”, “CALLERID(number)=110”) in new stack
– Executing [[email protected]:7] Macro(“SIP/110-00000015”, “outisbusy,”) in new stack
– Executing [[email protected]:1] Progress(“SIP/110-00000015”, “”) in new stack
– Executing [[email protected]:2] GotoIf(“SIP/110-00000015”, “0?emergency,1”) in new stack
– Executing [[email protected]:3] GotoIf(“SIP/110-00000015”, “0?intracompany,1”) in new stack
– Executing [[email protected]:4] Playback(“SIP/110-00000015”, “all-circuits-busy-now&pls-try-call-later, noanswer”) in new stack
– <SIP/110-00000015> Playing ‘all-circuits-busy-now.alaw’ (language ‘en’)
– <SIP/110-00000015> Playing ‘pls-try-call-later.alaw’ (language ‘en’)
== Spawn extension (macro-outisbusy, s, 4) exited non-zero on ‘SIP/110-00000015’ in macro ‘outisbusy’
== Spawn extension (restrictedroute-1-2-3-4-5, 0019208868130, 7) exited non-zero on ‘SIP/110-00000015’

Looks like we will have this resolved later this afternoon.

Great. Thanks.

@tm1000 Should this be through a module update or script upgrade?

It will be through yum

@GameGamer43 can I have a price check on isle 10 please

A new release of our asterisk 11 rpms which should resolve this issue should be released shortly (barring no immediate issues).

Just installed the new rpms and everything seems to be working fine.
Thanks.