Hello,

at least I narrowed it down a bit. It is empty also in the clone stored in transaction, so it happens either during cloning or before. I will have to check these parts.

Cheers,
Daniel

On 11/06/14 17:00, Igor Potjevlesch wrote:
Hello,

This is the result, always for frame 5 :

(gdb) p *t->uas.request->pai
$1 = {type = HDR_PAI_T, name = {
    s = 0x7f6a60cd34b8 "P-Asserted-Identity: \"0987654321\"<sip:0987654321@A.B.C.D>\r\nContact: <sip:0987654321@A.B.C.D:5060>\r\nAllow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, INFO, REFER, UPD"..., len = 19}, body = {
    s = 0x7f6a60cd34cd "\"0987654321\"<sip:0987654321@A.B.C.D>\r\nContact: <sip:0987654321@A.B.C.D:5060>\r\nAllow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE\r\nSupported: path,"..., len = 43}, len = 66, parsed = 0x7f6a6d81da88, next = 0x7f6a60cd3f10}
 
(gdb) p *((p_id_body_t*)(t->uas.request->pai->parsed))
$2 = {id = 0x0, num_ids = 0, next = 0x0}

Did you find one thing in common between the 2 occurrences? Do you have any ideas about what is the cause of this pai reset?

Regards,

Igor




2014-06-11 16:09 GMT+02:00 Daniel-Constantin Mierla <miconda@gmail.com>:
Hello,

in the same frame 5, can yo get:

p *t->uas.request->pai
p *((p_id_body_t*)(t->uas.request->pai->parsed))

Cheers,
Daniel


On 10/06/14 18:35, Igor Potjevlesch wrote:
Hello,

Here is the results :

(gdb) frame 5
#5  0x00007f6a687e9b43 in acc_onreply (t=0x7f6a60d16ff8, req=0x7f6a60cd2c10, reply=0x7f6a6c119aa8, code=200) at acc_logic.c:471
471                     acc_db_request(req);




-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda