Gemalto is now part of the Thales Group, find out more.

You are here

Community > Forum > Cellular Hardware > Establish connection to an Cinterion MC52i from a Webserver?

Establish connection to an Cinterion MC52i from a Webserver? | Thales IoT Developer Community

Like
0
5
fillibuster's picture
fillibuster

March 19, 2014 - 1:19pm, 8769 views

Hi, I'm searching for a way to establish a connection from my Webserver to an Cinterion MC52i. First: is this possible? On the server runs PHP. I think the best way to communicate is the TCP/IP stack, but where to start? Thank you and best regards ...
5
Comment
Log in or register to post comments
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Mar 19 2014 - 5:24pm
Hi, MC52i allows you to access web resources using internet services over AT command interface. Big advantage of these services is fact, that you don't need to worry about protocols handling as it's being handled by the module itself in the background, so with minimal effort you can have working acquire access to internet resources. For example you can simply connect to socket server and exchange data. You can setup socket listener and handle incoming connections. You can also use more complex internet services like FTP, HTTP, SMTP or POP3 clients. I assume that if you have HTTP server with php installed, you may want to connect from module to server with HTTP. The commands you'll need to use to setup the connection are: AT^SICS, AT^SISS, AT^SISO, AT^SISR, AT^SISW and AT^SISR. Please refer to chapter 10 - "Internet Service Commands" of AT Command Set documentation for details and examples.
j2meDev's picture
j2meDev
Apr 16 2014 - 4:12am
Hi, it seems you'd like to open a connection FROM your PHP WebApp TO the Cinterion MC52i. Actually if you intend you work this way, then I suggest that you start a permanent HTTP connection from your MC52i module and put it in a polling cycle waiting for any request from your server. An other solution would consist in using the DynDNS service. You may create an inbound server listening socket for port 'socketPort'... This is part of a MIDLet I did in the past: // ================================== sconn = "socket://:" + socketPort; // inbound socket connection try { GSMServer = (ServerSocketConnection) Connector.open(sconn); // display local IP address GSM_IP_Address = GSMServer.getLocalAddress(); wait(SVR_DELAY); System.out.println("Local IP address: " + GSM_IP_Address); // notify dynDNS.org notifyDynDnsOrg(GSM_IP_Address); etc. // ================================== Good luck, Frederic
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Apr 16 2014 - 1:05pm
Hi, your above ideas are in general very good, but unfortunately they're not applicable to MC52i as it isn't Java capable module, so you have to operate over AT command interface using Internet Services or PPP. The easiest way to access HTTP server is using HTTP Internet Service, but keep-alive mode is not supported. Single call HTTP requests is performed when using the service and after execution, the connection goes to state "down". It must be closed and opened again to send another request. Regards Jedrzej
Shaheen8911's picture
Shaheen8911
Jan 22 2019 - 7:04am

Hi

It means for every http request the connection has to be opened and closed?

Can you suggest some other way where connection is established once and write and read is possible until some issue occurs on client or server side?

Regards,

SS

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Jan 22 2019 - 12:49pm

Hello,

This is for HTTP and not for normal socket. The connection is open, HTTP request is sent (for example GET or POST), then you can read all data (in case of GET) o write all the data for POST then read the reply and the connection is closed automatically (you still have to call SISC on it). For another HTTP post or GET you need to open another connection. That's how it is implemented for HTTP via AT commands. In case of socket connection you can open it and keep open as long as you want (or until it's disconnected by the other party or the context is disconnected by the network). 

Best regards,

Bartłomiej