When I want to get an account BIS, a window popup appear like in the picture.
And to make the steps cited in the popup: option > theDevice > Advanced System Settings > Host Routing Table. Then I Pressed the Menu key and clicked Register Now. I obtain Registration message queued. It will be sent once data coverage is available.
You could try a battery pull reboot and see if it fixes it. If not try resending the service books .It sends the service books for the BlackBerry Internet Service. you can look here to get information about how to do it.
Related
I'd like to play back credit card numbers for verification purposes; however, when you do this it exposes the redacted CC in the Request Inspector logs. Of course, I can turn these logs off, but Infosec wants more assurances that Request Inspector remains off and that we have steps in place in case it gets turned back on while live calls are arriving or is turned on and forgotten about.
Aside from seeking to have Twilio set it in a permanent state, I've proposed trying to code a status check that would account for either scenario.
That said though, is the Boolean/Toggle for Request Inspector available to be read from the API?
Example lazy code:
IF(Request inspector = 1) say "Please confirm that you wish to pay xx amount"
else if(request inspector = 0) say "Please confirm that you wish to pay x amount using your credit card 400000000000000"
Basically:
If inspector is on, don't read the CC.
If it's off, you can read CC
Twilio developer evangelist here.
In reality, you should enable PCI mode in your voice settings which is permanent.
As far as I know, you can't read or change the status of the request inspector via the API.
What I might suggest is that for testing you create a separate project within the Twilio console which is responsible for all its own resources. When you run in a test mode you can then use the credentials for this project and log or repeat actions and confirmations as you require. Then, when you run in production mode, you use your production account credentials which are in PCI mode.
We have a hotspot product using SMS authentication method. The user chooses our WiFi Hotspot network and is redirected to our login page.
On iOS and Adroid, a Captive Portal pop-up is activated showing our login page. We ask users to fill in a form and submit their phone number. When they click "Submit" we send them an SMS with a verification code.
The login window (hosted on our server) changes to a new page which is displaying a field to enter the verification code. So far so good... If the user sees the "notification popup" for the SMS on his screen on top of the captive window, he can see the code and enter it in the provided field and authenticate.
But if he doesn't have SMS notification set like this, he has to go to his SMS app and look up the code. Now, the only way to do that is to close the Captive popup but then he gets disconnected from our hotspot. If he reconnects he needs to fill in the form again and gets a new SMS but he faces the same problem.
Now, all this time user is not authenticated, so in iOS the captive window displays "Cancel" in the top right corner. I have seen this same method on other hotspots, but from the first Captive window, the control displayed in top right corner is "Done". As far as I know, the difference there is that the "Done" control is shown when the user is authenticated and "Cancel" while he hasn't been authenticated yet.
Is there a way to "fool" the CNA to "think" the user has internet access and display "Done" so when Captive window is closed, the device stays connected to our Hotspot?
We are thinking either some "two-step" authentication, like temporary (to get "Done") and then the "real" one after entering verification code.
Another way might be to use some kind of script (like "Success" trick on iOS) to fool the CNA into thinking there's internet access. But where and how to apply the "Success trick"? In some of the HTML pages in the router? Or somewhere in our login page code?
Different OS versions and different platforms check for internet access in different ways. iOS for example looks for one of these:
http://captive.apple.com/hotspot-detect.html
http://captive.apple.com
etc.
Android uses (among others):
http://clients3.google.com/generate_204
The best solution is for your captive portal to allow access to these through the firewall. If you're using MAC filtering via ipfw or iptables this is easy. If you're doing DNS spoofing it's harder -- for those cases I'd just include the "success" pages in your captive portal package.
I used below code to add menu it's working in one machine but not working on another machine
ISubscriptionMsgSetRequest _menuSet = GetSubscribeMsgRequest();
IUIExtensionSubscriptionAdd query = _menuSet.AppendUIExtensionSubscriptionAddRq();
query.SubscriberID.SetValue(SUBSCRIBER_ID.ToString("B"));
query.COMCallbackInfo.AppName.SetValue(AppName);
I am not getting any issue, actually i am not clear with the code
i have taken code from this url
check all steps one by one
Run your code using administrator account
When you will run you code check whether response status is 0? - if it is 0 then continue else check status message and update in your question
check whether below code is present
InformManager.SubscribeToQBUIExtensionEvents(handleMenuEvents);
ATTACHED EVENT OF MENU CLICK
After successful execution open Quickbook as administrator
Then you will get Authorisation box - Allow your plugin to add menu in quickbook, it is required.
If you dont get any Autorisation box then go in Edit menu in Quickbook
Edit->Preference->IntegratedApplication->Company Reference
Remove your app if it is present, and close & open QB again you will get Autorisation Box
Close you Quickbook
Open Quickbook as normal user then check your menus and their events
If events are not present again you need to check you event attached code.
10.Happy Quickbook coding
If you have any concern regarding Quickbook feel free to ask.
I am going over the checklist of QB requirements and currently looking at C2QB WF5.0. The steps are:
Go here: https://appcenter.intuit.com
/Home/ManageSubscriptions/.
On the Manage My Apps tab, locate the app and click the Disconnect link.
On the Confirm Disconnect dialog, click the Yes, Disconnect App button.
On the Confirm Disconnect dialog, click the Next button.
Sign in to the app.
As I using a staging (not authorized) version of the app it does not seem to show up in Apps.com for my QB user. Is there a way to either make the app show in https://appcenter.intuit.com/Home/ManageSubscriptions/ or to test this requirement in some other way?
Thank you!
To simulate the proper flow you can simply paste the Disconnect URL into the browser after the App Center completes the disconnect process. Intuit uses this method to complete the testing during the technical review .
Thanks
I have been given a webtrends DCSID number that is liked with my clients webtrends account.
However I have not been given access to the clients account, so I have no way of verifying if the reporting is working.
Is there a way to verify if it is working, e.g. setting up a trial account to test on?
The target is an iPhone app
You can also download an HTTP monitoring tool that will show you everything that is sent to Webtrends when the tag fires. It won't show you what the reports will look like, but testing the tag should really be the first step in any tagging implementation. If the tagging doesn't work as expected, the reports won't work either. :)
Standalone tools: Fiddler (free) or HttpWatch (basic or paid). Firefox Add-on: HTTPfox (free).
To test how the tag fires from an iPhone, you will need to either use a User Agent switcher/spoofer in your desktop browser, or use an actual iPhone and monitor the traffic using Fiddler—here are instructions. Once you install one of these, look for the hits to http(s)://statse.webtrendslive.com/[the client's DCSID]/dcs.gif?etcetera
You can go to https://tagbuilder.webtrends.com and generate the needed files for tracking, e.g. an empty html page and the javascript. If possible, upload both to a test webspace and access the page. Type into the addressbar
javascript:dcsDebug();
and a small popup will appear. You will now see all informations collected by the javascript and what would be send to the SDC server.
If needed, ask your customer to send you the logfiles of the SDC and compare the logs with your activity.