OTAP problem when using different ips

[Michail Apostolou]

I am working on the TC65 Gateway and i have encountered a really strange problem!

On my old ISP my sims take ip's from 93.92.*.*.

Recently i decided to change my ISP. This provides us with sims that take ip's from 93.93.*.*

The strange problem is that OTAP with my current ISP is not working where everything else is working properly!

I have tested changing OTAP to the same port as the other services that work and it didn't work either.

There is no firewall setting nor in my ISP neither on my servers. Nothing has changed in the code.

The only thing that i have not tested because i didn't find a way, is to hardcode a specific ip, in order to make sure that this is not what causes the problems and look somewhere else. 

Any help on this or ideas for troubleshooting would be greatly appreciated!

[Joschka Thurner]

Do you initiate OTAP with SMS or from your code? Did you adjust the connection parameters (apn, user, pw) for the new ISP? Try to reproduce manually with the exact strings used, and turn on the OTAP tracer (in ^scfg). It should give you some idea at what stage it is failing.

[Florent Clairambault]

Hi Michail,

You should start it here:
http://www.javacint.com/OTAP#Diagnose_OTAP_problems

--
Florent

--
javacint group - http://www.javacint.com/
---
You received this message because you are subscribed to the Google Groups "Cinterion Java enabled chips support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to javacint+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Michail Apostolou]

I initiate otap from code, all the parameters are set correctly since all the other services are working properly. I also know that the process stucks before the download of the jad file, since there is no request to the server for the jad file. Now i will try to work with the otap tracer and i will be back.

[Michail Apostolou]

Hi all,

i just confirmed that the problem is down to the at^sjotap command. I contacted the operator and we confirmed that there is nothing happening on their end, after i give the otap command to the GW. There is apparently an at^sjotap configuration that needs to be changed in order to work with the new operator.