search for: peerlistcomplete

...PPeers, QueueStatus (the three that I will be calling the most) NONE of those three has a standard return value. Login doesn't return an Event: LoginComplete flag, so the login function can't use the generic Action function I've written. SIPPeers returns an additional line after Event: PeerlistComplete, and Peerlist != SIPPeers (meaning the action and eventcomplete flags should match, IMHO). The way QueueStatus returns data is the ideal, the action flag (QueueStatus) has a corresponding complete tag (QueueStatusComplete) and I can (fairly) easily parse the return data by tacking 'Complete...

...ntlist: start Message: Peer status list will follow Event: PeerEntry Channeltype: SIP ObjectName: 1001 ChanObjectType: peer IPaddress: 192.168.175.1 IPport: 63772 Dynamic: yes Natsupport: no VideoSupport: no TextSupport: no ACL: no Status: Unmonitored RealtimeDevice: yes Event: PeerlistComplete EventList: Complete ListItems: 1 Response: Success Message: Peer status list will follow Event: PeerEntry Channeltype: IAX2 ChanObjectType: peer ObjectName: 1001/1001 IPaddress: -none- IPport: 0 Dynamic: yes Trunk: no Encryption: no Status: UNKNOWN Event: PeerEntry Channeltype: IAX2 ChanO...

The Asterisk Manager Interface is driving me nuts. Whoever wrote it should be drawn and quartered. Sometimes the data comes back separated by \r\n, and sometimes it's separated by \n. The whole thing is completely inconsistent, and trying to write any kind of API for it is -GHASTLY- Doug.