If it is using OPAL, then Ekiga should behave the same way. I'll try
that path.
On 03/29/2012 03:09 PM, Jan Fricke wrote:
Joegen,
just got the gaitronics ruggedized phone for evaluation. Don’t know if
they might give you an evaluation to get it working with Sipx/OpenUC.
I took the Www-Authenticate Header with nonce from a 401 in a pcap
file. Put that header into a method that usually calculates
Authorization header with response for a tool we wrote that can
subscribe presence (rls) from sipx. The response of our method was not
equal to the response of the gaitronics. But would not say this or
that device makes something wrong. Any other ideas how I could debug
this further without stepping through sipx code?
The Gaitronics hardware is really nice by the way, and I think the
phone will perform well after it is registered. Would like to see this
work on SipX. I’ve seen a document with open-source licenses
mentioned. The phone seems to use OPAL as voip api (adam: correct me
if I’m wrong). If this is correct I’d expect a nice behavior when it
is registered.
Jan
_____________________________
Jan Fricke (B.Sc.)
*IANT -
APPLIED NGN-TECHNOLOGIES
**Turn-Key VoIP/UC Solutions and More...
*Fon: +49 (5331) 6794 0
Fax: +49 (5331) 6794 499
Mail: [email protected] <mailto:[email protected]>
Web: www.iant.de <http://www.iant.de/en/startseite>
IANT is eZuce <http://www.ezuce.com/> Elite Partner for EMEA
IANT is Member of GROUPLINK <http://www.grouplink.de/>
*Von:*Joegen Baclor [mailto:[email protected] <mailto:[email protected]>]
*Gesendet:* Mittwoch, 28. März 2012 17:15
*An:* Jan Fricke
*Cc:* Discussion list for users of sipXecs software; Adam Newman
*Betreff:* Re: AW: [sipx-users] Backward Compatibility for "qop"
Jan,
Thanks. May I know what client you are using to test? Is it
something that I can have posession of?
"SipMessage::parseQopValue - no qop value found" is something that I
expect.
Response auth hash does not match (bad password?) is the thing that
needs to be looked at
Joegen
On 03/28/2012 08:37 PM, Jan Fricke wrote:
Hi,
here it is.
Authentication is around line 3708. Demo user 300 password asdf. Phone
ip 10.99.149.203. SipX ip 10.99.10.9.
There are at least two interesting lines in the registrar log.
"SipMessage::parseQopValue - no qop value found"
And …Response auth hash does not match (bad password?)…
I’m 100% sure that the password in sipx and also in the phone is asdf.
Jan
*Von:*Joegen Baclor [mailto:[email protected] <mailto:[email protected]>]
*Gesendet:* Mittwoch, 28. März 2012 13:47
*An:* Discussion list for users of sipXecs software
*Cc:* Jan Fricke; Adam Newman
*Betreff:* Re: [sipx-users] Backward Compatibility for "qop"
Hi,
can we have the debug level log of the proxy and registrar for this?
joegen
On 03/27/2012 10:34 PM, Jan Fricke wrote:
Hi,
I installed a 4.4 64-bit test system from 287 iso, yum updated it, set
repo to staging and yum updated again.
Sipxproxy is now at release 374.g2acd4. But unfortunately it does not work
(pcap attached). Does this release contain the patch posted here before?
Do I have to set some option in the proxy settings?
Sincerely
Jan
_____________________________
Jan Fricke (B.Sc.)
IANT -
APPLIED NGN-TECHNOLOGIES
Turn-Key VoIP/UC Solutions and More...
Fon: +49 (5331) 6794 0
Fax: +49 (5331) 6794 499
Mail:[email protected] <mailto:[email protected]>
Web:www.iant.de <http://www.iant.de>
IANT is eZuce Elite Partner for EMEA
IANT is Member of GROUPLINK
-----Ursprüngliche Nachricht-----
Von:[email protected]
<mailto:[email protected]>
[mailto:[email protected]] Im Auftrag von Douglas
Hubler
Gesendet: Montag, 26. März 2012 18:18
An: Discussion list for users of sipXecs software
Betreff: Re: [sipx-users] Backward Compatibility for "qop"
On Mon, Mar 26, 2012 at 7:12 AM, Douglas Hubler<[email protected]> <mailto:[email protected]> wrote:
On Sun, Mar 25, 2012 at 2:04 PM, Adam Newman<[email protected]>
<mailto:[email protected]>
wrote:
I would be delighted if you could send me the patch for testing.
I should have patch and instructions later today. We're simply pushing
the rpms to 4.4 stage directory.
RPMs are in
http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/
You need to edit
/etc/yum.repos.d/sipxecs.repo
with appropriate url and perform a yum update on at least sipx
yum update 'sipx*'
_______________________________________________
sipx-users mailing list
[email protected] <mailto:[email protected]>
List Archive:http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected] <mailto:[email protected]>
List Archive:http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
