Hello,
soon we should sketch the roadmap for the next major release 3.2. There
are some private git branches with lot of work on it, so we need to
synchronize a bit and decide about the proper time: before or after summer.
Several devels will be in Berlin for Linuxtag, but no so much
overlapping for a big face to face meeting, therefore might be better to
have a IRC chat conference sometime in the near future. Next week will
be fine for me, say Wednesaday till Friday, in the afternoon to allow
fair time of the day for US timezones.
If you have other proposals, speak up.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Iñaki Baz Castillo (ibc)
Attached to Project - sip-router
Summary - Error parsing Via parameter with space before semicolon
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - Very Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - The following valid Via causes a parsing error:
Via: SIP/2.0/UDP 1.2.3.4;branch=z9hG4bK1aaaaa;rport;param1 ;param2<CRLF>
It occurs due to the space before ";param2".
If param2 has value (param2=abc or param2 = abc) the error also occurs.
According to RFC 3261 BNF the above Via is 100% valid as header parameters separator is SEMI which is defined as:
SEMI = SWS ";" SWS
SWS = [LWS]
LWS = [*WSP CRLF] 1*WSP
WSP = SP | HTAB;
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=127
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A user has added themself to the list of users assigned to this task.
FS#127 - Error parsing Via parameter with space before semicolon
User who did this - Iñaki Baz Castillo (ibc)
http://sip-router.org/tracker/index.php?do=details&task_id=127
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi Peter,
thank you very much for the suggestion. In fact, with the XHTTP_AUTH enable,
SIP Communicator (JITSI) doesn’t work with XCAP of Kamailio. With the
XHTTP_AUTH comment out. The Presence authorization finally works, but
partially.
When bob add alice as a contact, there is a authorization request popup to
alice, and alice click accept, then the auth req result popup appear to
alice saying the bob has accepted the request! After that, bob can see the
presence status of alice correctly. But alice always see the bob is offline.
In the xcap table, we see there is an entry in the rls (contact alice in the
user bob entry) and another entry in the presence rules (contact alice in
the user bob entry).
But when I try to add bob as a contact from alice, nothing happen, there is
no popup of authorization request to bob. And alice always see the bob is
offline. Any idea?
Thank you very much.
Best Regards,
Laura
> Message: 2
> Date: Tue, 19 Apr 2011 10:17:34 +0100
> From: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
> Subject: Re: [sr-dev] Presence problem
> To: Development mailing list of the sip-router project
> <sr-dev(a)lists.sip-router.org>
> Message-ID: <1303204654.4056.10.camel@pd-laptop-linux>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Laura,
>
> I have recently been testing presence with Kamailio as well.
>
>
> > - The change status of the presentity is immediately visible
> > by watcher with the only exception, when the user goes offline, the
> > presentity keeps online in the watcher buddy list, any idea? Can you
> > help me?
> >
>
> I have had the same issue with clients I was testing with. In my case
> it turned out to be problems with the client.
>
> You should take a LAN trace from the client side and check that the
> client logging out is properly updating presence status on log-out. If
> that is OK, then take a trace on the client still logged in, it could be
> that the client is receiving the status update but not displaying it.
>
>
> >
> > The xcap table is empty. Do I need to configure also the xcap table?
> > Or it?s automically done by kamailio presence server?
> >
>
> The xcap table will be empty for new subscribers. When the client
> requests a document (of supported type) from Kamailio that is not on the
> server it will get a "404 Not Found" response. The client should then
> create a new document (with sensible defaults for the client) on the
> server using an HTTP PUT.
>
> If the client requests a document that is not of supported type Kamailio
> will return a "500 Server Error" response and the client should continue
> (if it can) without support for that document.
>
> During my testing I came across a client that didn't support HTTP
> authentication properly, so when Kamailio responded with a 401 the
> client gave up instead of authenticating. Disabling HTTP authentication
> (take out the "#!define WITH_XHTTPAUTH" line in kamailio.cfg).
>
> Regards,
>
> Peter
>
> --
> Peter Dunkley
> Technical Director
> Crocodile RCS Ltd
>
Hi,
we are trying to setup a Kamailio as a SIP/SIMPLE presence server for chat
based on the guide published in SIP SIMPLE Presence Made Simple with
Kamailio 3.1.x on the site:
http://kb.asipto.com/kamailio:presence:k31-made-simple.
The OS we are using is Linux RHEL 5.6 x64 and MYSQL as Database.
We found some strange behaviors of the Kamailio basic presence, presence
rules functionalities. As suggested in the guide we created 2 users (Alice
and Bob) and both the latest jitsi (SIP communicator) to test it. The test
scenario is following by using either UDP or TCP protocol:
- Alice add the Bob as a contact
- Bob add the Alice as a contact
- Alice change presence status
- Bob change presence status
- Alice send IM to Bob
- Bob send IM to
- Alice put the status offline
- Bob put the status offlice
First, test the configuration without XCAP server load:
- WITH_XCAPSRV is not defined
- Use implicit presence rule modparam("presence_xml",
"force_active", 1) (from my understanding, without xcap we can only use
implicit presence rule without any authorization for the subscription
Result:
- Add contact is ok and the presence status is immediately visible
(because force_active = 1)
- The change status of the presentity is immediately visible by
watcher with the only exception, when the user goes offline, the presentity
keeps online in the watcher buddy list, any idea? Can you help me?
Second, test the configuration with XCAP server load and the configuration
is the same of the guide:
- WITH_XCAPSRV is defined
- Use implicit presence rule modparam("presence_xml",
"force_active", 0)
- modparam("presence_xml", "integrated_xcap_server", 1)
Result:
- When Alice add the Bob as a contact, there is no popup to ask the
Bob authorization immediately.
- When Bob change the presence status, Alice dosen’t see the
change(offline), but they can exchange IM.
- When Alice goes offline, the popup of the authorization request
of the Alice is appear to Bob, Bob accept the request
- When Alice come on line again, the same behavior, Alice always
see Bob is online even Bob change his status.
- When Alice goes offline again, the Authorization Request come up
again to Bob just like Bob even Bob has accepted the request before. Very
strange
When we configured the kamailio with XCAPSRV and enable the xcap also in the
SIP communicator as suggested by the guide, we got the following error in
/var/log/messages when alice goes online:
Apr 18 16:35:01 kamailio3p1 /usr/sbin/kamailio[7561]: ERROR: <script>: =====
xhttp: resource-lists : sip:alice@10.10.5.214
Apr 18 16:35:01 kamailio3p1 /usr/sbin/kamailio[7561]: ERROR: <script>: =====
xhttp: get sip:alice@10.10.5.214 => /xcap-root/resource-lists/users/
sip:alice@10.10.5.214/index
Apr 18 16:35:01 kamailio3p1 /usr/sbin/kamailio[7562]: ERROR: <script>: =====
xhttp: pres-rules : sip:alice@10.10.5.214
Apr 18 16:35:01 kamailio3p1 /usr/sbin/kamailio[7562]: ERROR: <script>: =====
xhttp: get sip:alice@10.10.5.214 => /xcap-root/pres-rules/users/
sip:alice@10.10.5.214/presrules
The xcap table is empty. Do I need to configure also the xcap table? Or it’s
automically done by kamailio presence server?
Any idea? Maybe we have wrong configuration or is it a bug of kamailio?
Thanks and Best Regards,
Laura
Hello,
I am using Kamailio RLS and integrated XCAP Server. When I add a
contact with my client it updates my XCAP documents but there is no
additional SIP messaging between the client and Kamailio.
I have been assured (by the client author) that this is the correct
behaviour. However, having looked at both the XCAP Server and RLS
module code I cannot see anything that will either inform RLS that a
document has been updated or a timer to check for that.
Have I missed something obvious?
Thanks,
Peter
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd