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

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 as to-tag is filled in). This error occurs when a matching temporary dialog can't be found in the hash table (or DB if in DB only mode). The temporary dialog record cannot be created until after the SUBSCRIBE has been sent (the call-id and from-tag are generated by the TM module). This means, on a single server with RLS back-end subscriptions over the local loopback, it is theoretically possible for the SUBSCRIBE to be sent and the 2XX generated, sent, received, and processed before the temporary record is created. This is much more likely to happen when using DB only mode than when using the in-memory hash (in fact, it was added and tested before the DB only mode changes and I never observed it happening with the in-memory hash). If you are using DB only mode there is a fix for this. The new (start|end|abort)_transaction() and query_lock() DB APIs are used in pua to prevent this problem. However, these DB APIs are only supported by db_postgres at the moment. Regards, Peter -- Peter Dunkley Technical Director Crocodile RCS Ltd