Ray (and Dave), I have created a patch which does exactly what you are asking for. This works, however there are other links that need to be fixed up potentially in the code base (wengo is well integrated into the server).
This patch is NOT a substitute for the CoIPManager as it does just the bare minimum. The main things this patch does is: 1) Turn off Wengo SSO, as this requires a web service to be built 2) Stores the config info from the SSO in the config file (can be modified in advanced settings, compile time, or install time) 3) User login now uses the sip user name, not an email address A couple other points to note: sip.usewengo.sso = true // uses wengo's servers, false uses the config's servers I'm not sure what the relationship between the following 3 settings is. In testing, I think the sip.address.server.host appears to be the end of the username, while the other two point to sip proxies, which is not what I would expect (Jerome, any thoughts?) I.e. [EMAIL PROTECTED], proxy sip.somesipserver.com would translate to: sip.auth.realm = "sip.somesipserver.com" sip.address.server.host = "somesipserver.com" sip.outbound.proxy.host = "sip.somesipserver.com" But please test. Also, have not extensively tested the wengo SSO version assuming someone wants to incorporate the patch. Also, references to WengoIDs may not make sense in your new client. You may have to modify some lang translation files, or educate your users. Hope this helps, -Lukas Lukas Oberhuber -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Neary Sent: 12 November 2006 09:29 To: Ray Jackson Cc: [email protected] Subject: Re: [Wengophone-devel] Custom Wengo Client Build? Hi Ray, Ray Jackson wrote: > I realise the NG client does not work with *other* SIP providers yet, > but how hard would it be to customise the client to talk to our own SIP > servers? Not very hard, I think, but Tanguy or Jérôme could probably give you a better idea. Making the wengophone work with other SIP platforms is a high priority for us, though, and if you would like to collaborate on that, I'd be thrilled. > Also, would it be acceptable to do our own custom build of the > Wengo client so that it uses our own platforms in NZ rather than the > Wengo service? Is this something that we could do and what limitations > would there be if we chose to offer our own custom Wengo based client? That would be fine. We would like to make sure that the wengophone is coherent in its branding, so if you want to ship it under a different name, then it would probably be best to rebrand completely - if you ship it as the wengophone, then please submit any patches that you make back here for approval. > As developers ourselves we are happy to contribute back any changes/new > features etc. to the project of course. Great! That's what the project's all about. Cheers, Dave. _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
SIPServerConfig.patch
Description: Binary data
_______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
