Hi,
I tried to use append_branch() with dst_uri and path parameters set (and using set_dst_uri() / set_path_vector() for the first message). It works well as long as only parallel forking is involved, but when I use serialize_branches and next_branches and serial forking is required, the information given in dst_uri and path is discarded. This also seems obvious when reading the code from serialize.c, which simply doesn't store it on the contacts[n]-structs. I could add it to the sturct, but I'm at a loss how to store/retrieve it from the AVP.
Are there any plans to fix this? Or any help on how I can fix it myself?
Regards, Daniel
Hi Daniel,
yes, that's an known limitation of the serialization process... the solution will be to store inside an AVP something more than string or int - maybe pointers or structures. This will allow a to store all branch info into AVPs for serial forking.
regards, bogdan
Frey, Daniel (external) wrote:
Hi,
I tried to use append_branch() with dst_uri and path parameters set (and using set_dst_uri() / set_path_vector() for the first message). It works well as long as only parallel forking is involved, but when I use serialize_branches and next_branches and serial forking is required, the information given in dst_uri and path is discarded. This also seems obvious when reading the code from serialize.c, which simply doesn't store it on the contacts[n]-structs. I could add it to the sturct, but I'm at a loss how to store/retrieve it from the AVP.
Are there any plans to fix this? Or any help on how I can fix it myself?
Regards, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Frey, Daniel (external)