Support forum

Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_TopicIcon
Communication problems with Hypermedia SMS Pro Gateway
sp_NewPost Add Reply sp_NewTopic Add Topic
June 21, 2013
8:57 pm
Henk Helmantel
Admin
Forum Posts: 1487
Member Since:
May 28, 2013
sp_UserOfflineSmall Offline

In the Hypermedia SMS Pro Gateway section of the online manual you can find some information on the use of the Client ID setting.

The text in the manual says "Note that if no ID is given, a unique ID will be generated for the client by the gateway", this is taken from the documentation of the Hypermedia API but your experience suggests that the generated Client ID is not unique when you leave it empty and it is necessary to specify a unique, non-empty, Client ID when you want to use multiple gateways.

Using multiple gateways is only necessary when you want to use Diafaan SMS Server to route messages through specific GSM modules on the Hypermedia SMS Pro Gateway. When the Hypermedia Gateway does the message routing, only one gateway is sufficient for all the GSM modules in the Hypermedia SMS Pro Gateway.

Regards, Henk

June 21, 2013
8:12 pm
Eric van Doorn
Guest
Guests

Hello Henk,

Your analysis is correct. We had 2 gateways configured, each looking at a different SIM card in the Hypermedia SMS Pro Gateway and each using the same Client ID. After removing one of the gateways in Diafaan it all started working fine.
I think it is important to share this information with anyone that wants to use a similar setup. The Hypermedia box supports 32 SIM cards, so it's almost inevitable that you will define multiple gateways when using it with Diafaan.

Thanks a lot for your quick and effective support.

Regards,
Eric

June 21, 2013
5:10 pm
Henk Helmantel
Admin
Forum Posts: 1487
Member Since:
May 28, 2013
sp_UserOfflineSmall Offline

Thank you for the log.

It looks like the problem is caused because two programs, or two defined Hypermedia Gateway's in Diafaan SMS Server, are logging in to the Hypermedia SMS Pro Gateway at the same time with the same Client ID. You can see this line in the log, just before the connection is lost:

{"notification": "replaced by new one connection IP - xxx.xxx.xxx.xxx"}

This means that another process is now using the connection to the Hypermedia SMS Pro Gateway and the current connection is lost.

If you want to connect more than one program to the SMS Pro Gateway or if you want to specify multiple Hypermedia gateways in Diafaan SMS Server to the same device, you have to supply a different Client ID for each connection. You can change the Client ID in the Hypermedia SMS PRO Gateway settings in Diafaan SMS Server

Regards, Henk

June 21, 2013
4:00 pm
Henk Helmantel
Admin
Forum Posts: 1487
Member Since:
May 28, 2013
sp_UserOfflineSmall Offline

Hello Eric,

Can you send a complete log file, preferably with some sent and received messages, to dms@diafaan.com? It looks like the SMS Pro Gateway does not return a consistent reply to the ping method and I would like to see the full communication log to get a better impression what happens exactly.

Regards, Henk

June 21, 2013
2:35 pm
Eric van Doorn
Guest
Guests

We have connected the latest version of Diafaan with a Hypermedia SMS Pro Gateway. Sending SMS messages works fine, but half the messages received on the Hypermedia box do not reach Diafaan. Also, in the eventlog of the gateway the following message is displayed every half hour: "Timeout error: no response after the keep alive command".

The communication log contains the following sequence that is repeated continuously:
2013/06/21 14:18:50.908 - IP connection to: 10.130.10.75:63333 open.
2013/06/21 14:18:50.908 > {"method":"authentication", "server_password":"admin", "client_id":""}
2013/06/21 14:18:51.158 < {"notification": "replacing old connection IP - 10.130.10.56"}
2013/06/21 14:18:51.158 {"method":"register_for_incoming_sms"}
2013/06/21 14:18:51.408 {"method":"ping"}
2013/06/21 14:19:46.659 {"method":"ping"}
2013/06/21 14:20:41.910 < {"reply": "error", "error_msg": "unknown_method", "method_reply": "ping"}
2013/06/21 14:20:46.410 {"method":"ping"}
Then it start over again with:
2013/06/21 14:22:41.662 - IP connection to: 10.130.10.75:63333 open.
...etc

Forum Timezone: Europe/Amsterdam

Most Users Ever Online: 529

Currently Online:
3 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Member Stats:

Guest Posters: 671

Members: 0

Moderators: 0

Admins: 1

Forum Stats:

Groups: 2

Forums: 3

Topics: 1140

Posts: 3897

Newest Members:

, Henk Helmantel

Administrators: Henk Helmantel: 1487