ICYMI: Last week I got #Doom running on an
@ribboncomm#SBC1000. Here's an article going into how I got it working for all @Foone's and @lazygamereviews' fans. (Skype4B engineers already know how!)
https://t.co/kbbjA6skNP
@ricsip82@ribboncomm The disadvantage is now, I don't just need to support what the carrier sends me, but also whatever the far PBX/Phone decides to send too! Mainly because carriers don't need get into the actual call, so they just make it your SBC's problem. 3/3
Ran into an issue recently where a @ribboncomm SBC2K worked with #MSTeams, but a SWe Lite with the same IP/Ports didn't. The issue was very interesting, so I figured I'd drop this article and explain NAT, ICE-Lite, and STUN in depth.
https://t.co/tLwcSCIKtS
@ricsip82@ribboncomm In both a blessing and a curse. (mostly thanks to mobiles moving to SIP) carriers peer using SIP nowadays, so that weird SIP header your iPhone generates? Yeah, my SBC see's all the junk in there too. The advantages is being able to use 22Khz audio instead of 8khz. 2/3
@ricsip82 That's the point. With the industry moving to ACME, it makes perfect sense for the SBC vendors to do it as well. @anynodeSBC already does, why cant everyone else? Especially the ones that offer physcial hardware.
TLS certificates are changing. SBCs haven’t. And that gap is about to start breaking Teams Direct Routing in very real ways. I’ve written up what the move to 47‑day certificates actually means for SBCs, why “just use the API” isn’t good enough.
https://t.co/chXZSShupz
@theatretwitt This is my point, especially when vendors cry "we are Microsoft Teams certified"
Hey @ilyabu, thoughts on making ACME certificate renewal part of the certification? Happy to talk about this offline.
#MicrosoftTeams and #Skype4B Telephony nerds.
With TLS cert lifetime changes forcing automation of renewals. Is your vendor planning to support ACME protocol? Do you think the burden lies on the vendors to support this or customers? 1/?
I'm thinking about building something, but it's going to be tricky, especially when the TLS vendors expect either DNS changes or a Web challenge for validation that only lasts 10 days.
I've spoken with one vendor who shall remain nameless until their public statement. Their engineering has said they are aware of the issue and have no plans implement ACME and are instead asking customers to write code to use their API 2/?
I really need to get around to finishing the documentation and releasing this.
I just saved half an hour trying to find a transformation table entry in a Ribbon SBC by punching the numbers and config in here
Update to my Search-UxCallLog.ps1 script.
reports on what RegEx rules were evaluated, what failed and the last successful test was!
Oh, and we warn about unrouteable calls now too!
Not to mention performance increases and folder path support too!
https://t.co/DUIHrRNY1e
I might have gotten a little carried away.
I wanted a way to simulate call routing on Ribbon SBC's
Parses a config file, finds Routes > TransTables > Rules. Marks disabled routes, warns for AD rules (cant simulate those)
Not bad for a few hours with #GitHubCopilot
@ribboncomm (there's a mistake in the image, I should have said, "its clearly 3.1.3" not 3.3.3)
Route Table 3
Transformation Table 1
Transformation Rule 3
When you go looking for a bug in your @ribboncomm SBC Log parsing script. Only to find the SBC itself is writing the wrong stuff to a logfile.
I'm going to have a fun one explaining this to support...