Skip to main content

whisper and barging

Posted by sbutera on Fri, 09/12/2008

I am trying to determine if TL supports whisper monitoring or barging. We have sales call center clients that will require this feature.

Can anyone answer confirm this feature is available?


Submitted by mattdarnell on Fri, 09/12/2008 Permalink

Thirdlane is just a GUI on top of Asterisk. Not all the functionality of Asterisk has been exposed. You always can manually do things via the config files if you want to do something that TL hasn't exposed.

That said, I don't think that is exposed via the GUI.

-Matt

Submitted by thirdlane on Mon, 09/15/2008 Permalink

If I understand this correctly it is a question of how to execute barging in/whisper through the web GUI or some other way. "Some other way" in Thirdlane is creating a script - 1) you can write your own and "plug" it into the GUI by associating it with a Feature Code or 2) we could do that for you knowing the specific requirements.

Best regards,

Alex

Submitted by fuse3 on Tue, 09/23/2008 Permalink

Alex,

I think what Scott (sbutera) was looking for is the ability for a remote user to perform a whisper/barging from their remote phone. Yes a feature code type config would be perfect, enter feature code then users extention. What would it take to accomplish this?

Thank you

Michael

Submitted by eeman on Tue, 09/23/2008 Permalink

look at applications

ChanSpy

ExtenSpy

you should be able to write a custom script + feature extension to accomplish your tasks

Submitted by rbf on Wed, 02/16/2011 Permalink

I have successfully used ExtenSpy in other deployments, but I am having trouble making it work inside the Thirdlane architecture.

Any assistance would be appreciated.

I have set up a script (and a feature code to point at that script). The script looks like this:

exten => s,1,ExtenSpy(101@from-inside-test)

no dice. I hear the BEEP but no spying.

I have tried various incarnations of the same thing. Here are the attempts:

exten => s,1,ExtenSpy(101@local-extensions-test)
or
exten => s,1,ExtenSpy(101@from-inside-test)
or
exten => s,1,ExtenSpy(101-test@from-inside-test)
or
exten => s,1,ExtenSpy(101-test@local-extensions-test)
or
exten => s,1,ExtenSpy(101)

In each case I hear the BEEP indicating that Asterisk is spying, but the call on 101 is not being spyed. All I hear is dead air.

I am pretty sure that this has to do with me referencing the wrong context. The entry in sip.conf for the extension in question is:
[101-test]
qualify=yes
nat=yes
pickupgroup=3
callerid=Test <101>
context=from-inside-test
call-limit=9
canreinvite=no
vmexten=101
secret=secret
username=101-test
host=dynamic
subscribecontext=local-extensions-test
callgroup=3
dtmfmode=rfc2833
type=friend
mailbox=101@default-test
disallow=all
allow=ulaw
allow=alaw

Thanks

Submitted by rbf on Thu, 02/17/2011 Permalink

You are right. The number of contexts flying around got me flustered.

ChanSpy is a better alternative.

Thanks again.

Submitted by moshe on Tue, 05/28/2013 Permalink

use the following script wit an argument for the password


exten => s,1,Authenticate(${ARG1})
exten => s,n,Read(SPYNUM,vm-extension)
exten => s,n,ChanSpy(SIP/${SPYNUM}${TL_DASH}${tenant},q)

Im only using it ChanSpy i never tried ExtenSpy