Hi, I'm evaluating WengoPhone in my company (we use Asterisk for now).
I've installed it to five members of a department in my company. They use the
Windows 2.1 version, so be sure I'll report their experience and issues
here ;)
But for now, I have some features request.
First of all note
Hi Dave - maybe I'm only failing in the configuration. In the Account
settings, there are the following fields:
login/username: I guess this is the username in the SIP AoR (public SIP URI)
Password: the password
SIP Domain/Realm: I guess this is the domain part in the SIP AoR (public
SIP
Hi Iñaki,
Iñaki Baz Castillo wrote:
- SIP blind and attended transfer. This is essential in my company (and in
any
one), and I can't imagine why OpenWengo doesn't include it (or maybe I'm
wrong?).
Can you describe the feature please? I don't know what either attended
transfer or SIP
Hi,
When adding the new Jabber account wengophone2.2 terminates at line 54 of
QtJabberSettings.cpp
54 _ui-useTLSCheckBox-setChecked(params.isJabberTLSUsed());
Function isJabberTLSUsed())
bool IMAccountParameters::isJabberTLSUsed() const {
return
El Thursday 12 July 2007 12:19:01 Dave Neary escribió:
Hi Iñaki,
Iñaki Baz Castillo wrote:
- SIP blind and attended transfer. This is essential in my company (and
in any one), and I can't imagine why OpenWengo doesn't include it (or
maybe I'm wrong?).
Can you describe the feature
This is a Columbia.EDU development
They have integrated it with OpenWengo for Windows and
Linux. The executables and instructions can be downloaded from:
http://www1.cs.columbia.edu/~dc2378/setupp2pp.html
http://www1.cs.columbia.edu/%7Edc2378/setupp2pp.html
Please visit Columbia.edu
Le Jeudi 12 Juillet 2007 13:31, Grzegorz Siemek a écrit :
Hi,
When adding the new Jabber account wengophone2.2 terminates at line 54 of
QtJabberSettings.cpp
[snip]
which thus throws LOG_FATAL wiht message that jabber.use_tls key does'nt
exist.
The same result is when adding other IM
Hi,
I would like to know whether wengochat application from trunk is
functional.
I compiled a trunk version, but when I try wengochat I get only a Log
window and application stucks.
It is worth to mention that I have 4.2.3 version of QT.
The log that I get :
(debug) static std::listvoid*,
In the wengophone Trac is really difficult to categorize a bug or request
because the amount of options that it offers.
For example:
- What is the difference between Component and Functional component?
- Why there appear in Version options as WengoPhone 2.2.X and NG? Isn't
the 2.2.X version a
Le Jeudi 12 Juillet 2007 15:51, Aurélien Gâteau a écrit :
Le Jeudi 12 Juillet 2007 13:31, Grzegorz Siemek a écrit :
Hi,
When adding the new Jabber account wengophone2.2 terminates at line 54 of
QtJabberSettings.cpp
[snip]
which thus throws LOG_FATAL wiht message that jabber.use_tls
El Thursday 12 July 2007 16:58:25 Charles B. Schiele escribió:
Couldn't call transfers, etc., be handled by dialing feature codes? With
proper configuration of feature codes in Asterisk (* codes) you can
configure any endpoint to inform the server to handle the SIP REFER stuff.
I know
Hi Iñaki,
Iñaki Baz Castillo wrote:
In the wengophone Trac is really difficult to categorize a bug or request
because the amount of options that it offers.
I agree with you, and step by step, I'm working on improving things.
For example:
- What is the difference between Component and
[EMAIL PROTECTED] wrote:
OK good, valid information, Iñaki... - my response:
1) I agree - as far as good SIP proxy for SIP agents, asterisk could
vastly improve - and OpenSER etc. are likely a better choice... AND that,
clearly the best way to do this is using a native SIP Referral... But
2)
13 matches
Mail list logo
