I've just tried this on a semi-fresh installation of CentOS and it looks to be working fine. And the configs look fine too. Does anybody else have the same problem? -benny Gideon Klompje wrote: > OK, without trying to make a monkey of myself, I get the following: > # svn co http://svn.pjsip.org/repos/pjproject/trunk pjproject > svn: REPORT request failed on '/repos/!svn/vcc/default' > svn: REPORT of '/repos/!svn/vcc/default': 403 Forbidden > (http://svn.pjsip.org) > > I'm using SVN "1.4.3dfsg1-1ubuntu1", but I get the same error in Windows > land (TortoiseSVN 1.4.4.9706 32-bit). Please advise... > > _____________ > Gideon Klompje > Engineer > BizCall > Subsidiary of Vox Telecom Limited > Block B, Rutherford Estate > 1 Scott Street > Waverley > tel: +27 800 BIZCALL > direct: +27 11 809 1656 > mobile: +27 84 560 0200 > fax: +27 86 524 2014 > email: gideonk at bizcall.co.za > http://www.bizcall.co.za > > Disclaimer: BizCall does not accept responsibility or liability for the > unauthorised use of its e-mail facility and/or opinions relating to bona > fide company matters. Save for statements and/or opinions relating to > bona fide company matters, Bizcall denies responsibility or liability > for the contents of this communication. > > -----Original Message----- > From: pjsip-bounces at lists.pjsip.org > [mailto:pjsip-bounces at lists.pjsip.org] On Behalf Of Benny Prijono > Sent: 10 September 2007 07:25 PM > To: pjsip at pjsip.org > Subject: Re: [pjsip] Buddy status text > > Gideon Klompje wrote: >> Hi, >> >> Please note that I sent this e-mail earlier (2007-09-03 subject: > "Buddy >> status"), but that was while the mailing list was having problems, so >> I'm not sure it reached the list. Apologies... > > The apology is ours. We apologize for all the mess with the list in > the past couple of weeks. > >> I've been playing around with PJSIP for about 2 days now (mainly using > >> py_pjsua), and I have a question about the way buddy status is > handled. >> I've noticed that the fields buddy_info.status and >> buddy_info.status_text only give you one the following (from "enum >> pjsua_buddy_status { PJSUA_BUDDY_STATUS UNKNOWN, >> PJSUA_BUDDY_STATUS_ONLINE, PJSUA_BUDDY_STATUS_OFFLINE}"): >> >> 0 = Unknown >> 1 = Online >> 2 = Offline >> >> This is neat and all, but I was wondering whether a more detailed > status >> is available. For example, if I'm monitoring an IP phone connected to > >> an Asterisk PBX, I'd like to know whether the phone (buddy) is "On the > >> phone" (busy) or "Idle" (ready to take a call). I noticed that the > SIP >> packets contain some XML that contains this information, but the >> struct/object "buddy_info" does not contain it. > > The most recent pjsip in SVN trunk (r1430) contains some support for > specifying and receiving custom presence status text in the NOTIFY > and PUBLISH requests. I've just updated the Python module to support > this feature. > > This feature implements subset of RPID XML presence data format. For > setting custom presence status text, one has to use the new > pjsua_acc_set_online_status2() instead of the usual > pjsua_acc_set_online_status(). > > When pjsip/PJSUA-LIB receives incoming NOTIFY, it will check for > this custom presence status text, and if it's present it will set > the pjsua_buddy_info's status_text to this string. If this custom > status is not present, then status_text will be just "Online" or > "Offline". > >> PS - I spent some time modifying py_pjsua.c to export the field "buf_" > >> (not available in the Python object for some reason) in the hope that > it >> might contain what I'm looking for, but my observations seem to show >> that it only contains the "contact" string at the time when my >> on_buddy_state_changed(buddy_id) equivalent is called (either that or > my >> implementation is dodge). Btw, I'm using v0.5.10.4. Instead of > hacking >> at the source code all day, I came to my senses and posted this mail. > > The buf_ field was really not supposed to be there at all, and it > has been removed. And sorry for the late reply, I hope by now you've > had more than enough time to hack pjsip's source code all day. ;) > > -benny > > > > > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -- Benny Prijono http://www.pjsip.org
