So, I can use my Breeze to send SMS via Zang. I see there's an inbound poller running in the ZangSmsConnector.log but none of my SMSs to my Zang PSTN number are picked up by the poller. I wanted to avoid invoking an outbound REST call from Zang to my Breeze and was hoping the ZangSMSConnector snap in would pick up the SMS and make an event out of it.

What am I missing?

There is a setting required on the Zang CPaaS in order to support inbound SMS.

In CPaaS: Numbers; Manage Numbers;

Set the incoming url (SMS Request URL) with the following url -

https://pubsub.zang.io/<AccountSid>/SMS/Incoming

where <AccountSid> is to be replaced with actual accountSid of the respective Zang account.

The Zang SMS Connector will poll for incoming message only for Default account specified in service attributes.
This also requires that the SMGR;Breeze;Config;Attributes are set for the ZangSMSConnector and that outbound SMS is working.

CPaaS Notifications will provide good troubleshooting information while using this connector.

I hope this helps.
-Valerie

Awesome!

Closer...

So, I set the SMS request URL in CPaaS to what you suggested - which is also the name of the poller URL Breeze is using.

It just sits there when I send SMS to my number. If I change it back to the default http://static.zang.io/ivr/welcome/sms.xml and send a SMS, i immediately get the "We have received your message..."

When I change it back to the poller URL you suggested/in the breeze logs, nothing gets picked up on subsequent SMSs. Weird.

2020-10-30 14:05:02,482 [Thread-488] ZangSmsConnector INFO - ZangSmsConnector-3.8.0.0.0990022 - com.avaya.services.zang.smsconnector.common.PollerUtil - createInboundUrl() : complete incoming poller url https://pubsub.zang.io/ACf674eb32b98db1e91f8d4495b2e3670d/SMS/Incoming
2020-10-30 14:05:02,483 [Thread-488] ZangSmsConnector INFO - ZangSmsConnector-3.8.0.0.0990022 - com.avaya.services.zang.smsconnector.process.PollerServiceProvider - startPollerForAccount() : Poller started for account ACf674eb32b98db1e91f8d4495b2e3670d Pollertype INBOUND isDefaultService true
2020-10-30 14:05:02,501 [Thread-488] ZangSmsConnector INFO - ZangSmsConnector-3.8.0.0.0990022 - AuthorizationRegistrar: registering listener
2020-10-30 14:05:05,491 [WorkManager.DefaultWorkManager : 2] ZangSmsConnector INFO - ZangSmsConnector-3.8.0.0.0990022 - com.avaya.services.zang.smsconnector.configuration.ServiceManager - getNodeClusterIP() : Cluster IP is : 100.125.78.126
2020-10-30 14:07:09,015 [DAOReplicationQueueServicer] ZangSmsConnector INFO - ZangSmsConnector-3.8.0.0.0990022 - com.avaya.services.zang.smsconnector.configuration.AttributeServiceImpl - notify() : attribute name -defaultSMSNumber attribute value - 15xxxxxxx03
2020-10-30 14:07:09,017 [DAOReplicationQueueServicer] ZangSmsConnector INFO - ZangSmsConnector-3.8.0.0.0990022 - com.avaya.services.zang.smsconnector.configuration.AttributeServiceImpl - notify() : attribute name -accountId attribute value - ACf674eb32b98db1e91f8d4495b2e3670d
2020-10-30 14:07:09,021 [DAOReplicationQueueServicer] ZangSmsConnector INFO - ZangSmsConnector-3.8.0.0.0990022 - com.avaya.services.zang.smsconnector.configuration.AttributeServiceImpl - notify() : attribute name - userPassword attribute value - *****

For the Breeze server, check that the Breeze Eventing Connector is open to the internet. There might be a Postman project to simulate/test; I can look if that is of interest.

Is outbound SendSMS Notification task working / sending out from ED or other Breeze snap-in? You should see these in CPaaS dashboard Logs; SMS Messages.

If outbound is working but not inbound, you might turn logging up on the ZangSMS Connector to see whether it is Warning or sending any Errors.

My breeze eventing connector is open to the internet.

https://aoc15dc1brzedp1-sm100.suletmaaslab.ca/services/EventingConnector/events

I was able to point the incoming SMS for my phone number to that URL and I see the request come from CPaaS, go through my SBCE proxy and hit Breeze.

Looking for documentation, I only found the 3.3 version info on the ZangSmsConncetor on DevConnect. I appreciate the URL you gave me, but I'm wondering if that was available in documentation I could have found on my own so I don't have to keep bugging you.

I have a single breeze cluster, so I figured for fun I'd give it a cluster IP and cluster FQDN - aoc15dc1brzedp.suletmaaslab.ca. I was thinking maybe the inbound poller on the SMS connector advertises a Breeze event FQDN. It doesn't seem like it because SMS's don't trigger any activity in my Nginx traces on the inbound eventing FQDN.

Using traceCE and debugging "ALL" for the snapin, I was able to get ZangSmsConnector.log to print very verbose information.

One thing that caught my eye was:

2020-10-30 18:20:26,999 [WorkManager.DefaultWorkManager : 0] ZangSmsConnector DEBUG - ZangSmsConnector-3.8.0.0.0990022 - com.avaya.services.zang.smsconnector.httpservices.HttpRequestDataBuilderImpl - prepareHttprequestUri() : No append url provided: request URI - https://pubsub.zang.io/ACf674eb32b98db1e91f8d4495b2e3670d/SMS/Incoming?session=d21eec89-79b0-4028-b5a0-62737c191b23&timeout=15s

I was thinking maybe that "append URL" was like a callback URL and that my polling subscription should include a callback URL for when CPaaS gets a message for me. That's why I tried both not setting a cluster IP/FQDN for my single node cluster AND setting a unique cluster IP/FQDN. I updated my certs to include both FQDNs as SANs. Feel free to check for yourself!

I'm not seeing anything coming in through my SBC reverse proxy when I send a text using the URL But, if I point the phone number's SMS handling to the cluster FQDN's eventing connector URL:

https://aoc15dc1brzedp.suletmaaslab.ca/services/EventingConnector/events

Then I see a lot of 499's which seems like it's an Nginx thing and 504s from the Breeze back to the SBC back to CPaaS. It at least proves CPaaS hits my Breeze.
Oh well. I'll try later...

Thanks!

I have the SMS URL set to https://pubsub.zang.io/ACf674eb32b98db1e91f8d4495b2e3670d/SMS/Incoming for my number.

I'ev also verified external connectivity. You can curl this and pop in a Canada/US number and you'll go through my SBC, to my Breeze and get a SMS back from CPaaS with a body of just your mobile number.

curl --location --request POST 'https://aoc15dc1brzedp1-sm100.suletmaaslab.ca/services/EventingConnector/events' --form 'family=sms' --form 'type=smsin' --form 'version=1.0' --form 'eventBody={"smsfrom":"15145551234"}'

For what it's worth, I see the following in my traces when I know I've sent messages to CPaaS - it looks like I get a 204 reply of no content. Does my CPaaS account need to be enabled somehow to use inbound SMS?

2020-10-31 14:04:10,193 [WorkManager.DefaultWorkManager : 3] ZangSmsConnector FINE - ZangSmsConnector-3.8.0.0.0990022 - com.avaya.services.zang.smsconnector.httpservices.HttpConnectionManager - OUTBOUND L:100.125.78.126 R:pubsub.zang.io HTTPS id:e8fe5481-0134-4f08-8b08-0570cec8fb16

GET https://pubsub.zang.io/ACf674eb32b98db1e91f8d4495b2e3670d/SMS/Incoming?session=e8fe5481-0134-4f08-8b08-0570cec8fb16&timeout=15s HTTP/1.1



--------------------



2020-10-31 14:04:12,242 [WorkManager.DefaultWorkManager : 1] ZangSmsConnector TRACE - ZangSmsConnector-3.8.0.0.0990022 - com.avaya.services.zang.smsconnector.poller.PollerResponseReader - checkResponseStatus() : status line HTTP/1.1 204

Success!

I wound up proxying Breeze outbound through my SBC just to see all the HTTP traffic in there rather than the logs, and lo and behold, I always get a 204 no content when there are no new messages, but I do actually get a 200 with the message when there is a message!

I guess I couldn't easily see in trace logs on the Eventing Connector or the SmsConnector that this was happening.

I wound up guessing that the event type "Message" and SMS_Incoming was the thing it published to the event bus and figured my way around.

Yay! I can receive SMS now!

Thanks for the tip on the URL required for the phone number. Is there any more up to date documentation around it? Did I miss something somewhere?