Interface Not Active but service is accessible using telnet 1

[LeanClink]

We have developed a local TCP service for testing; it is simple service that echoes string sent to it and appends ' -received'

Service is hosted on same server and using port 5009. Using telnet, it works properly.

However, using below code, it errors on rxmsg, specifically showing "Interface Not Active".

waitforclear "testing - press esc"	
txmsg "test"     //Format message to transmit
waitforclear "sent to - press esc" // for response
getrxmsg "requesting from SIM" //Transmit message and wait
waitforclear "finshed - press esc" // for response

It reaches up to "sent to - press esc" but errors on getrxmsg; it does not reach "finished - press esc" anymore.

Error shows "Interface Not Active"; I am not sure what that means. Does it reach the TCP but TCP fails to reply? Does TCP service need to reply in a specific format?

I tried to look at 3700d.log with verbosity set to 10 but doesn't include any information. Also tried network IP address instead of 127.0.0.1 but still same result.

Is there a way to debug easily what is wrong or is there something wrong with my configuration? Below is my configuration:

Set up a Network Node pointed to the Server:
1. Computer Name = <Server Name>
2. IP Address = <IP Address from IP config>
3. Subnet Mask = <IP Address from Subnet Mask>

And set up an Interface using following settings:
1. Outgoing Message Name = SIM
2. Network Node = <server configured above>
3. Number ID Digits = 2
4. Interface Type = TCP
5. Sim Interface ENABLED
6. TCP Server Name = 127.0.0.1
7. Port = 5009

Thank you!

 

[CathalMF]

It usually just means the system hasnt updated fully with your new Interface configuration. It happens all the time.
Usually a Db Reload resolves the issue.

Specialist in creating custom applications for the Micros POS range: 3700, 9700, Simphony FE, Simphony. SIM Scripts, Data Exports, Simphony extension applications, API Creation and integration. If you need anything please contact me via my website

http://www.microspostools.com/

 

[LeanClink]

Thank you Cathal! I'm pretty new to this so didn't realize you needed to reload DB after Interface configuration. I was just restarting it since ISL file changes seemed to reflect. It is proceeding now

 

[CathalMF]

You shouldn't have to reload the db, but sometimes you do if you get this error.

Specialist in creating custom applications for the Micros POS range: 3700, 9700, Simphony FE, Simphony. SIM Scripts, Data Exports, Simphony extension applications, API Creation and integration. If you need anything please contact me via my website

http://www.microspostools.com/