Re: [GnomeMeeting-devel-list] Problems with gnomemeeting-snapshot (opal) and SIP-Provider web.de
- From: "Damien Sandras" <dsandras seconix com>
- To: "GnomeMeeting development mailing list" <gnomemeeting-devel-list gnome org>
- Cc: craigs postincrement com
- Subject: Re: [GnomeMeeting-devel-list] Problems with gnomemeeting-snapshot (opal) and SIP-Provider web.de
- Date: Thu, 14 Jul 2005 20:01:57 +0200 (CEST)
Jonita will probably kill me. I found the bug and a fix but I can not
commit that fix, nor produce the exact code to fix the problem, but I
think Craig can do it.
Craig, in src/sip/sipcon.cxx, find method
"OnReceivedAuthenticationRequired". At the end of the method, we have this
// Restart the transaction with new authentication info
remotePartyAddress = targetAddress.AsQuotedString(); // start with a new
This line is there to start with a fresh To field, without any tag present
or parameter which would have been added by the answers to the first
unauthenticated INVITE. The problem, is that when you are using an
outbound proxy, the targetAddress is the address of that outbound proxy,
which is not necessarily the same as the remotePartyAddress (here :
outbound proxy = sip.web.de, but remotePartyAddress = something web de).
So the fix is to start with a fresh to tag without changing the
remotePartyAddress. It should be easy to do but I'm connected with a
dialup, and in "honeymoon".
Craig, can you have a quick look at this? Jorge, can you test the fix?
> I'm still away, as part of my honey moon, so I can not fix your problem
> and I can not try reproducing it. However, I can explain it :
> - you are using sip.web.de as outgoing proxy
> - OPAL is sending a first INVITE PDU with the correct To: field
> - the proxy requests authentication
> - OPAL sends an authenticated INVITE PDU, but the To: field is not
> correct, it doesn't reprensent the called party
> - the proxy accepts the call and sends a 200 OK answer with an incorrect
> Contact: field which is created from the incorrect To: field sent by OPAL
> - OPAL sends an ACK with a status line corresponding the Contact: field of
> the 200 OK PDU, which is incorrect.
> That's the reason why it fails. I'm not sure, but it could be related
> to the fact that sip.web.de is used as "outbound proxy". Perhaps Craig can
> have a look, I hope so, as I'm still away for at least 2 weeks.
>> I try to use my VOIP-Account at web.de with gnomemeeting but fail.
>> A test with kphone was successful.
>> Problem description:
>> Registration works, Incoming calls work, but outgoing fails.
>> sip proxy/outgoing proxy: sip.web.de
>> realm: web.de
>> username: USERNAME
>> Attached you will find to debug outputs, one from gnomemeeting and one
>> from kphone. I replaced my username with USERNAME, my IP with
>> MYCURRENTIP, and crippled the called number.
>> gnomemeeting establishes a connection with the sip proxy, but the only
>> thing I get is a anncouncment that the called number is not registered,
>> with kphone it just works.
>> Jï¿½rg Friedrich
>> There are only 10 types of people:
>> Those who understand binary and those who don't.
>> Gnomemeeting-devel-list mailing list
>> Gnomemeeting-devel-list gnome org
> Gnomemeeting-devel-list mailing list
> Gnomemeeting-devel-list gnome org
] [Thread Prev