[SR-Users] pua 'Could not convert temporary dialog into a dialog' error

2012-09-08 Thread Juha Heinanen
when testing presence/rls, i'm getting a pua error when presence server handles subscribe: Sep 8 20:36:12 siika /usr/sbin/pres-serv[22932]: INFO: Handling SUBSCRIBE Sep 8 20:36:12 siika /usr/sbin/pres-serv[22932]: INFO: Routing locally generated NOTIFY to Sep 8 20:36:12 siika /usr/sbin/pres

Re: [SR-Users] pua 'Could not convert temporary dialog into a dialog' error

2012-09-08 Thread Peter Dunkley
In order to cope with the scenario when a NOTIFY is received on a new dialog before the 2XX to the SUBSCRIBE, pua creates a temporary dialog (for the NOTIFY to match against) when it sends the SUBSCRIBE. This temporary dialog is converted to a full dialog when the 2XX is received (information such

Re: [SR-Users] pua 'Could not convert temporary dialog into a dialog' error

2012-09-08 Thread Juha Heinanen
peter, thanks for the explanation. i was using in rls db_mode=0 when i saw the error message. i then switched to db_mode=2 for rls just in case you had fixed something there and i haven't seen the error since then although i'm using mysql where your fix should not help. > The temporary dialog r

Re: [SR-Users] pua 'Could not convert temporary dialog into a dialog' error

2012-09-08 Thread Peter Dunkley
Hi, I only use PostgreSQL, so I'd have no way to test changes made to db_mysql (which is why I only added the APIs to PostgreSQL). That said, I don't believe it will be hard to do and most (if not all) of the PostgreSQL code should be re-usable (although some of the locking stuff might be Postgre