Member
Last active 12 years ago
Here is a debug dump from failing spy session.
79.135.228.xxx <= <msg data="19|tospy|31|ade261879d45d5b8e6f3918741fc1515" />^M -- PROCESS_FLASH_COMMAND origen 19 accion tospy destino 31 password ade261879d45d5b8e6f3918741fc1515 VALIDAR USUARIO 1030@GENERAL VALIDAR USUARIO 1030 OK con clave regular (79.135.228.xxx) Validation ok, have all permissions for all buttons (0) 31 It's blessed into class Extension It's blessed into class Extension TO SPY no hay canal activo a espiar!
Can you describe what is happening. I can understand only english.
I've upgraded to 2.24 and nothing changed. The issue is still here.
I'm using 2.23
I'll try to update to 2.24 tonight and post results in a couple of days, after testing.
HI.
Fop shows a strange behavior when i'm trying to spy a channel.
Sometimes it just ignores me.
I see a command to spy in fop log (something like <= <msg data="19|tospy|38|5a80f4ab867759349c0892c7768a9032" /> ) but fop server doesn't send spy to asterisk.
What can be a reason for this?
If a spy session was successfully established fop server log shows something like this:
127.0.0.1 -> Action: Originate 127.0.0.1 -> Channel: Local/1001@from-internal 127.0.0.1 -> CallerID: 1001 127.0.0.1 -> Application: ChanSpy 127.0.0.1 -> Data: SIP/1053,bq 127.0.0.1 -> ActionID: fop2spy!SIP/1053 127.0.0.1 -> Async: True
I haven't find any regularity for successful and unsuccessful attempts.