Network Connection Issue + Blackberry - blackberry

I am facing a network connection issue. My client has sent me following mail and I am having no idea what I should do in this condition
"One of our companies have asked if it would be possible for them to use their apps with the data going via a proxy. The hve disabled WAP on their BES so they are unable to use the application. I think in this instance the data needs to be routed through the BIS."
For using BIS , I have read that application needs to be approved by RIM and we need to append a secret String provided by the RIM to the connection URL.
For BES we append ;deviceside=false in case of simulator.
For TCP we append ;deviceside=true to the connection URL.
For Wifiwe append ;interface=wifi to the connection URL.
What should we append in the case of BIS?

Related

timeout in telegram.bot webhook - asp.net mvc

I had been developed a telegram bot using Telegram.Bot.
I tried to rework with the bot, First I created bot using BotFather and got token.
I set webhook server api address in telegram api. But when I check webhookinfo it returns this error
https://api.telegram.org/botToken/getWebhookinfo
respone:
"last_error_date":1585419712,"last_error_message":"Connection timed out"
I checked it need TLS12 to have secure connection using
System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;
But It's not getting updates in my server and show time out error.
I tried posting using postman and ngrok to run on my iisexpress and I'm getting data and can sending messages to bot in my localhost.
But In hosting it's not working, whats wrong with new Telegram.Bot library or telegram server?
update
I checked with postman my hosting url, post man also cant connect to that url. what can be wrong with my codes?
This is response when i'm call update receiving URL in my hosting:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.34.35:443
I got problem, the certificate which we use should be valid one, not free.
For more information please study this link:
https://core.telegram.org/bots/webhooks

Network Sniffing/SSL Pinning : Not able to get post through the login page in a mobile app when detecting traffic with Fiddler

I am debugging network calls of one of the client's application whom code I am not having. The steps I have gone thorough is as below.
1) Install fiddler in a windows system.
2) unable HTTPS decryption.
3) set the system proxy to match the client's country. (USA)
4) install the app on iOS to which is on same network.
5) Installed the Fiddler certificate in phone, added to trusted certificate
6) Applied the manual proxy matching the same internal IP of the windows system. (not the system proxy of USA)
Now when I open the app, I am able to trace the network calls till login page. Also able to detect network call which send the credentials.
But after loading for 5-8 seconds, the app shows "something went wrong, we are unable to serve you"
I am not able to see any trace of my machine IP (internal IP), in network calls being sent. I changed my phones Timezone in case that is the triggering point for stop serving.
Also randomly after 2-3 attempts the following popup comes. I have set the Client Certificate as asked, which was downloaded from http://ipv4.fiddler:8888 .
There are many other apps for which I am able to see the entire network calls but not for this specific one.
Is there any issue in my system settings or the app provider have mechanism to identify man in the middle proxies. Or certificate issues?
Update 1 : I checked the fiddler log and found the below error
HTTPS hand shake to TargetURL failed The exact error was "a call to SSPI failed, see inner Exception, the certificate chain was issued by an authority that is not trusted. is this case if SSL Pinning?
You are mixing up the certificates. Usually the problem is the server certificate, however in your case the problem arises from a client certificate. A SSL client certificate is a optional feature that allows to identify a user based on a certificate + private key instead of username+password. It is often used in companies where each user has a certificate+private key on a smart card.
There are now two possibilities:
The iOS app includes a client certificate+private key and the app developers use this to protect the communication API (a bit similar like an API key). In this case you have to extract the certificate and the private key and provide it to Fiddler. Most likely certificate and private key are the same for every device world-wide and can be found as static resource in the iOS app (potentially obfuscated or somehow protected).
The server asks for a client certificate but providing a certificate is optional. I don't know if Fiddler can handle this situation.

How to connect a device to a Rails server via TCP?

let me explain what I've already completed and what is needed to be done.
What's I've done
Rails server with PG database that returns some data to a user from DB via GET request.
What's needs to be completed
I need to connect the device to this server via TCP. The manufacturer of the device asks me to provide the server address and the port, so he can configure the device to send some messages to the port provided. This messages should be recorded to DB (this part is not important, just to let you know the flow I'm trying to achieve) and then a user can get those messages by GET request mentioned above.
The question
How to set up the Rails server to accept TCP messages from the device to a specified port? How to handle those messages? E.g. the simplest: how to print the message received?
Is it even possible with Rails? If you have a better option on how to achieve the flow mentioned above, please share it.
I'd appreciate some help with code or links.
Just start your rails server with command rails s -b 0.0.0.0
this will bind your public IP with your server so that you can connect with other devices to your rails server.
for example your IP is 192.168.64.40 so, after this command you can do like 192.168.64.40:3000 in to other device's browser so that they can connect to your rails server

Cannot reach SIP server

I'm developing a VoIP IOS app using SIP protocol. I have my own SIP parser library and I use GCDAsyncUDPSocket to send data to the server.
The problem is that I can't reach the server on double NAT with my app. I do PING and the server responds immediately PONG, but when I send a SIP package, I can't even reach the server.
I try to reach the server with other clients like Zoiper or Media5 and works perfectly. So I think i'm doing something wrong.
Make sure to:
include your private IP:port in the contact and via headers (not a wrong public address)
add the rport attribute to Via
make sure that the REGISTER message is well formed (is a valid SIP message)
If still doesn't work, check the server logs. If still doesn't work or you don't have access to the server logs, let me see your REGISTER message.

Passbook couldn't connect to development web service

I'm creating my own Passbook Web Service, in order to register and update passes created by my server. When I add to the Pass information inside the pass.json the webServiceURL and the authenticationToken attributes, the pass is displayed but not added to the iOS Passbook App. Given I'm still in development I don't have a https with SSL server, but a plain http one:
http://192.168.1.100:8080/PassbookDelivery
Does the device and/or the protocol inside the Web Service need some special change in order to accept the pass produced by my server? Does the authenticationToken have any restriction, like string length, cipher or content?
NOTE: I already use the format URL for registering the device for updates, as detailed in the Passbook web service specification, which is (POST)
http://192.168.1.100:8080/PassbookDelivery/v1/devices/_deviceLibraryIdentifier_/registrations/_passTypeIdentifier_/_serialNumber_
but it doesn't get any call from the device.
Try this: go to Settings > Developer, scroll down to PASSKIT TESTING and toggle "Allow HTTP Services".

Resources