I tried the On-Behalf-Of subscription feature to add topics for mqtt clients and found out that it only works for the following topic structure:
T1/T2/T3
T1/T2/T3/*
but not for the following (wildcards):
T1/T2/T3/>
T1/T2/T3/+
I wonder how I can add multi-level topic subscription for my mqtt clients.
I am using sol-common 7.1.2.230 and sol-jcsmp 7.1.2.230 and my Solace appliance version is soltr_7.1.1.582.
Thank you.
The On-Behalf-Of subscription feature is only supported for SMF clients and therefore only subscription topics using SMF syntax are accepted.
When using an SMF client to manage subscriptions for a MQTT client, the ">" wildcard is not allowed because there is no MQTT equivalent. The ">" wildcard means the following path must match 1 or more topic levels, whereas in MQTT, the "#" means that the following path must match 0 or more topic levels.
The reason the "+" wildcard doesn't work is because it is not valid SMF syntax.
On the other hand, the "*" wildcard is the exact equivalent of the "+" wildcard in MQTT. This is why the "*" wildcard works.
Related
When I try to publish to different topics using same client id it disconnects the previous connection.
It says the mosquitto_pub publishes a single message at a time so was wondering if this is a limitation.
MQTT Client Ids MUST be unique across all clients connected to the broker. The spec says the broker must disconnect any existing client when a new client with the same client id tries to connect.
The mosquitto_pub command will only publish a single message to a single topic (unless reading from a file or stdin, in which case it publishes a message per line, but again to a single topic).
If you want a single client to publish to multiple topics then you should look at one of the many MQTT client libraries and built a client that meets your needs.
We have a query to ask regarding the Twilio voice communication and hope you will help us.
We are having a client and they are having business with Health care domain having Doctor-Patient communication happening through Twilio cloud.
We know that a non-twilio number can be used for caller id after verification with twilio by 6 digit input from the user.
The client requires a mechanism like when they sell the product to many customers, each customer just input any valid work number (office number) and wants to use those number as Caller Id without the verification process.
We would like to know whether Twilio us offering such custom caller ids without doing the verification steps ? Like with means of a high-level membership plan with twilio or for utlizing any bulk purchase schemes or by trusting the client with any documents or by any other means of ?
Please give your suggestions in this.
Thanks
No. You need to verify each number to use it for your caller ID. Another way of doing it is that you buy the number via Twilio when the customer signs up and that's their outbound caller ID. Would be much easier to do.
david
I am using the Verification service and all working fine. My Service Name appears in the body of the Verification message correctly but how can I change the SMS From label?
In my SMS app I see a list of messages from various contacts and companies, the message from Twilio Verification Service shows as a 5 digit code e.g 12345. How can I change that from 12345 to "MyService"?
I get messages from other companies and a short company name appears as a contact name, how can I do the same with my twilio verification service?
Thanks
Twilio developer evangelist here.
Twilio Verify uses a variety of short codes, alphanumeric sender IDs and other phone numbers in order to send the verification messages around the world. The Verify team work on ensuring the numbers/sender IDs have the best possible delivery by pre-registering them in various countries. This gives you the highest possible chances of getting authentication messages delivered swiftly. You can't customise the number by default.
If you are looking to customise the number that is used, I would recommend you talk to the Twilio sales team to see what you can arrange.
My organization is using the Twilio SDK in C# to sms and mms messages with a single long code. We have several teams in several different departments using it for various purposes and are looking to track how much of the bill belongs to each team. Each team has an API Key that they are using to authenticate their calls to send a message: TwilioClient.Init(apiKey,apiSecret,accountSid);
Is there anyway to see in the sms logs a breakdown of which API Key was used to send messages?
There is not. You can however use sub-accounts which are logical containers of resources, and then the usage API to determine usage by subaccount.
Our firewall restricts outbound network connections. Hence we need to know the list of IP addresses to which we need to open up the port for outbound network connections that connects to Twilio for the REST API for sending sms.
How to find out what are the list of IP addresses that twilio uses for outbound connections so that we can open those in our firewall?
As per the Twilio docs it says we need to open up for https://api.twilio.com.
Unfortunately our firewall needs to define a list of IP addresses instead of a URL and it looks like the IP Addresses keep changing and is not static.
Does the following hold good for outbound connections from Twilio for Messages via their REST API?
https://forums.aws.amazon.com/ann.jspa?annID=1701
Please advise.
From the FAQ article on this topic:
Twilio makes HTTP requests to your server to fetch your app’s TwiML instructions. Some users prefer to know which IP address the request from Twilio is coming from in order to open up specific ports in a firewall. However, due to the fluid nature of our cloud architecture, we don’t have a set range of IPs that requests are sent from or know in advance what they will be.
Because Twilio’s requests will be coming from different IP addresses, we instead recommend that you validate that a request came from Twilio by other means. Please see our documentation on securing your application for more details.
If the inability to have a request come from a static IP address is a serious concern, please contact our sales department to discuss other options which might be available.