<div dir="ltr">Alexander,<div><br></div><div>Your capture has two packets, a MESSAGE from Ekiga to Opensips, and a 407 Proxy Auth Required reply from Opensips to Ekiga. When Ekiga tells you "NOTICE: Could not send message: Unauthorised", it's correct given the capture, but the real question is why Ekiga didn't try to use authentication at that point. Instead it just stopped and showed the error.</div><div><br></div><div>I can't speak any more to Ekiga; I've never tried it. If you're looking for other options, one may be Blink[1]. I've used it on Mac OSX with a lot of success. I've found its mailing list[2] to be active with prompt responses from the developers. </div><div><br></div><div>[1] <a href="http://projects.ag-projects.com/projects/documentation/wiki/Repositories">http://projects.ag-projects.com/projects/documentation/wiki/Repositories</a></div><div>[2] <a href="http://support.icanblink.com/">http://support.icanblink.com/</a></div><div><br></div><div><br></div><div>- Jeff</div><div> <br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 2, 2015 at 7:41 PM, Alexander Shukaev <span dir="ltr"><<a href="mailto:opensips@alexander.shukaev.name" target="_blank">opensips@alexander.shukaev.name</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">You are the Bo$$, Jeff. Exactly, that was the case. Although the data for the user registration was correct in Ekiga (and I also have no idea how the registration even passed), I decided to simply deregister and register again. As a result, I can now call from Ekiga to Linphone too, but there is a still a problem with IM, a different one though. Now Ekiga reports "NOTICE: Could not send message: Unauthorised" for IMs, and now I also understand why (thanks to your previous response): it does not send "Proxy-Authorization" anymore (see the attachment)! I begin to think that Ekiga is merely bugged, though I've heard lots of positive reviews on it, including facts that it can be considered a mature piece of software. So I still hope that this could be my misconfiguration on the OpenSIPS side and if anybody can point me to it, I'd be very grateful. Otherwise, I guess I better off with another softphone client anyway.<br>
<br>
Kind regards,<br>
Alexander<span class=""><br>
<br>
On 02.11.2015 21:54, Jeff Pyle wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">
Alexander,<br>
<br>
First, let me say I do not use Opensips for instant message or related<br>
operations. Looking at your capture, however, I may have a thought.<br>
Let's look at the headers from Ekiga's authenticated MESSAGE:<br>
<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
U 2015/10/31 13:02:54.844064 <a href="http://192.168.2.109:5060" rel="noreferrer" target="_blank">192.168.2.109:5060</a> [1] -><br>
<a href="http://127.0.0.1:5060" rel="noreferrer" target="_blank">127.0.0.1:5060</a> [2]<span class=""><br>
<br>
MESSAGE <a href="mailto:sip%3A5678@127.0.0.1" target="_blank">sip:5678@127.0.0.1</a> SIP/2.0.<br>
<br>
CSeq: 17 MESSAGE.<br>
<br>
Via: SIP/2.0/UDP<br>
<br>
</span></blockquote>
192.168.2.109:5060;branch=z9hG4bK4ef094e5-5e7e-e511-8953-0008cafa0605;rport.<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
User-Agent: Ekiga/<a href="http://4.0.1." rel="noreferrer" target="_blank">4.0.1.</a> [3]<br>
<br>
From: <<a href="mailto:sip%3A5678@127.0.0.1" target="_blank">sip:5678@127.0.0.1</a> [4]>.<div><div class="h5"><br>
<br>
Call-ID: 868b94e5-5e7e-e511-8953-0008cafa0605@G75VW.<br>
<br>
To: <<a href="mailto:sip%3A5678@127.0.0.1" target="_blank">sip:5678@127.0.0.1</a>>.<br>
<br>
Proxy-Authorization: Digest username="1234", realm="127.0.0.1",<br>
nonce="5634f45c0000000f04ee114e87bbede48ba1228797acae09",<br>
uri="<a href="mailto:sip%3A5678@127.0.0.1" target="_blank">sip:5678@127.0.0.1</a>", algorithm=MD5,<br>
response="4f5373eb311376dad81cfae2e5122423".<br>
<br>
Expires: 5000.<br>
<br>
Content-Length: 2.<br>
<br>
Content-Type: text/plain;charset=UTF-8.<br>
<br>
Max-Forwards: 70.<br>
</div></div></blockquote><div><div class="h5">
<br>
The From header says your Ekiga is configured with 5678, but you're<br>
trying to authenticate as 1234 (Proxy-Authorization header). I<br>
believe that is why Opensips returns a 403 Forbidden Auth ID in the<br>
subsequent packet. You probably want 1234 in the From header since it<br>
appears you're trying to send the message to 5678. Perhaps this is a<br>
misplaced value in Ekiga's configuration. I'm surprised you're able<br>
to completely a registration.<br>
<br>
Or, I could be completely wrong. As I mentioned, I don't do IM over<br>
SIP.<br>
<br>
- Jeff<br>
<br>
On Mon, Nov 2, 2015 at 2:49 PM, Alexander Shukaev<br>
<<a href="mailto:opensips@alexander.shukaev.name" target="_blank">opensips@alexander.shukaev.name</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Apologies, I don't want to look like a nasty bumper here, but I<br>
can't believe that nobody has a slightest idea how to approach the<br>
problem. I would be grateful even for a link to mailing<br>
list/forum/community where I could find help with this.<br>
<br>
Regards,<br>
Alexander<br>
<br>
On 31.10.2015 18:14, Alexander Shukaev wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hello everyone,<br>
<br>
I'm testing a new setup of OpenSIPS. I have created two accounts<br>
in<br>
DB: 1234 and 5678. I run both, Ekiga and Linphone, to test<br>
communication between these two accounts. So through Ekiga, I<br>
register 1234 and add 5678 to contacts, while through Linphone, I<br>
register 5678 and add 1234 to contacts.<br>
<br>
There are two problems that I experience. First of all, within<br>
Linphone I can do both, IM and call from 5678 to 1234 (Ekiga), and<br>
in<br>
Ekiga I can read those IMs and accept calls accordingly, while<br>
within<br>
Ekiga I can neither IM nor call from 1234 to 5678 (Linphone) as<br>
for<br>
IMs I get "NOTICE: Could not send message: Forbidden" (for calls I<br>
assume it's the same error, though not shown). I attach the<br>
corresponding Wireshark log. Secondly, even though I can IM from<br>
Linphone to Ekiga, the result is strange. In particular, each IM<br>
arrives twice to Ekiga. In other words, in Linphone I see the IM<br>
being typed once into chat, while in Ekiga I get two notifications<br>
for<br>
each IM and that each IM appears two times in the chat.<br>
<br>
I'm new to OpenSIPS and VoIP in general, and I have no idea how to<br>
deal with these quirks. Any help is greatly appreciated. Thanks<br>
in<br>
advance.<br>
<br>
Regards,<br>
Alexander<br></blockquote></blockquote></div></div></blockquote></blockquote></div><br></div></div></div>