5 Feb
2008
5 Feb
'08
12:09 p.m.
On 02/05/08 12:52, kokoska rokoska wrote:
I would like to have patch for 1.3.0 too :-)
thanks for volunteering to test. Here is the attached patch. Let me know
if works so I can commit on SVN.
Cheers,
Daniel
Thanks, regards
kokoska.rokoska
Daniel-Constantin Mierla napsal(a):
There is bug mistakenly introduced about 2 years
ago, if I could spot it
right on the svn log. A wrong variable for registrar address was used. I
have just made a commit on trunk. Can you test and let me know if works
now? If you need patch for 1.3 I can send it to you -- I will backport
after some testing is done.
Thanks,
Daniel
On 02/05/08 11:37, Iñaki Baz Castillo wrote:
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
On Tuesday 05 February 2008 10:08:16 Dan-Cristian
Bogos wrote:
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
Iñaki,
it looks like I have misunderstood your problem.
I was speaking about "202 Accepted" confirmation and not a new MESSAGE.
Yes, that was what I meant ;)
Why would you need a new message?
Because it's the only way that any UAC will show the notification to
its user.
For example:
- If X-Lite sends a MESSAGE and it's stored and replied by proxy with "202
Accepted" then XLite UI will show nothing to the user, but message correctly
received by destination, so he will think that the destinaiton is ireceiving
him messages but ignoring them.
- If the message is stored and proxy replies "404 User Not Found, MEssage
Stored" then XLite will just show in the UI: "404 User is not online".
- Twinkle will not show the code description for a 202, but it will do it in a
negative reply (404 for example), but Twinkle IM is not very advanced yet in
usability terms.
Best regards.