#624 time conversion lost when using mongodb and cache_db

[Ovidiu Sas]

If mongodb is used as a location database for usrloc (via cachedb), the time is lost during the conversion.
If a user registers and then a restart is performed, when location table is repopulated, all contact are restored as permanent.
On mongodb, the record looks ok:
{ "_id" : ObjectId("51378fb604708d261556ed03"), "username" : "osas1111", "contact" : "sip:osas1111@192.168.2.97:5060", "expires" : ISODate("2013-03-06T21:00:08Z"), "q" : -1, "callid" : "8e341f1-ee1cf2ff@192.168.2.97", "cseq" : 17785, "flags" : 0, "cflags" : 1, "user_agent" : "Linksys/SPA962-5.1.15(aSC)", "received" : "sip:192.168.2.97:5060", "socket" : "udp:192.168.2.3:5060", "methods" : 5183, "last_modified" : ISODate("2013-03-06T20:00:08Z") }
The fifo shows the contact as being permanent:
AOR:: osas1111
Contact:: sip:osas1111@192.168.2.97:5060 Q=
Expires:: permanent
Callid:: 8e341f1-ee1cf2ff@192.168.2.97
Cseq:: 17785
User-agent:: Linksys/SPA962-5.1.15(aSC)
Received:: sip:192.168.2.97:5060
State:: CS_SYNC
Flags:: 0
Cflag:: 1
Socket:: udp:192.168.2.3:5060
Methods:: 5183

A raw SQL query shows the timestamp as: 1969-12-31 19:00:00.

Regards,
Ovidiu Sas