Remote Monitoring Setup

[linuxknight]

I have setup the foundation for a remote monitoring system for the owner of our company.

He is unhappy with the setup, and says he wants be able to access conferences from anywhere without having to look at the real-time summaries to acquire sessionids. In short he wants to troll and be able to jump between sessionids, active or not - and not be disconnected.

I've played around with the Meetme options, and came up with what I thought would work. Ideally if the conference ends, or the monitoring person hits #, I would like for it to drop to the previous context.

Any ideas on how to enhance this? Please forgive the sloppy code as I am a fairly new user.

; remote silent monitoring for client
exten => 5000,1,Authenticate(123456,j,6)
exten => 5000,2,Goto(sessions,s,1)
exten => 5000,102,Hangup()

[sessions]
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})
exten => s,1,Set(TIMEOUT(digit)=10)
exten => s,n,Set(TIMEOUT(response)=10)
exten => s,n,Background(sessions_menu)
exten => 51,1,Meetme,8600051|FmqrXp
exten => 52,1,Meetme,8600052|FmqrXp
exten => 53,1,Meetme,8600053|FmqrXp
exten => 54,1,Meetme,8600054|FmqrXp
exten => 55,1,Meetme,8600055|FmqrXp
exten => 56,1,Meetme,8600056|FmqrXp
exten => 57,1,Meetme,8600057|FmqrXp
exten => 58,1,Meetme,8600058|FmqrXp
exten => 59,1,Meetme,8600059|FmqrXp
exten => 60,1,Meetme,8600060|FmqrXp
exten => 61,1,Meetme,8600061|FmqrXp
exten => 62,1,Meetme,8600062|FmqrXp
exten => 63,1,Meetme,8600063|FmqrXp
exten => 64,1,Meetme,8600064|FmqrXp
exten => 65,1,Meetme,8600065|FmqrXp
exten => 66,1,Meetme,8600066|FmqrXp

[mflorell]

Interesting idea, let us know if it works. The only remote monitoring solutions we've made involve using a web interface in some way.

[linuxknight]

Hi Matt, would something like this work? I cant seem to figure out the syntax where it would dump the caller back to the "sessions" context.

[sessions]
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})
exten => s,1,Set(TIMEOUT(digit)=10)
exten => s,n,Set(TIMEOUT(response)=10)
exten => s,n,Background(sessions_menu)
exten => 51,1,Meetme,8600051|FmqX,Set(MEETME_EXIT_CONTEXT=sessions)

[mflorell]

I have no idea and don't really have much time to experiment, why don't you try it and let us know if it works?

[linuxknight]

This is the closest thing which makes sense to me based on my asterisk knowledge (which is very little) and looking at the MeetMe options. It still doesnt work, but will post any progress here. I read somewhere that there was a bug in asterisk 1.2.0 with respect to the X option, but we are using 1.2.30.2. Ill keep at it, Thank you.

; remote silent monitoring for client
exten => 5000,1,Authenticate(123456,j,6)
exten => 5000,2,Goto(sessions,s,1)
exten => 5000,102,Hangup()

[sessions]
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})
exten => s,1,Set(TIMEOUT(digit)=10)
exten => s,n,Set(TIMEOUT(response)=10)
exten => s,n,Set(MEETME_EXIT_CONTEXT=sessions_exit)
exten => s,n,Background(sessions_menu)
exten => 51,1,Meetme,8600051|FmqX
exten => 52,1,Meetme,8600052|FmqX
exten => 53,1,Meetme,8600053|FmqX
exten => 54,1,Meetme,8600054|FmqX
exten => 55,1,Meetme,8600055|FmqX
exten => 56,1,Meetme,8600056|FmqX
exten => 57,1,Meetme,8600057|FmqX
exten => 58,1,Meetme,8600058|FmqX
exten => 59,1,Meetme,8600059|FmqX
exten => 60,1,Meetme,8600060|FmqX
exten => 61,1,Meetme,8600061|FmqX
exten => 62,1,Meetme,8600062|FmqX
exten => 63,1,Meetme,8600063|FmqX
exten => 64,1,Meetme,8600064|FmqX
exten => 65,1,Meetme,8600065|FmqX
exten => 66,1,Meetme,8600066|FmqX

[sessions_exit]
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})
exten => #,n,Goto(sessions,s,1)