I have done a nice proof of concept in the past few hours to test the idea of an XMLRPC interface. I did it using res_perl which allowed me to prove it was a wise idea.

I did two simple ones.. asterisk.ShowChannels and asterisk.ShowUptime ... its possible but alot of the code and output in asterisk will need to have concise or machine readable output that is sane.

<432>:perl channels.pl
$VAR1 = {
          'channels' => {
                        'SIP/16-e3e1' => [
                                         'SIP/16-e3e1',
                                         'default',
                                         '999',
                                         '4',
                                         'Up',
                                         'MusicOnHold',
                                         'default',
                                         '16',
                                         '',
                                         '3'
                                       ]
                      }
        };


<433>:perl uptime.pl $VAR1 = { 'uptime' => '849' };

/b



On May 4, 2005, at 5:15 PM, Brian West wrote:

I VOTE for totally removing the manager... and replacing it with XML-RPC .. then each module can register methods when it loads... ;)

(and the flames start w000000000000000000sh)

/b

On May 4, 2005, at 9:29 AM, Olle E. Johansson wrote:


I see a lot of managare events named "Hold" and "Unhold", "ParkedCall", "UnParkedCall".

I would like to have *one* event name, say "Hold"
and then an additional paramater signalling the state, like

Event: Hold
Holdstatus: On | Off

Event: ParkedCall
PCstatus: Parked | Unparked | GivingUp

Does that make any sense?

For me, it would be much easier writing a parser... We do this in the
channel with registration status - one event name, then different status lines marking the current status.


/O
_______________________________________________
Asterisk-Dev mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-dev



_______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev


_______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev

Reply via email to