I want to deploy Restcomm SMSC. I have downloaded its binary release and running SMSC in simulator mode. I am not using any digital card as I want to work with SIGTRAN and user guide states that in order to use ss7 with IP connectivity (SIGTRAN) , card is not required. Now I start following
SMSC in simulator
jss7 simulator
smpp simulator
also i do 'ant client' with smpp-load module but the build fails with error.
[java] Error: Could not find or load main class org.mobicents.protocols.smpp.load.Client
Also, I am still unable to understand the message flow despite reading the guide. The screenshots in the user guide is using telscale SMSC which is feature-rich than restcomm SMSC. Kindly guide me
Thanks
Related
iotedge list command error
Hi,
On running the iotedge list command it is throwing - A module runtime error occurred. Is there something missed. It was working fine till yesterday.
If you are still blocked, you can check the below information.
There could be multiple reasons for the module runtime error on IoT Edge.
Was it working earlier and stopped suddenly? As Matthijs mentioned in
the comments, collect complete logs to know more about the issue.
Refer Gather debug information with 'support-bundle' command
Also, check Azure IoT Edge security manager logs. The IoT Edge
security manager is responsible for operations like initializing the
IoT Edge system at startup and provisioning devices. If IoT Edge
isn't starting, the security manager logs may provide useful
information.
Make sure that the module is properly configured and all
required environment variables are set.
If the issue still persists, you can try restarting the module or the
entire IoT Edge device to see if that resolves the issue.
You can also check Solutions to common issues for Azure IoT Edge for most common errors and solutions.
I developed an Apple app that I am testing on a Mac Mini. When I set the Delphi configuration to "Normal" then build and run the app on the Mac, the program starts up and connects to the internet without problems. Once the program has been built and run on the Mac, I can go into the scratch-dir folder on the Mac (created by Delphi's PSServer) and run the "app" file without problems also.
However, when I change the configuration to "Application Store", rebuild, then use the Deploy button to create the "app" and "pkg" files on the Mac, the app will no longer work when trying to access the internet. Any internet access attempt fails. This happens with both the rebuilt "app" file in the scratch-dir folder, and when I install the "pkg" file and try to run the program.
Note: this app uses the Indy components TIdFTP and TIdSMTP to access an FTP server and to send emails. Both of these work with the "Normal" app, and both fail with the "Application Store" app. The fact that both components fail with the "Application Store" build probably indicates that this is not an Indy problem. But just in case, for the FTP connection, I just get an "Unable to connect to FTP" message that is from my program, I have not added additional error handling to see what fails with the FTP. For the email failure, Indy raises an "Error resolving Address smtp.office365.com: nodename nor servname provided, or not known (8)" exception.
Any suggestions on how to determine why my "Application Store" build isn't working?
Additional info on 2023-01-03. Just simply changing from Normal configuration to Store Application and doing a deploy causes the problem. I checked the messages given out by Delphi during the builds and the Normal and Store build messages match. For the deploy, only difference in messages is the Normal configuration does a quick compile (not build) and the Store configuration adds the "Apple Distribution" and "3rd Party Mac Developer Installer" info to the deployment.
As mentioned by both Remy Lebeau and Dave Nottage, the problem with the Application Store compile was not having Outgoing network socket for connecting checked in the Entitlement List for the Mac. Checking that option allows the Application Store compile to access the internet.
Note: not sure why compiling the project when set to Normal configuration does not require Outgoing network socket for connecting but the Application Store compile does. Makes things confusing and causes a lot of head scratching.
I have searched high and low for a solution to this which I am sure must exist but I have failed to find one that works.
I am running XCode 7.3 and iOS 9.2 on an iPhone.
I have a test server running on 127.0.0.1:8000
I cannot get my app running on the iPhone to connect to either 127.0.0.1:8000 or 192.168.1.200:8000 (which is the local ip address of my server).
There must be a way to give the iPhone app access to the local server if only I knew how!
The best solution to this problem, that many app developers have, is to download ngrok which acts as a proxy website.
ngrok is insanely easy to use:
Download from https://ngrok.com/
Run: ngrok http 8000 in terminal (where 8000 is your port)
Cut and paste the displayed ngrok url (e.g. http://a021v2tc.ngrok.io) into your app
So simple. And works!
Check if iPhone connect the same wifi with your server.
You can use Fiddler as iPhone agent to get the detail error message.
There is the link how to capture traffic from IOS device.
here
)
I want to deploy my app that is created with Phonegap to my BlackBerry Z10 device.
I created some Hello World basic app with Phonegap, then in the terminal (Mac OS Lion) I ran following command:
/Users/macbook/Documents/BB10APP/cordova/run BBZ10
Everythings seems to work fine, but in the end I get a connection error:
[BUILD] BAR packaging complete
Error: Error: Cannot connect: Connection to https://169.254.x.x:443 refused. Please check IP address settings for the target. You may have to reboot the target.
What could be the problem with the connection?
And is there some other tools that I can use to just send the app via USB to the device like on Android?
Thanks :-)
I found a solution if anyone wants to know:
You have to use the device IP address and not the developer IP that is found in the developer settings on the device (where you see your developer token).
And then it will work (don't ask me what the developer ip is for, just annoying to lead developers in a wrong direction).
The device ip can be found in some settings entry on the device (I don't remember in which unfortunately, but it is there). Just dont use the ip from the developer menu that wont work :-)
There are two IPs in Blackberry
IP that is appearing on bottom part of Controller EX. ( 192.168.139.129)
IP that is configured in Blackberry simulator (Security and Privacy -> Development Setting)
EX. ( 169.254.0.1)
Using Controller IP "Network connection problem" issue will be solved
D:\bbndk\hello\platforms\blackberry10\cordova>target.bat add mydevice 192.168.139.129 -t device --password 0000 --pin 00000000
I tried to deploy a Play app to Cloudbees (only via push to git repo from which it is built by jenkins), it compiled and should work but I get a "502 Bad Gateway" error when loading the app. There is no error shown in the console only that it answers "502 Bad Gateway" when trying to access it. But that's what I see in the browser, too.
Cloudbees say that there is no other manipulation necessary, just cloning/pulling the ClickStart-Project, making it you application and pushing it back. The Play project works fine locally.
I am very grateful for any help. Please let me know if I need to provide any other information. Thanks a lot!
Edit: It works fine with Heroku only adding a Procfile. I don't get the problem with Cloudbees...
In this case the error is due to the database needing evolutions to be run before it can start:
[warn] play - Run with -DapplyEvolutions.default=true and -DapplyDownEvolutions.default=true if you want to run them automatically (be careful)
Oops, cannot start the server.
#6eg39l651: Database 'default' needs evolution!
You can see the error in your application console:
https://run.cloudbees.com/a/strehlst#app-manage/logs:strehlst/odzh
or via bees app:tail if you have the bees CLI installed.
You can also deploy direct from your desktop if you like:
play dist
bees app:deploy -t play2 dist/yourapp.zip
And it will push direct to your app (if you don't want a continuous deployment pipeline).