More over,
Same thing seams to happen for those devices that use ";" (semicolons) 
instead of "; " (semicolons plus space).
Kind of very bothering thing, since when one of those happens the result is 
everything between an empty session or multiple sessions been created (empty 
or filled) for the same device.
This is actually tricky, as long as u have just the sessionID as only value 
in you cookie everything works fine. The odd things starts to happen once u 
add more then one cookie value.
For instance, dealing with regular cookies leads to the usual:
Cookie: PHPSESSID=s1buavh0oa80dggt6i646nl084; test=ok
Array
(
    [PHPSESSID] => s1buavh0oa80dggt6i646nl084
    [test] => ok
)

this is what happening with the other separators:
Cookie: PHPSESSID=a4qmclqmck8kok2gj26vblmj72, test=ok,
Array
(
    [PHPSESSID] => a4qmclqmck8kok2gj26vblmj72, test=ok
)

which is just silly ;P

Most important:
I hope there is a patch for this somewhere, we cannot afford to use a cvs or 
development version since we're in a production environment :(

thx for help
lucio

See bug #32111

Bug #32827 was reported to _revert_ the bad fix for allowing comma as cookie separator. You're missing the part "Read RECOMMENDED, BUT NOT REQUIRED." in it.. :)

Please report the problem to the manufacturers of these devices, they're the ones interpreting the "standard" wrong.