Dave Neary wrote:
Hi Ray,
Ray Jackson wrote:
Can I just say what a superb job you guys are doing with the 2.2
release! I am running it against our SIP platforms here and it is
working great so far!
Thank you! What SIP platforms are you using?
A combination of open source platforms including Asterisk, Callweaver
and OpenSer currently.
By the way, is there any documentation on the sign-in procedures for
Wengo?
Not really, but it's quite simple - we put a php page on the server
which we connect to over https putting username & password in a POST,
and we get a very simple format back which gives us the SIP server, SIP
username other information back.
XML type response or just plain text? Is there a way I could grab an
example response or should I just read the source code?
I see you can brand the softphone and set it to login to our own
hosts which would be nice?
If you want to do single sign-on you'll probably need to hack something
up - you can change the string for the SSO URL and recompile, and if you
have the script respect the way we do things at Wengo, you should not
have a lot of work server-side. You may decide to do things differently,
though, in which case you'll probably need to do a bit more work.
To be honest, we would probably just stick with the standard SIP login
procedure for now as all our clients have real world phone numbers and
connect up using SIP. We don't have unique email address->phone number
mappings like Wengo so it probably wouldn't work for us.
Alternatively, it would be nice to have a
flag that turns off the Wengo style account option at startup and just
presents the SIP account settings - rather than clicking on 'Other' (for
Power users). Also, any docs/info on the SMS features and how we can
support this would be great.
You can currently (with the 2.2) put in a system config for the server
to connect to by default, then the initial connection screen just
becomes the way the person enters their SIP username and password.
For SMS, there isn't, as far as I know, a standard way to do them. We do
a POST to a server-side script which then does the work with the billing
platform.
Hmmm. I tried a few things but still can't get rid of the first choice
'Wengo account' or 'Other (Power Users)'. Once you click on Other it's
all good and the user only has to enter their phone number/password and
the other settings are automatically filled in from the config file. So
you believe there should be a way of hiding the Wengo style sign-in and
skip straight to the SIP login screen?
The HTTP Post for SMS would work for us. What variables should I expect
from the post and what are the expected responses for the Wengo phone?
Should I read the source?
I'm hoping to brand/skin our own version of Wengo for our clients to use
- but I'm happy to retain Wengo references throughout the softphone.
What are your recommendations/guidelines (keeping in mind GPL etc.) for
people who wish to brand/skin Wengo? Would you rather we remove all
Wengo references/logos or keep them in certain areas such as the 'About'
section for Copyright etc.?
The minimum would be, for me, to have "Based on the WengoPhone from
OpenWengo" in the About box. Other than that, I would simply like to
know so that I can reference you as a user of our technology, but if you
are making substantial changes to the code, then I'd appreciate it if
there were no obvious links to the WengoPhone in the interface -
rebranded is better.
I am happy to leave the About info as it is and also happy to promote
the OpenWengo project. I simply wanted to hide the 'Wengo-only' stuff
to avoid confusion for users. I don't plan to change any code unless I
absolutely need to. I would prefer to introduce config entries to hide
stuff in the interface rather than hack the source so I don't have to
keep patching each time a new version of Wengo comes along! I am a
developer myself but don't have lots of spare time at the moment but I'd
be happy to contribute what I can to your project - the same way I make
small contributions to several other Open Source projects.
By the way, can you tell me who your client is?
The softphone is for customers who have signed up to the 2 talk VoIP
service in New Zealand. We support many SIP compliant devices - mostly
phones/ATA's from Linksys, Asterisk trunks etc. but we do have quite a
few softphone users who currently use our 'recommended' softphone which
is X-Lite. I'd like to change that and provide our own branded
softphone based on Wengo which I think is far better with it's IM
integration and of course it's open source! We haven't made a final
decision yet on OpenWengo until we go through all our acceptance testing
but once we have made a decision to go with Wengo then I'd be happy for
you to use us as a reference for the technology.
Thank you!
Dave.
Cheers,
Ray
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
