Without reading the RFC I suspect the version to be increased within the
subscription. So, if there is a NEW subscription, the version will be
reset. If it is a re-subscription (to keep the current subscription
alive) the version will not be reset.
So, how to differ between NEW and RE-subscription? If the SUBSCRIBE
contains a to-tag, then it is a RE-subscription. If there is no to-tag,
than it is a new subscription.
regards
klaus
kamailio.org(a)spam.lublink.net wrote:
Hey,
I have noticed that the XML body of the dialog messages contains a
version attribute. The server is counting the versions using the latest
subscription as a reference point, and the phone is counting the
versions from the first subscription ( at reboot ).
Which is the correct way to count these versions?
Consider :
10:00 Subscription
10:05 Notification version 1
10:35 Notification version 2
11:01 Subscription
11:05 Notification version X
Is X = 3 because it is the third notification or 1 because it is the
first after the last subscription? If it's version 1, it could confuse
the phone cause a notification that is sent at the same time as the
notification would have a confusing version.
On the other hand, each subscription, has it's own versioning, so would
it not logically follow that the different subscriptions for the same
device have seperate versioning?
From my phone : BLF Notify received for line: 3 has older version: 3
last version:135
To confirm my theory, I redialed the number 133 times, and once the
version number had run up to 136, the lights started flashing again.
Is this a bug in Grandstream, Kamailio, or perhaps an RFC which was
unclear?
Thanks,
David
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users