SOTI Pulse Logo

APN Setup for Android device

YG
Yoann Garcia
Swissport International Ltd.

Hi the community, 

hope you're all doing well.

Hope someone can help me as I'm starting getting crazy with this point.

We have an APN to be setup on all our mobile for our staff to use their dedicated app on different type of device. Crosscall Core X5 and Samsung Xcover7.

We created, years ago, a profile with all APN informations inside and deploy it to the group of device.

It is working perfectly on Crosscall devices but on Samsung devices, the phone dialing is not working anymore since 10 days. If we setup the APN manually on the device it works, but if it is pushed by SOTI, it doesn't.

The only difference between the one pushed and the manually created is the type of APN (default, mms, ....). Via SOTI it was pushing a * which is not recognized anymore by Samsung but still by Crosscall...

 

My problem is, I havemore than 2000 devices working with this APN profile, I don't want to touch the actual profile.

I made a clone of this profile and just change the type of APN and now SOTI is not pushing the correct password with a new profile... I dont know why. I tried with a new profile, a clone of profile, .... Everytime the password is false now...

I also tried to push the APN via the OEM config of Samsung in SOTI but it doesn't work, the device receive nothing...

Any idea? I got more than 500 Samsung devices and really don't want to install the APN manually on all of them...

 

Thank you

samsung apn crosscall type of APN
4 months ago
SOTI MobiControl
ANSWERS
RS
Rafael Schäfer
4 months ago

If your devices doesn't receive the setting in oem config, there would be a general issue to investigate together with support.

But as long as you work with oem config (for testing) enable debug mode to see why the APN profile there is not working/distributed.

RC
Raymond Chan Diamond Contributor
4 months ago (edited 4 months ago)

What are the version and build number of your MobiControl server?

What about the Android firmware version and KNOX library versions in your XCover7 devices?

There might be bugs/compatibility issues in any of the above that needs to be identified and upgraded/fixed.

 

Have you successfully used any OEMConfig parameters (i.e. other than the APN parameters in your current issue) to your XCover7 devices in the past?  Are you sure you have the Samsung KSP app properly installed on the devices?

 

Have you opened an official case with Soti support team.  If so, after performing some tests on your devices, the problem may be quickly fixed with some undocumented script command(s).  Unfortunately,  I don't have any Crosscall Core X5 or Samsung XXover7 device to do any tests.

Similar Discussions