>> Hello
>>
>> I try to capture the information with Ethereal on Windows. I am not sure
>> which XML is looked after. To my knowledge, there is a config.XML on
>> local
>> drive under "my documents" on Windows. It has some information about
>> user
>> ID
>> and proxy server. But the registrar server is hardcoded in program.
>> Could
>> you shed some lights how the registrar protocol works in Wengophone?
>>
>> thanks!
>> steven
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] Behalf Of Anban
>> Mestry
>> Sent: Monday, August 28, 2006 12:10 AM
>> To: Anban Mestry
>> Cc: [email protected]; Leonardo Jos?Reyes Diago
>> Subject: Re: [Wengophone-devel] WengoPhone configuration
>>
>>
>> Anban Mestry wrote:
>>> Klaus Darilion wrote:
>>>> Gianluca Sforna wrote:
>>>>> On 8/24/06, Klaus Darilion <[EMAIL PROTECTED]> wrote:
>>>>>> You can reverse engineer by blocking the https port. openwengo will
>>>>>> fallback to http and you can use a packet sniffer to analyze the XML
>>>>>> provisioning format.
>>>>>>
>>>>>
>>>>> Considering this is an Open Source project, that sounds quite
>>>>> overkill...
>>>>
>>>> Reverse Engineering is done in 10 minutes (blocking https port under
>>>> Windows can be easily done using the netdefender firewall).
>>>>
>>>> Writing an XLM file an put it on a webserver: 10 minutes
>>>>
>>>> That is nothing compared to writing your own sip client :-)
>>>>
>>>> Of course it would be best if these reverse engineered XML profile is
>>>> published at the wiki, and the provisioning URL is a config option
>>>> which can be changed without recompiling.
>>>>
>>>> regards
>>>> klaus
>>>> _______________________________________________
>>>> Wengophone-devel mailing list
>>>> [email protected]
>>>> http://dev.openwengo.com/mailman/listinfo/wengophone-devel
>>>>
>>> Apologies for the double post. Google made me do it. I was going to
>>> say Chuck made me do it...but its getting kinda tired...
>>> hi,
>>>
>>> I had the same experience. Yes you can reverse engineer it using
>>> ethereal and http -- its not too difficult . You can also see the XML
>>> output when typing the url into your browser when logging into your
>>> openwengo account (jgi on the irc chan gave me the url...it was a
>>> while back...i'll look for it :) ) -- looking at the XML output is
>>> much easier in my opinion. I also remember in the classic version the
>>> XML authorization classes...if you have a look at those file you can
>>> see what XML tags wengo is looking for... haven't really looked at ng
>>> though. Hope that helps in whatever weird way ;)
>>>
>> Ok I found the script that I wrote to authenticate my server with
>> CLASSIC ( have no clue if it is going to work with NG...at all)... it
>> works with classic
>>
>> You can find it here http://pastebin.ca/151640 ...please let me know if
>> it works with NG...and if it doesn't...like...how is it different?
>>
>> ok bye
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>> _______________________________________________
>> Wengophone-devel mailing list
>> [email protected]
>> http://dev.openwengo.com/mailman/listinfo/wengophone-devel
>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>>
>
> Word yo.
>
> Ok, I assume that when you're using Ethereal, you're doing so when logging
> into your wngo account with https disabled right? If so you should be able
> to see ... wait a second...
>
> look here: http://pastebin.ca/153644 <-- this is the file
> WengoAccountParser.h -- I haven't tried this but this seems like the way
> the authentication and configuration works.
>
> Please let me know if this is correct .... :)
>
>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
Word yo again,
so this is what I get, which seems to be similar/exactly what I've said
before.... apologies for the uncessary post :)
sso vapi="1">
<status code="200">OK</status>
<user>anbanm</user>
<userid>anbanm</userid>
<displayname>anbanm</displayname>
<password>lol</password>
<outbound>1</outbound>
<realm>voip.wengo.fr</realm>
−
<proxy>
<host>213.91.9.216</host>
<port>5060</port>
</proxy>
−
<server>
<host>voip.wengo.fr</host>
<port>5060</port>
</server>
−
<httptunnel>
<host>httpproxy.wengo.fr</host>
</httptunnel>
</sso>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
