Hi all,
since there are some others having trouble getting into sync, i tracked down my blackberry->egw sync errors to the following:
all requests from blackberry were appended with the string “;WAPGatewayIP=139.7.29.1;WAPGatewayPort=9201” so an url looks like:
/egroupware/rpc.php;WAPGatewayIP=139.7.29.1;WAPGatewayPort=9201
I am not a http crack but this is not a good query string (? is missing)
If i look into /tmp/sync i see:
http:///rpc.php;WAPGatewayIP=139.7.29.1;WAPGateway
APN=wap.vodafone.de;WAPGatewayPort=9201?syncml_sessionid=syncml-f5ef47f9463ae11b10e53fe29
2429876;WAPGatewayIP=139.7.29.1;WAPGatewayAPN=wap.vodafone.de;WAPGatewayPort=9201</LocURI
That seems wrong, too.
I fiddled around with apache redirect and managed to get out the POST requests from
/rpc.php;WAPGatewayIP=139.7.29.1;WAPGatewayAPN=wap.vodafone.de;WAPGatewayPort=9201?syncml_sessionid=syncml-f5ef47f9463ae11b10e53fe29
2429876;WAPGatewayIP=139.7.29.1;WAPGatewayAPN=wap.vodafone.de;WAPGatewayPort=9201
to
/rpc.php?syncml_sessionid=syncml-f5ef47f9463ae11b10e53fe292429876;WAPGatewayIP=139.7.29.1;WAPGatewayAPN=wap.vodafone.de;WAPGatewayPort=9201
but then the WAPG… rest is escaped into the session id.
Would this be the right way to do it? Or patch egroupware php sync code to handle it?
Anyone knows how to tell vodafone not to append their ;WAP thing?
Greets,
Frank