Reverse charge? - SOLVED

Asterisk 11

[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:1] Set(“SIP/ZZZ-0004c731”, “GROUP()=OUT_2”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:2] Goto(“SIP/ZZZ-0004c731”, “from-trunk,XXXXXXXXXX,1”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Goto (from-trunk,XXXXXXXXXX,1)
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:1] Set(“SIP/ZZZ-0004c731”, “__FROM_DID=XXXXXXXXXX”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:2] Set(“SIP/ZZZ-0004c731”, “CHANNEL(language)=en”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:3] Gosub(“SIP/ZZZ-0004c731”, “app-blacklist-check,s,1()”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:1] GotoIf(“SIP/ZZZ-0004c731”, “0?blacklisted”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:2] Set(“SIP/ZZZ-0004c731”, “CALLED_BLACKLIST=1”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:3] Return(“SIP/ZZZ-0004c731”, “”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:4] Set(“SIP/ZZZ-0004c731”, “CDR(did)=XXXXXXXXXX”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:5] ExecIf(“SIP/ZZZ-0004c731”, “0 ?Set(CALLERID(name)=07950224720)”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:6] Set(“SIP/ZZZ-0004c731”, “CHANNEL(musicclass)=default”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:7] Set(“SIP/ZZZ-0004c731”, “__MOHCLASS=default”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:8] Ringing(“SIP/ZZZ-0004c731”, “”) in new stack
[2015-07-23 09:15:52] WARNING[30558][C-0007b5f5] func_channel.c: Unknown or unavailable item requested: ‘reversecharge’
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:9] GotoIf(“SIP/ZZZ-0004c731”, “0?macro-hangupcall”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:10] Set(“SIP/ZZZ-0004c731”, “__CALLINGPRES_SV=allowed_not_screened”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:11] Set(“SIP/ZZZ-0004c731”, “CALLERPRES()=allowed_not_screened”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Executing [[email protected]:12] Goto(“SIP/ZZZ-0004c731”, “from-did-direct,YYYY,1”) in new stack
[2015-07-23 09:15:52] VERBOSE[30558][C-0007b5f5] pbx.c: [2015-07-23 09:15:52] – Goto (from-did-direct,YYYY,1)

Any idea why this would happen? Call comes in to extension 1 (XXXXXXXXXXX) but then ends up dialling (YYYY) due to blacklisting or reverse charging? Not sure if either of those is actually related to the problem though?

Very strange.

Cheers

Hi!

I can’t answer your main question but the “reversecharge” you see here is just a warning telling you that this channel doesn’t support that “indicator” ( See Reversecharge ).

I am also pretty sure it’s not blacklisting because I played a little with the blacklisting (I wanted the message to be in two languages) and I am pretty sure the path that was taken is the not blacklisted path…

Did you use follow-me perhaps?

Have a nice day!

Nick

That’s a successful inbound route match. Fix your inbound route.

Thanks - that was the problem. Seems like someone misconfigured the route.

1 Like