Hi ,
I am using SIGCOMP to compress/decompress SIP application. SIP Client is uploading UVDM bytecode in all messages it sends to server (Not stateful) . Below is the message exchange between SIP Client and Server, Client Server 1) REG (Client sends bytecode) ----> (2) <---- 401(Server sends byte code) 3) REG (Client sends bytecode) ----> (4) <----- 200 OK (Server sends byte code) 5) SUBSCRIBE (Client sends bytecode)-----> (6) <----- 200 OK (Server sends partial state identifier ) After decompressing message (4).. SIP Client creates state having state identifier (SHA1 result) and stores it as a state item.. Also at (4), Server asks to create state using Partial Id, what does partial state id signify here during state create ?? [-]UDVM execution trace no_of_state_create 3 ### Creating state ### Partial state identifier: AEDBAB80652A ### Creating state ### Partial state identifier: AAA2B32CE212 ### Creating state ### Partial state identifier: As mentioned above, for 200 OK REGISTER, SIP Client creates state having state identifier (SHA1 result) which does not match with either AEDBAB80652A or AAA2B32CE212.. Should they match ??? Why is server asking to create state giving partial state identifiers ??? Now, at (6).. 200 OK to SUBSCRIBE, Server references a partial state identifier AEDBAB80652A, which does not match with any of the state identifiers stored with SIP Client.... and as a result SIP Client fails to decompress this 200 OK to SUBSCRIBE. [-]Signaling Compression Returned_feedback item: 03 Partial state identifier: AEDBAB80652A Remaining SigComp message bytes: 280 ### Accessing state ### Partial state identifier: AEDBAB80652A It is expected from Client to successfully decompress message (6).. Please help to identify the issue. Regards, Kishore _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
