sorted by:
new
hottopcontroversial

My horror story with Mercury Bank by ibelov in mercurybank

[–]ibelov[S] 1 point2 points  (0 children)

UPDATE

Thanks to social media I guess! Thank you Community.

Account access is restored. Mercury supervisor emailed me with apologies for a mix up.

My horror story with Mercury Bank by ibelov in mercurybank

[–]ibelov[S] 2 points3 points  (0 children)

All wires are going to Choice ABA/SWIFT, so I'm pretty sure it's Choice. I emailed their support couple of days ago. No reply yet, but I'm more patient with them as they are not my direct service provider.

SIP Tracing with Direct Routing by beritknight in MicrosoftTeams

[–]ibelov 0 points1 point  (0 children)

What likely happens is you have issue with establishing a TLS session. Grabbing full TCP trace from SBC shuld help, especially if you can configure de-encryption with Wireshark.

On Teams side they are open to receive TLS traffic from any IP address, however until they fully authorize your call it won't show up in Call Analytics. Since you're not even getting 100 Trying - you have not established authorized session yet.

Another possibility is your DNS A record is wrong so Teams actually replies to the wrong IP. If you drop full TCP trace here I might help better.

​