ExtenSpy

Discussion in 'General' started by mihpel, Jul 23, 2009.

  1. mihpel

    Joined:
    May 8, 2007
    Messages:
    87
    Likes Received:
    0
    Hi all

    Does anybody have any experience regarding the implementation of ExtenSpy

    I have found several references :

    http://www.panoramisk.com/64/real-time-call-listening/en/
    http://forums.digium.com/viewtopic.php?p=121974&sid=34e94cf34389fa7ab2e47c05d684ae32
    http://www.trixbox.org/forums/trixbox-forums/help/extenspy-permanent-configuration

    but thought a question here would not hurt anybody , right ?


    So any advice anybody ?

    Thx in advance!

    Edit:

    would something like this work :

    and how can i co mix the ability to whisper ?
    Should another context handle that ?
    like:


    Or is ExtenSpy mandatory for the ability to select a specific extention and be able to whisper to it ?

    Thanks again !
     
  2. Megabyte

    Joined:
    Mar 28, 2009
    Messages:
    327
    Likes Received:
    0
    Use this to chanspy depending your extension technologic.

    Put it in extension_custom.conf

    [chanspy]

    exten => 2500,1,Answer
    exten => 2500,n,Wait(1)
    exten => 2500,n,ChanSpy(SIP)
    exten => 2500,n,Hangup

    exten => 2501,1,Answer
    exten => 2501,n,Wait(1)
    exten => 2501,n,ChanSpy(ZAP)
    exten => 2501,n,Hangup

    exten => 2502,1,Answer
    exten => 2502,n,Wait(1)
    exten => 2502,n,ChanSpy(AGENT)
    exten => 2502,n,Hangup

    After that press the number of the extension you want to spy and the "#" and done. # ej: 2525#
     
  3. mihpel

    Joined:
    May 8, 2007
    Messages:
    87
    Likes Received:
    0
    So you have one entry for each extension?

    What about larger implementations ?

    How are you handling "whisper" ?

    Do you have this working ?
     
  4. Megabyte

    Joined:
    Mar 28, 2009
    Messages:
    327
    Likes Received:
    0
    NOpe its not for every extension bro, its one for technology, i mean one for all SIP (exten => 2500,1,Answer), exten => 2501,n,ChanSpy(ZAP) for Zap Channels and
    exten => 2502,n,ChanSpy(AGENT)for an agent.

    You got it?

    I mean if you want to listen on sip channel dial 2500 and later extension number+#
    if you want to listen on ZAP channel dial 2501 and later extension number+#


    etc
     
  5. mihpel

    Joined:
    May 8, 2007
    Messages:
    87
    Likes Received:
    0
    Ok i get it now !

    If you care to elaborate a bit further on this .....

    From application ChanSpy Description i see that

    which leads me to the conclusion that if 'chanprefix' is not set then any channel type can be spied upon regardless if it's sip, zap, agent, iax etc. . Is this correct ?

    Also from the entry

    Which again leads me to conclude that regardless if 'chanprefix' is set you can always jump to the desired channel after initiating ChanSpy.
    Also through this approach you have to start spying on a random channel before jumping to the desired one by entering xxxx# which is not optimal if you know what channel you want to spy on.

    If my assumptions are correct this is feasible but already coded in extensions_additional.conf .

    Also there is no prediction for whisper which is the main reason i am looking into this .



    If my above assumptions are not correct, ( i would really be grateful if someone took the time to share his wisdom! ) would modifying your approach as below, do the trick for purely directed chanspy with whisper?

    Then again if my assumptions are correct what would be the correct syntax to pass the 'w' whisper option without having to use 'chanprefix'?


    Many thanks for your time and sorry for the long post!
     
  6. mihpel

    Joined:
    May 8, 2007
    Messages:
    87
    Likes Received:
    0
    One more think !

    Theoretically :

    would achieve a directed extension spy with whisper enabled regardless of channel type.

    Is that correct ?
     

Share This Page