First question: is ChanSpy dangerous to the switch from an operational standpoint. I mean there is none of the evil chan local stuff is there?
Second Question:
Found this in another post and added the ARG1 to it so I can have a unique password for every client:
exten => s,1,Authenticate(${ARG1})
exten => s,n,Read(SPYNUM,vm-extension)
exten => s,n,ChanSpy(SIP/${SPYNUM}${TL_DASH}${tenant},q)
ARG1 is just the Password
I was trying to figure out if there was a way to dial a feature code + the extension and then the lady would come on and ask for the password if correct connect the call.
Example: I want to monitor x204 with a feature code of *666
I dial *666204 the lady comes on and asks for the password if it is successful i listen if not I don't
Any Ideas? I have looked through the scripts and have found nothing. At least I am not able to Identify how it works so I can pull it out into my script.
IS ChanSpy Dangerous?
First question: is ChanSpy dangerous to the switch from an operational standpoint. I mean there is none of the evil chan local stuff is there?
That's the most important part of that question.
dangerous? not by design. The
dangerous? not by design. The best way to see if it has problems like chan_local is to just read through the patch logs (changelog) and do a search for chanspy. Tabulate how frequent they have to patch either a crash or a deadlock. If it seems like every other version then I would steer clear. Are you needing whisper mode? If not iSymphony had a good alternative. They take both parties and silently transfer them to a conference room while the eavesdropper is also merged into the conference room as a muted member.
use the pattern _*666! and then use ExecIF for the condition LEN(${MACRO_EXTEN}) < 5 if it matches true then execute your Read command, and if false use Set to set the value of SPYNUM to ${MACRO_EXTEN:4}