From discuss@opengroupware.org Sun Apr 1 20:51:41 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Sun, 01 Apr 2007 21:51:41 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070401195141.CD0DC373DC@l00-bugdead-prods.de> Hi all, discuss@opengroupware.org wrote: > > Again, some people do this, but its obviously an even smaller > > minority. And extremly uncommon (the far majority of users just have > > a Windows PC). > > Anyways, I'm not complaining :-) If you want to add support for such > > setups, feel free to do so! :-) > I added a patch to the following bug: http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=929 This started as a copy of the STLIDialer, but changed to allow triggering calls via the asterisk management interface. How it works is explained in the comment to the patch. This is at least working for me with a very basic asterisk setup, so it may not work everywhere yet. It also needs to be cleaned up, as there is still a lot of leftovers from the STLIDialer in the patch. Maybe not all solutions are perfect, comments are welcome. kind regards Sebastian From discuss@opengroupware.org Sun Apr 1 22:31:24 2007 From: discuss@opengroupware.org (chris h) Date: Sun, 1 Apr 2007 17:31:24 -0400 Subject: [OGo-Discuss] CTI Integration In-Reply-To: <20070401195141.CD0DC373DC@l00-bugdead-prods.de> References: <20070401195141.CD0DC373DC@l00-bugdead-prods.de> Message-ID: <200704011731.24671.chris123@magma.ca> On Sunday 01 April 2007 15:51, Sebastian Reitenbach wrote: > This started as a copy of the STLIDialer, but changed to allow triggering > calls via the asterisk management interface. How it works is explained in > the comment to the patch. This is at least working for me with a very basic > asterisk setup, so it may not work everywhere yet. It also needs to be > cleaned up, as there is still a lot of leftovers from the STLIDialer in the > patch. Maybe not all solutions are perfect, comments are welcome. This is a great start. I recall a poster stating that an alternative solution was being prepared for presentation at either CeBIT or FOSDEM. I have not heard anything nor any followup on any of the lists. Just wondering what happened to that initiative as it may assist you with yours. -- /ch From discuss@opengroupware.org Sun Apr 1 22:43:13 2007 From: discuss@opengroupware.org (Helge Hess) Date: Sun, 1 Apr 2007 23:43:13 +0200 Subject: [OGo-Discuss] CTI Integration In-Reply-To: <200704011731.24671.chris123@magma.ca> References: <20070401195141.CD0DC373DC@l00-bugdead-prods.de> <200704011731.24671.chris123@magma.ca> Message-ID: On Apr 1, 2007, at 23:31, chris h wrote: > I have not > heard anything nor any followup on any of the lists. Just wondering > what > happened to that initiative as it may assist you with yours. Oh, it was actually a success. The Reciprocate dialer works just fine with OGo. But for OGo its rather trivial from a technological PoV, we just need to generate tel: links and we are done :-) Greets, Helge -- Helge Hess http://www.helgehess.eu/ From discuss@opengroupware.org Tue Apr 3 21:23:18 2007 From: discuss@opengroupware.org (Adam Tauno Williams) Date: Tue, 03 Apr 2007 16:23:18 -0400 Subject: [OGo-Discuss] Freshmeat entries Message-ID: <1175631798.4943.10.camel@aleph.whitemice.org> --=-4MI4rw+fjDsliXlyZZ6N Content-Type: text/plain Content-Transfer-Encoding: quoted-printable The Freshmeat entries for OpenGroupware don't reflect the release of 1.0, etc... It would be a good thing, IMHO, to touch these, so to someone searching they look alive. http://freshmeat.net/projects/opengroupware_org/ http://freshmeat.net/projects/zidestore/ --=-4MI4rw+fjDsliXlyZZ6N Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD4DBQBGEre2LRePpNle04MRAo7ZAJYhyauDmf+EIPWNnYEd5ACaJftcAJ42A6+z UngC+cUd0P+Pqw447lM/ig== =Ima8 -----END PGP SIGNATURE----- --=-4MI4rw+fjDsliXlyZZ6N-- From discuss@opengroupware.org Tue Apr 3 22:20:09 2007 From: discuss@opengroupware.org (Helge Hess) Date: Tue, 3 Apr 2007 23:20:09 +0200 Subject: [OGo-Discuss] Freshmeat entries In-Reply-To: <1175631798.4943.10.camel@aleph.whitemice.org> References: <1175631798.4943.10.camel@aleph.whitemice.org> Message-ID: <25B58671-932F-4C5B-9F1F-670E5F6BB137@opengroupware.org> On Apr 3, 2007, at 22:23, Adam Tauno Williams wrote: > The Freshmeat entries for OpenGroupware don't reflect the release of > 1.0, etc... It would be a good thing, IMHO, to touch these, so to > someone searching they look alive. Yes, its on my todo list. Thanks, Helge -- Helge Hess http://www.helgehess.eu/ From discuss@opengroupware.org Wed Apr 4 20:15:26 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Wed, 04 Apr 2007 21:15:26 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070404191526.895B838E9F@l00-bugdead-prods.de> Hi, > I added a patch to the following bug: > http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=929 > > This started as a copy of the STLIDialer, but changed to allow triggering > calls via the asterisk management interface. How it works is explained in > the comment to the patch. This is at least working for me with a very basic > asterisk setup, so it may not work everywhere yet. It also needs to be > cleaned up, as there is still a lot of leftovers from the STLIDialer in the > patch. Maybe not all solutions are perfect, comments are welcome. > I just updated the patch, cleaned it up a bit, and added the possibility to set different contexts for internal and outgoing calls via some Defaults. the differentiation of internal and outgoing calls is not very sophisticated, but well, works for me ;) It makes just a decision about the length of the number called, if it matches the lenght of the internal extensions, then it is internal context, all the rest is the outgoing context. Maybe I should drop this and make an arbitrary number of contexts configurable? I'm open for suggestions, and feedback, if someone is testing. kind regards Sebastian From discuss@opengroupware.org Wed Apr 4 20:21:40 2007 From: discuss@opengroupware.org (Helge Hess) Date: Wed, 4 Apr 2007 21:21:40 +0200 Subject: [OGo-Discuss] CTI Integration In-Reply-To: <20070404191526.895B838E9F@l00-bugdead-prods.de> References: <20070404191526.895B838E9F@l00-bugdead-prods.de> Message-ID: <637C09B2-D44F-48B1-87C5-8C53565A5DE6@opengroupware.org> On Apr 4, 2007, at 21:15, Sebastian Reitenbach wrote: > I'm open for suggestions, and feedback, if someone is testing. Well something which would be cool is a page on docs which explains how everything fits together :-) Thanks, Helge -- Helge Hess http://www.helgehess.eu/ From discuss@opengroupware.org Wed Apr 4 20:54:29 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Wed, 04 Apr 2007 21:54:29 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070404195429.F379038E41@l00-bugdead-prods.de> Hi, discuss@opengroupware.org wrote: > On Apr 4, 2007, at 21:15, Sebastian Reitenbach wrote: > > I'm open for suggestions, and feedback, if someone is testing. > > Well something which would be cool is a page on docs which explains > how everything fits together :-) here we are: http://docs.opengroupware.org/Members/buzzdee/asterisk/OGo%20Asterisk%20Dialer/document_view From discuss@opengroupware.org Wed Apr 4 21:43:02 2007 From: discuss@opengroupware.org (Adam Tauno Williams) Date: Wed, 04 Apr 2007 13:43:02 -0700 Subject: [OGo-Discuss] CTI Integration In-Reply-To: <637C09B2-D44F-48B1-87C5-8C53565A5DE6@opengroupware.org> References: <20070404191526.895B838E9F@l00-bugdead-prods.de> <637C09B2-D44F-48B1-87C5-8C53565A5DE6@opengroupware.org> Message-ID: <5009-SnapperMsg05076A73C239BE9D@[75.212.33.94]> >> I'm open for suggestions, and feedback, if someone is testing. >Well something which would be cool is a page on docs which explains >how everything fits together :-) Here Here! :) Not having an asterisk box this is all a bit abstract, some docs would be very nice. I night even be inspired to try and make it work with one of these &+$)#?@ Nortel phone systems. Although I'm pretty sure what a call context is, does the the PBXls dial plan not do this for you? (Haven't really done much CTI stuff). From discuss@opengroupware.org Fri Apr 6 08:17:51 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Fri, 06 Apr 2007 09:17:51 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070406071752.4F673392A3@l00-bugdead-prods.de> discuss@opengroupware.org wrote: > >> I'm open for suggestions, and feedback, if someone is testing. > >Well something which would be cool is a page on docs which explains > >how everything fits together :-) > > Here Here! :) http://docs.opengroupware.org/Members/buzzdee/asterisk/OGo%20Asterisk%20Dialer > > Not having an asterisk box this is all a bit abstract, some docs would be very nice. I night > even be inspired to try and make it work with one of these &+$)#?@ Nortel phone systems. I don't know how Nortel works, but at least for the Asterisk it was fairly easy. > > Although I'm pretty sure what a call context is, does the the PBXls dial > plan not do this for you? (Haven't really done much CTI stuff). As far as I know, there is a fallback context that is used if nothing else matches, but I am not perfectly sure about that. At least I know it triggers my phone to dial the right number, when I give the right contexts. As this dialling is now working for me, I think it would be great to have access to more features that the Asterisk system provides. The most intersting features for me would be: - management of meeting rooms (app_conference or meetme) - notifications about voice-mails and voice mailbox status, managing voice-mail - see whether other extensions are "online" (especially important for mobile users with softphones) I am not sure whether this would fit into the AsteriskDialer or whether it would more appropriate to provide this functionality as a separate library or bundle, or whether it would better belong to sope, like sope-mime, a sope-asterisk bundle? kind regards Sebastian From discuss@opengroupware.org Fri Apr 6 13:36:46 2007 From: discuss@opengroupware.org (Michael Brown) Date: Fri, 06 Apr 2007 8:36:46 -0400 Subject: [OGo-Discuss] CTI Integration In-Reply-To: <20070406071752.4F673392A3@l00-bugdead-prods.de> References: <20070406071752.4F673392A3@l00-bugdead-prods.de> Message-ID: <225-SnapperMsg8EFA1DC3C23BEF81@[192.168.0.2]> ...... Original Message ....... On Fri, 06 Apr 2007 09:17:51 +0200 "Sebastian Reitenbach" >I am not sure whether this would fit into the AsteriskDialer or whether it >would more appropriate to provide this functionality as a separate library >or bundle, or whether it would better belong to sope, like sope-mime, a >sope-asterisk bundle? I'd say a seperate bundle from the dialer. One of OGo's strenths is it's modularity; admins can deploy what they want. Some may only want to deploy the dialer, as they may have some other app for management. I'd definately say develop a management app for Asterisk; it would just enhance the overall OGo experience for many. It would be wise to enhance the website "features" section to show the Telephony and Messaging integrations that people have been working on. Especially as they get added to either the core, or maybe a "user contribs" section. Hope that helps! /Mike From discuss@opengroupware.org Fri Apr 6 16:03:47 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Fri, 06 Apr 2007 17:03:47 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070406150348.1023739394@l00-bugdead-prods.de> Hi, discuss@opengroupware.org wrote: > discuss@opengroupware.org wrote: > > On Mar 28, 2007, at 12:49, Sebastian Reitenbach wrote: > > > yes, they do, massively, assume some sales people, stuffed with a voip > > > client on their notebook, connected via VPN to the company, or > > > employees > > > working at home, ... In my eyes, this is a rapidly growing group of > > > telephone users, which not uses static assigned desktops to notebooks. > > > > Yes, but its still a very small minority. I suppose it isn't even 1% > > of the installed PBXes, including VoIP ones. Whatever ... > > > > >> Yes. Its for inhouse operation. > > > Terminal servers are used inhouse, at least what I mean with > > > terminal server > > > in the old unix style, e.g. a lot of people connect vi X or NX to a > > > powerful > > > station, to work on this one, If they access the groupware, they > > > all come > > > from that one IP address. I think this is also not too uncommon usage. > > > > Again, some people do this, but its obviously an even smaller > > minority. And extremly uncommon (the far majority of users just have > > a Windows PC). > > > > Anyways, I'm not complaining :-) If you want to add support for such > > setups, feel free to do so! :-) just done that: http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1863 kind regards Sebastian From discuss@opengroupware.org Fri Apr 6 16:51:13 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Fri, 06 Apr 2007 17:51:13 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070406155113.B780838E41@l00-bugdead-prods.de> Hi, > > I'd say a seperate bundle from the dialer. One of OGo's strenths is it's > modularity; admins can deploy what they want. Some may only want to deploy > the dialer, as they may have some other app for management. I'd definately > say develop a management app for Asterisk; it would just enhance the > overall OGo experience for many. yes, makes sense to me too, I could imagine sth. for the user like the email UI, with some tabs like: see who is online, managing voice-mail, managing virtual telephone conference rooms. > > Hope that helps! > thanks. Sebastian From discuss@opengroupware.org Fri Apr 6 18:42:26 2007 From: discuss@opengroupware.org (Adam Tauno Williams) Date: Fri, 06 Apr 2007 10:42:26 -0700 Subject: [OGo-Discuss] CTI Integration In-Reply-To: <20070406071752.4F673392A3@l00-bugdead-prods.de> References: <20070406071752.4F673392A3@l00-bugdead-prods.de> Message-ID: <5381-SnapperMsg05076A73C23C3708@[75.213.86.242]> >> Not having an asterisk box this is all a bit abstract, some docs would be >very nice. I night >> even be inspired to try and make it work with one of these &+$)#?@ Nortel >phone systems. >I don't know how Nortel works, but at least for the Asterisk it was fairly >easy. Probably simple, the hard part is digging through all the proprietary docs to find the API. But I have managed to reverse engineer part of the Call Pilot unified messaging API. Since the next version of the BCM is LINUX based vs. Embedded-NT I'll probably wait until we upgrade. > - management of meeting rooms (app_conference or meetme) Doesn't ogo already provide this via resources, or do you mean the creation of conference bridges on the PBX? > - notifications about voice-mails I really think the job of notification should fall to XMPP. >and voice mailbox status, managing >voice-mail Does Asterisk not support storing of messages in IMAP, or managing messages via IMAP? This is what Nortel's callpilot does, it is actually a rather nice model. Perhaps someone could add this to Asterisk? Seems like using the code based from a simple IMAP server it should be reasonably simply to overlay the Asterisk spool directory. This would give you something like 'real' unified messaging from any client, including OGO. > - see whether other extensions are "online" (especially important for > mobile users with softphones) Again seems like a job for XMPP. Wildfire XMPP server has a very nice plugin that allows you to check presence via a single HTTP GET. From discuss@opengroupware.org Fri Apr 6 19:07:03 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Fri, 06 Apr 2007 20:07:03 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070406180703.9E44F3940C@l00-bugdead-prods.de> Hi, discuss@opengroupware.org wrote: > >> Not having an asterisk box this is all a bit abstract, some docs would be > >very nice. I night > >> even be inspired to try and make it work with one of these &+$)#?@ Nortel > >phone systems. > >I don't know how Nortel works, but at least for the Asterisk it was fairly > >easy. > > Probably simple, the hard part is digging through all the proprietary docs to find the API. > But I have managed to reverse engineer part of the Call Pilot unified > messaging API. Since the next version of the BCM is LINUX based vs. > Embedded-NT I'll probably wait until we upgrade. > > > - management of meeting rooms (app_conference or meetme) > > Doesn't ogo already provide this via resources, or do you mean the > creation of conference bridges on the PBX? yes, virtual telephone conference rooms created on the asterisk, more here: http://www.voip-info.org/wiki/view/Asterisk+app_conference > > > - notifications about voice-mails > > I really think the job of notification should fall to XMPP. > > >and voice mailbox status, managing > >voice-mail > > Does Asterisk not support storing of messages in IMAP, or managing > messages via IMAP? This is what Nortel's callpilot does, it is actually a > rather nice model. Perhaps someone could add this to Asterisk? Seems like > using the code based from a simple IMAP server it should be reasonably > simply to overlay the Asterisk spool directory. This would give you > something like 'real' unified messaging from any client, including OGO. I have no idea whether I can do this with asterisk, maybe there is a branch that enhances it that way, but I am not aware of any. Well, Asterisk could send mail notifications to users about new voice mails, but I doubt that I could manage the voice mail box in any way via mail. > > > - see whether other extensions are "online" (especially important for > > mobile users with softphones) > > Again seems like a job for XMPP. > well, yes, xmpp presence could be checked too. Sebastian From discuss@opengroupware.org Fri Apr 6 19:11:50 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Fri, 06 Apr 2007 20:11:50 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070406181151.0EB18393DA@l00-bugdead-prods.de> Hi, > > > - notifications about voice-mails > > I really think the job of notification should fall to XMPP. > what about like sth. for e-mail, the link to the asterisk managment bold written in the dock, or a configurable popup like it exists for e-mail? notification via xmpp is also a good idea, with asterisk 1.4 some xmpp integration is done, but I haven't digged into it yet. maybe the asterisk supports it on its own already. Sebastian From discuss@opengroupware.org Sat Apr 7 00:10:22 2007 From: discuss@opengroupware.org (Adam Tauno Williams) Date: Fri, 06 Apr 2007 16:10:22 -0700 Subject: [OGo-Discuss] CTI Integration In-Reply-To: <20070406181151.0EB18393DA@l00-bugdead-prods.de> References: <20070406181151.0EB18393DA@l00-bugdead-prods.de> Message-ID: <5430-SnapperMsg05076A73C23C8456@[75.212.34.1]> >what about like sth. for e-mail, the link to the asterisk managment bold >written in the dock, If you mean bold if there is unread voice mail, yes, that would be cool. But I'm confused by the term "asterisk mangement". I think an OGo bundle should be end-user oriented, I don't see what an administrative interface would offer in addition to what is already available. > or a configurable popup like it exists for e-mail? Yes. Personally, I've found web driven notification popups to be notoriously unreliable. >notification via xmpp is also a good idea, with asterisk 1.4 some xmpp >integration is done, but I haven't digged into it yet. maybe the asterisk >supports it on its own already. From discuss@opengroupware.org Sat Apr 7 00:04:01 2007 From: discuss@opengroupware.org (Adam Tauno Williams) Date: Fri, 06 Apr 2007 16:04:01 -0700 Subject: [OGo-Discuss] CTI Integration In-Reply-To: <20070406180703.9E44F3940C@l00-bugdead-prods.de> References: <20070406180703.9E44F3940C@l00-bugdead-prods.de> Message-ID: <5432-SnapperMsg05076A73C23C845A@[75.212.34.1]> >> > - management of meeting rooms (app_conference or meetme) >> Doesn't ogo already provide this via resources, or do you mean the >> creation of conference bridges on the PBX? >yes, virtual telephone conference rooms created on the asterisk, more here: >http://www.voip-info.org/wiki/view/Asterisk+app_conference According to this conferences are created on-the-fly. I'm missing what exists to be controlled. When a conference is closed have it automatically pushed to the calendar with everyone who joined as a partcipant? I really wish our PBXs did that, would be endlessly useful.... But this would be an entirely asterisk side thing (but would belong in the docs plone!) >> Does Asterisk not support storing of messages in IMAP, or managing >> messages via IMAP? This is what Nortel's callpilot does, it is actually >a >> rather nice model. Perhaps someone could add this to Asterisk? Seems >like >> using the code based from a simple IMAP server it should be reasonably >> simply to overlay the Asterisk spool directory. This would give you >> something like 'real' unified messaging from any client, including OGO. >I have no idea whether I can do this with asterisk, maybe there is a branch >that enhances it that way, but I am not aware of any. That's what I mean: enhance asterisk. :) >> > - see whether other extensions are "online" (especially important for >> > mobile users with softphones) >> Again seems like a job for XMPP. >well, yes, xmpp presence could be checked too. I can't imagine an organization wanting more than one presence system/method. It seems like you'd want extensions to update their presence; and XMPP is a ubiquitous standard. From discuss@opengroupware.org Sat Apr 7 01:04:57 2007 From: discuss@opengroupware.org (Michael Brown) Date: Fri, 06 Apr 2007 20:04:57 -0400 Subject: [OGo-Discuss] CTI Integration In-Reply-To: <5430-SnapperMsg05076A73C23C8456@[75.212.34.1]> References: <20070406181151.0EB18393DA@l00-bugdead-prods.de> <5430-SnapperMsg05076A73C23C8456@[75.212.34.1]> Message-ID: <268-SnapperMsg8EFA1DC3C23CA9ED@[192.168.0.2]> ...... Original Message ....... On Fri, 06 Apr 2007 16:10:22 -0700 Adam Tauno Williams >But I'm confused by the term "asterisk mangement". I think an OGo bundle should be end-user >oriented, I don't see what an administrative interface would offer in addition to what is >already available. That's what I mean... End user account management. Call forwarding, extended absence greetings, voicemail management (listen, forward to another recipient, delete) greetings management, notification options, etc. HTH /Mike From discuss@opengroupware.org Sat Apr 7 07:44:25 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Sat, 07 Apr 2007 08:44:25 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070407064425.400D839422@l00-bugdead-prods.de> Hi, discuss@opengroupware.org wrote: > >what about like sth. for e-mail, the link to the asterisk managment bold > >written in the dock, > > If you mean bold if there is unread voice mail, yes, that would be cool. > yeah, exactly. > But I'm confused by the term "asterisk mangement". I think an OGo bundle should be end-user > oriented, I don't see what an administrative interface would offer in addition to what is > already available. yes, management is maybe the wrong term, right now I only have the end user as my target ;) but the users manage their very own voice-mail, telephone conferences... kind regards Sebastian From discuss@opengroupware.org Sat Apr 7 07:51:33 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Sat, 07 Apr 2007 08:51:33 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070407065133.E39B939551@l00-bugdead-prods.de> Hi, > > According to this conferences are created on-the-fly. I'm missing what > exists to be controlled. yeah, as these conferences can be created, configured and destroyed on the fly i mean, if the end user could control this, creation of conferences on the fly, without bothering the telephone system administrator, would be great. > > When a conference is closed have it automatically pushed to the calendar > with everyone who joined as a partcipant? I really wish our PBXs did that, > would be endlessly useful.... But this would be an entirely asterisk side > thing (but would belong in the docs plone!) I think at least creating an appointment in the database, when a user creates a virtual conference room, should be easy. I'll put this on my to-do list. > > >> Does Asterisk not support storing of messages in IMAP, or managing > >> messages via IMAP? This is what Nortel's callpilot does, it is > actually > >a > >> rather nice model. Perhaps someone could add this to Asterisk? Seems > >like > >> using the code based from a simple IMAP server it should be reasonably > >> simply to overlay the Asterisk spool directory. This would give you > >> something like 'real' unified messaging from any client, including OGO. > >I have no idea whether I can do this with asterisk, maybe there is a > branch > >that enhances it that way, but I am not aware of any. > > That's what I mean: enhance asterisk. :) oh, I just found out: with asterisk 1.4 it is already possible: http://www.voip-info.org/wiki/view/Asterisk+Voicemail+IMAP+storage nice, I only need to switch from asterisk 1.2x to 1.4x ;) Sebastian From discuss@opengroupware.org Sat Apr 7 08:36:09 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Sat, 07 Apr 2007 09:36:09 +0200 Subject: [OGo-Discuss] CTI Integration Message-ID: <20070407073609.94FED39551@l00-bugdead-prods.de> Hi all, as I am going to try to create a asterisk webui bundle (:, I just created this page in the docs UI: http://docs.opengroupware.org/Members/buzzdee/asterisk/AsteriskUI/document_view There the state of the actual work will be shown, a link pointing to the source in the bugzilla will be available too. Screenshots and documentation will be there too. comments are enabled at that page, so feel free to add comments, suggestions, ... there. well, might be more a question for the developers list, but as the whole thread is here: I need to parse the return values from the asteriks, they look like this, line by line: : I want to store the key:value pairs in a NSDictionary. What would be the best way to split the string on the space, then throw the colon away and save it in a NSDictionary? Any suggestions appreciated. happy easter Sebastian From discuss@opengroupware.org Sun Apr 22 18:25:46 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Sun, 22 Apr 2007 19:25:46 +0200 Subject: [OGo-Discuss] OGoAsteriskDialer and AsteriskUI Message-ID: <20070422172547.63CAC3C1C2@l00-bugdead-prods.de> Hi list, the last weeks I was working on trying to integrate my Asterisk system into the OGo WebUI. The outcome was the OGo Asterisk Dialer CTI plugin [1] and the AsteriskUI [2]. The Asterisk Dialer allows to click 'n dial from the WebUI using SkyDialNumber. It is tested and works at least with SIP phones. The AsteriskUI is separated into the OGoAsteriskCommands library, and the wobundles OGoAsteriskUI and OGoAsteriskVoiceMailInfo. OGoAsteriskCommands provides the interface to the Asterisk Management Interface. OGoAsteriskUI docks into the OGo WebUI. The page is separated by Tabs, the following tabs already show useful contents: * SIP accounts list * Voice Mail Information * Parked Calls list * Queues List The AsteriskUI also has a preferences page, allowing the user to make customizations. OGoAsteriskVoiceMailInfo provides Message Waiting Indication via a PopUp, and the Asterisk dock is bold in case voice mail messages are waiting in the asterisk. This functionality is copied from OGoMailInfo. There are still lots of known and unknown bugs in it, but as it already is useful for me, so I thought, maybe someone else will find it useful too. Questions, notes, problem reports, just post them here, or on the users list, or comment on the docs plone, at the links below. have fun Sebastian [1] http://docs.opengroupware.org/Members/buzzdee/asterisk/OGo%20Asterisk%20Dialer/document_view [2] http://docs.opengroupware.org/Members/buzzdee/asterisk/AsteriskUI/document_view From discuss@opengroupware.org Thu Apr 26 23:06:49 2007 From: discuss@opengroupware.org (Adam Tauno Williams) Date: Thu, 26 Apr 2007 18:06:49 -0400 Subject: [OGo-Discuss] Bug 1852: support creation of xmpp: field types in OGo In-Reply-To: <1174840812.8709.46.camel@ws01.whitemice.org> References: <20070325125449.789BD3D276@l00-bugdead-prods.de> <56A82A67-4DAC-4904-A77C-13A1F331F37A@opengroupware.org> <1174840812.8709.46.camel@ws01.whitemice.org> Message-ID: <1177625209.4935.1.camel@aleph.whitemice.org> > >>> Thinking about it, for the specific case of IM addresses we should > >>> really use the Outlook field in the way Microsoft uses it. Its sounds > >>> kinda stupid to reinvent the wheel here (how long before people ask > >>> about having IM addresses in Outlook/Evolution ...) Yea, why isn't that attribute encoded into the vCards, darn it!? :) > >> but I see only one im_address field in the company table, how is > >> Outlook > >> using it? Would it be possible to store an arbitrary amount of > >> arbitrary IM > >> accounts that way? > >Don't know, someone would need to check the exact behaviour. > I'll try to do that tomorrow. Using Zidelook this attribute is stored as a simple literal string; not a URL just exactly what was entered into the M$-Outlook contact panel. From discuss@opengroupware.org Fri Apr 27 01:50:45 2007 From: discuss@opengroupware.org (Adam Tauno Williams) Date: Thu, 26 Apr 2007 20:50:45 -0400 Subject: [OGo-Discuss] Bug 1852: support creation of xmpp: field types in OGo In-Reply-To: References: <20070325181103.CF3923D2BF@l00-bugdead-prods.de> Message-ID: <1177635045.4935.27.camel@aleph.whitemice.org> > To close the issue from my side, if you feel that its useful, please > commit it. After all the user has to configure the extended > attributes to enable the feature and do not get them automagically. I'm playing with this patch, and I have an extended attribute configured like: { defaultUrlScheme = "xmpp:"; key = "jabberid"; type = 20; } It works, at least 'technically' But - (a) The links rendered for XMPP are not actually compliant with RFC4622 [ http://www.ietf.org/rfc/rfc4622.txt ]. A link to send to an address from the default XMPP account should look like - xmpp:support@example.com?message - or at least that is how I interpret section: As an example, an XMPP IRI/URI intended to launch an interface for sending a message to the XMPP entity "example-node@example.com" might be represented as follows: xmpp:example-node@example.com?message Similarly, an XMPP IRI/URI intended to launch an interface for sending a message to the XMPP entity "example-node@example.com" with a particular subject might be represented as follows: xmpp:example-node@example.com?message;subject=Hello%20World It doesn't seam clear what a xmpp:{address} should actually do, unless I'm missing something. (b) I haven't been able to find/configure a browser/client combo that actually deals with an XMPP URL in the expected fashion. You can configure FF like: 1. Type "about:config" in the url bar 2. Right-click and select New->String 3. Enter "network.protocol-handler.app.xmpp" as the preference name 4. Enter the application to run - and enter the client (gaim, psi, etc...) as the handling application. But doing so doesn't seem to get you anything other than to start the application - which I can do from the "Start" menu. :) Any pointers on (b) would be appreciated. >From the XMPP RFC I think the best form for a XMPP URL is like - xmpp://guest@example.com/support@example.com?message - where guest@ is the user's IM address and support@ is the address you want to send to. Ideally I think the solution would be to add the imAddress attribute to the web interface and a Default to specify what type of link it should be (MSN, XMPP, etc...) or just be draconian and render it as XMPP. :) Then render the link, if XMPP, as xmpp://{user's imAddress}/{imAddress value}?message That seems like it would be straight forward to implement. From discuss@opengroupware.org Fri Apr 27 05:45:23 2007 From: discuss@opengroupware.org (Sebastian Reitenbach) Date: Fri, 27 Apr 2007 06:45:23 +0200 Subject: [OGo-Discuss] Bug 1852: support creation of xmpp: field typesin OGo Message-ID: <20070427044524.5F8CB3C94B@l00-bugdead-prods.de> Hi adam, > > (b) I haven't been able to find/configure a browser/client combo that > actually deals with an XMPP URL in the expected fashion. You can > configure FF like: > 1. Type "about:config" in the url bar > 2. Right-click and select New->String > 3. Enter "network.protocol-handler.app.xmpp" as the preference name > 4. Enter the application to run > - and enter the client (gaim, psi, etc...) as the handling application. > But doing so doesn't seem to get you anything other than to start the > application - which I can do from the "Start" menu. :) > > Any pointers on (b) would be appreciated. I started to implement that, to later find out, that konqueror/kopete are not able to handle these links :( Actually, I do not have a working combo. > Ideally I think the solution would be to add the imAddress attribute to > the web interface and a Default to specify what type of link it should > be (MSN, XMPP, etc...) or just be draconian and render it as XMPP. :) > Then render the link, if XMPP, as xmpp://{user's imAddress}/{imAddress > value}?message That seems like it would be straight forward to > implement. I'll take a look at it in the next days. It shouldn't be too hard to use the imAddress field instead of an extended attribute. I think it's a good idea to define a global default what kind of IM address should be stored in the imAddress field. If this default is not set, it could have xmpp as fall back IM Protocol. The Admin should be able to Define protocol dependent prefix and suffix, e.g.: imProtocol = xmpp; imProtoFields = { imPrefix = "xmpp://"; imSuffix = "?message..." } to render the IM field URL's. kind regards Sebastian