while trying find out, why sip-router produces mysql "out of sync" errors, i discovered that msilo m_dump only recognizes that register request is un-register request, if it has expires header with body 0. it is not checking if contact header has expires=0 parameter like this:
Contact: sip:jh_test_fi@192.98.101.10:5074;transport=udp;expires=0
-- juha
Hello,
On 06/06/2009 02:30 PM, Juha Heinanen wrote:
while trying find out, why sip-router produces mysql "out of sync" errors, i discovered that msilo m_dump only recognizes that register request is un-register request, if it has expires header with body 0. it is not checking if contact header has expires=0 parameter like this:
Contact: sip:jh_test_fi@192.98.101.10:5074;transport=udp;expires=0
could be. However, I think this check should be removed. Maybe save should return different code if it is unregister or register.
imo, m_dump() should be available for other cases, not only for registrations. It accepts parameter that can be unrelated to registration.
Cheers, Daniel
Daniel-Constantin Mierla writes:
could be. However, I think this check should be removed. Maybe save should return different code if it is unregister or register.
i agree that the best solution would be for save() code to tell if it was unregister.
is there a bug tracker available somewhere for sip-router?
-- juha
2009/6/9 Juha Heinanen jh@tutpro.com:
is there a bug tracker available somewhere for sip-router?
ops! that's a really good question!