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!