Uniqueid is converted to float with precision-problems
Reported by Sindre Aarsaether | April 23rd, 2009 @ 03:30 PM
It seems like adhearsion converts the uniqueid of an asterisk call to a float, which really breaks the whole unique-id purpose. When you fetch the remote id via manager-events, you get a string (as expected). That string differs from the unique-id of the same call in dialplan..
INFO agi: Handling call with variables { ... :uniqueid=>1173223225.10309 ...}
INFO events: #<Adhearsion::VoIP::Asterisk::Manager::ManagerInterfaceEvent ... "Uniqueid"=>"1173223225.103088" ...
This is the same call, and presumably they should have the same uniqueid. I think unique-id should always be treated as a string (over the whole system) as it might even be prepended by a string (by asterisk) if running several asterisk-instances on one server.
And with this rounding you get the chance of duplicate unique-ids which would be very bad when using it to identify calls in db etc.
Comments and changes to this ticket
-
Jay Phillips April 23rd, 2009 @ 08:29 PM
- State changed from new to resolved
Good point! I fixed this in master.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป