I assumed you read the famous article on Teams Direct Routing for Kamailio so I didn't bother mentioning it. https://skalatan.de/en/blog/kamailio-sbc-teams Regards, Sergiu -- *Teams PBX connector plus full MS Direct Routing automation**Web*: https://teamsphone.net On Fri, Dec 15, 2023 at 10:32 AM faisal.jamil.khan--- via sr-users < sr-users(a)lists.kamailio.org&gt; wrote:

# Add the Microsoft Teams-specific code here event_route[tm:local-request] { if(is_method("OPTIONS") && $ru =~ "pstnhub.microsoft.com") { append_hf("Contact: <sip:abcsbc.com:5061;transport=tls>\r\n"); } xlog("L_INFO", "Sent out tm request: $mb\n"); } are you talking about this ?

You didn't confirm if Contact was added to OPTIONS for local requests. In Teams <https://admin.teams.microsoft.com/direct-routing/v2> Admin Center <https://admin.teams.microsoft.com/direct-routing/v2>, do you have an enrolled SBC? What's the status of TLS, SIP OPTIONS and Enabled status? What's the result of: *kamcmd dns.lookup SRV _sips._tcp.sip.pstnhub.microsoft.com <http://tcp.sip.pstnhub.microsoft.com>* Can you ping sip.pstnhub.microsoft.com? On Mon, Dec 18, 2023 at 1:05 PM faisal.jamil.khan--- via sr-users < sr-users(a)lists.kamailio.org&gt; wrote:

new updated list according to the SRV records and after removing tls port. 1 sip:sip.pstnhub.microsoft.com;transport=tls 0 10 socket=tls:172.31.19.8;ping_from=sip:abcsbc.com 1 sip:sip2.pstnhub.microsoft.com;transport=tls 0 20 socket=tls:172.31.19.8;ping_from=sip:abcsbc.com 1 sip:sip3.pstnhub.microsoft.com;transport=tls 0 30 socket=tls:172.31.19.8;ping_from=sip:abcsbc.com 1 sip:sip4.pstnhub.microsoft.com;transport=tls 0 40 socket=tls:172.31.19.8;ping_from=sip:abcsbc.com

Ooops, obviously adjust the *-contact-uri* and *-fd* to your FQDN Regards, Sergiu -- *Teams PBX connector with full MS Direct Routing automation for service providers**Web*: https://teamsphone.net On Mon, Dec 18, 2023 at 3:35 PM Sergiu Pojoga &lt;pojogas(a)gmail.com&gt; wrote:

Hi there, Just to add to the above, I had a similar issue not so long ago where I was getting replies to my OPTIONS from my dispatcher destinations, but then they started rejecting them (for some unknown reason) causing all my dd's to go into flag: IP state. I just removed my probing to those carriers in the end. Not ideal, but it solved my immediate issue. I would confirm that the Teams Direct Routing endpoints reliably respond to all OPTIONs packets first. Or maybe just disable the probing for now as the default value for ds_probing_threshold is just "1" so any missed packets will change the flag on a default dispatcher config. Hope it helps. John. On Mon, 18 Dec 2023 at 20:57, Sergiu Pojoga via sr-users < sr-users(a)lists.kamailio.org&gt; wrote:

*> but I am checking my sngrep and there are no sip traffic coming back from Microsoft.* sngrep won't show anything, the traffic to/from MS is encrypted. You'll need to install and configure something like SIPDUMP or HEP. I'm afraid this isn't the easiest of tasks for someone who seems to be just getting started with VoIP. Too many things to consider in this task. Run the below to check if MS replies back. Besides that, I did what I could to help over email. Good luck! *sipexer* -options -contact-uri "sip:abcsbc.com:5061;transport=tls" -fd " abcsbc.com" -td "sip.pstnhub.microsoft.com;transport=tls" \ -tls-certificate "/usr/local/etc/kamailio/bundle.crt" -tls-key "/usr/local/etc/kamailio/privkey.pem" \ -xh "Max-Forwards: 70" -ua "Ribbon-SIPGateway" "sip:sip.pstnhub.microsoft.com:5061;transport=tls" Note: adjust certs path and FQDN, if needed. Regards, Sergiu -- *Teams PBX connector plus full MS Direct Routing automation**Web*: https://teamsphone.net On Mon, Dec 18, 2023 at 5:01 PM faisal.jamil.khan--- via sr-users < sr-users(a)lists.kamailio.org&gt; wrote:

This is from the section in the link you mentioned (https://skalatan.de/en/blog/kamailio-sbc-teams) # Add the Microsoft Teams-specific code here event_route[tm:local-request] { if(is_method("OPTIONS") && $ru =~ "pstnhub.microsoft.com") { append_hf("Contact: <sip:abcsbc.com:5061;transport=tls>\r\n"); } xlog("L_INFO", "Sent out tm request: $mb\n"); } I have added this in my code after the section # Wrapper for relaying requests route[RELAY] { ----- Continue scripts ----- Below is my Teams admin Center: kamcmd dns.lookup SRV _sips._tcp.sip.pstnhub.microsoft.com { name: _sips._tcp.sip.pstnhub.microsoft.com type: SRV size_bytes: 360 reference_counter: 2 permanent: no expires: 3600 last_used: 0 negative_entry: no records: { { rr_idx: 0 rr_name: sip.pstnhub.microsoft.com rr_port: 5061 rr_priority: 10 rr_weight: 0 rr_permanent: no rr_expires: 3600 } { rr_idx: 1 rr_name: sip2.pstnhub.microsoft.com rr_port: 5061 rr_priority: 20 rr_weight: 0 rr_permanent: no rr_expires: 3600 } { rr_idx: 2 rr_name: sip3.pstnhub.microsoft.com rr_port: 5061 rr_priority: 30 rr_weight: 0 rr_permanent: no rr_expires: 3600 } { rr_idx: 3 rr_name: sip4.pstnhub.microsoft.com rr_port: 5061 rr_priority: 40 rr_weight: 0 rr_permanent: no rr_expires: 3600 } } } From: Sergiu Pojoga &lt;pojogas(a)gmail.com&gt; Sent: Tuesday, December 19, 2023 12:18 AM To: Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.kamailio.org&gt; Cc: faisal.jamil.khan(a)gmail.com Subject: Re: [SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP You didn't confirm if Contact was added to OPTIONS for local requests. In Teams <https://admin.teams.microsoft.com/direct-routing/v2> Admin Center <https://admin.teams.microsoft.com/direct-routing/v2> , do you have an enrolled SBC? What's the status of TLS, SIP OPTIONS and Enabled status? What's the result of: kamcmd dns.lookup SRV _sips._tcp.sip.pstnhub.microsoft.com <http://tcp.sip.pstnhub.microsoft.com> Can you ping sip.pstnhub.microsoft.com <http://sip.pstnhub.microsoft.com> ? On Mon, Dec 18, 2023 at 1:05 PM faisal.jamil.khan--- via sr-users &lt;sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > wrote: kamctl dispatcher dump { "jsonrpc": "2.0", "result": { "NRSETS": 1, "RECORDS": [{ "SET": { "ID": 1, "TARGETS": [{ "DEST": { "URI": "sip:sip.pstnhub.microsoft.com:5061;transport=tls", "FLAGS": "IP", "PRIORITY": 3, "ATTRS": { "BODY": "socket=tls:172.31.19.8:5061 <http://172.31.19.8:5061> ;ping_from=sip:abcsbc.com <http://abcsbc.com> ", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls:172.31.19.8:5061 <http://172.31.19.8:5061> ", "SOCKNAME": null, "OBPROXY": null } } }, { "DEST": { "URI": "sip:sip2.pstnhub.microsoft.com:5061;transport=tls", "FLAGS": "IP", "PRIORITY": 2, "ATTRS": { "BODY": "socket=tls:172.31.19.8:5061 <http://172.31.19.8:5061> ;ping_from=sip:abcsbc.com <http://abcsbc.com> ", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls:172.31.19.8:5061 <http://172.31.19.8:5061> ", "SOCKNAME": null, "OBPROXY": null } } }, { "DEST": { "URI": "sip:sip3.pstnhub.microsoft.com:5061;transport=tls", "FLAGS": "IP", "PRIORITY": 1, "ATTRS": { "BODY": "socket=tls:172.31.19.8:5061 <http://172.31.19.8:5061> ;ping_from=sip:abcsbc.com <http://abcsbc.com> ", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls:172.31.19.8:5061 <http://172.31.19.8:5061> ", "SOCKNAME": null, "OBPROXY": null } } }] } }] }, "id": 19731 } My dispatcher settings. i am unable to get the trunk up with Microsoft . Can someone guide me how to fix this issue? __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org <mailto:sr-users-leave@lists.kamailio.org> Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:

Kamailio is installed on AWS obviously behind NAT. Cert signed: Let's ecncrypt However, I have a questions here: I have a registered account at faisal(a)7v840c.onmicrosoft.com but the domain for which we created SBC is abcsbc.com and we have an active user faisal.ahmad(a)abcsbc.com under the domain. We have created the SBC under voice routing on this account faisal(a)7v840c.onmicrosoft.com. SBC Network effectiveness TLS connectivity status SIP OPtions status abcsbc.com 0% Inactive Warning Is this the correct way to setup SBC under the main account or should I have to create the sbc by logging in to the account of faisal.ahmad(a)abcsbc.com.

so you mean I have to login from the user faisal.ahmad(a)abcsbc.com and then create the sbc there. but I have verified the domain in my faisal(a)7v840c.onmicrosoft.com. and then created the SBC.

when i tried to login via the user faisal.ahmad(a)abcsbc.com on admin.teams.microsoft.com, it gives me the error that you don't have access to the Teams admin center.

the Global administrator is faisal(a)7v840c.onmicrosoft.com and this faisal.ahmad(a)abcsbc.com is the user created for the domain abcsbc.com. The global account is the development test account with the Teams license without calling. But with this license you will be able to test the Teams trunking. here you go for the sipexer test below and it's successful but in the sngrep I see the options packet for alice without this command on udp when executing the default command for sipexer. ./sipexer -options -contact-uri "sip:abcsbc.com:5061;transport=tls" -fd "abcsbc.com" -td "sip.pstnhub.microsoft.com;transport=tls" -tls-insecure -tls-certificate "/etc/letsencrypt/live/abcsbc.com/fullchain.pem" -tls-key "/etc/letsencrypt/live/abcsbc.com/privkey.pem" -xh "Max-Forwards: 70" -ua "Kamailio" "sip:sip.pstnhub.microsoft.com:5061;transport=tls" [info] [sipexer.go:1581] main.SIPExerDialogLoop(): local socket address: 172.31.19.8:51882 (tls) [info] [sipexer.go:1582] main.SIPExerDialogLoop(): local via address: 172.31.19.8:51882 [info] [sipexer.go:1583] main.SIPExerDialogLoop(): sending to tls 52.114.148.0:5061: [[--- OPTIONS sip:sip.pstnhub.microsoft.com:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 172.31.19.8:51882;rport;branch=z9hG4bKSG.c031ebff-3cd4-4eb3-8c71-f82b3bc41b30 From: <sip:alice@abcsbc.com>;tag=5134186d-6804-419e-8abc-99cfe607e3b1 To: <sip:bob@sip.pstnhub.microsoft.com;transport=tls> Call-ID: 73f563c9-6647-4402-be59-361e4a1d40c0 CSeq: 44075 OPTIONS Date: Mon, 18 Dec 2023 22:07:12 UTC Contact: <sip:abcsbc.com:5061;transport=tls> User-Agent: Kamailio Max-Forwards: 10 Content-Length: 0 Max-Forwards: 70 [info] [sipexer.go:1585] main.SIPExerDialogLoop(): ---]] [info] [sipexer.go:1636] main.SIPExerDialogLoop(): response-received: from=52.114.148.0:5061 bytes=441 data=[[--- SIP/2.0 200 OK FROM: <sip:alice@abcsbc.com>;tag=5134186d-6804-419e-8abc-99cfe607e3b1 TO: <sip:bob@sip.pstnhub.microsoft.com;transport=tls> CSEQ: 44075 OPTIONS CALL-ID: 73f563c9-6647-4402-be59-361e4a1d40c0 VIA: SIP/2.0/TLS 172.31.19.8:51882;branch=z9hG4bKSG.c031ebff-3cd4-4eb3-8c71-f82b3bc41b30;rport CONTENT-LENGTH: 0 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY SERVER: Microsoft.PSTNHub.SIPProxy v.2023.12.11.2 i.USWE2.3 [info] [sipexer.go:1638] main.SIPExerDialogLoop(): ---]]

No problem I am sharing the full code of Kamailio.cfg and dispatcher active list. Here below is my kamailio.cfg https://pastebin.com/B7yeWBvg this below is dispatcher.list https://pastebin.com/qx77Bvi8 if anyother code required you can ask me. And really thankful to helping me in this.

Two things: 1. You're not paying attention. Previously, I asked if there's *force_rport()* in your kam config. Looks like you do. Remove it from the REQINIT route. 2. Are you sure Kamailio can read the cert and key files from */etc/letsencrypt/live/**abcsbc.com/ <http://abcsbc.com/>*? By default, those files may not be readable by kamailio, depending if you run it under root or kamailio user. Change the folder permissions or better yet copy the cert and key to some /tmp/ folder and adjust config for testing purpose sake. 3. You don't need *[server:172.31.19.8:5061 <http://172.31.19.8:5061>] & [client:172.31.19.8:5061 <http://172.31.19.8:5061>]* definitions in tls.cfg, default will suffice. 4. To avoid all this back and forth, enable debugging <https://kamailio.org/docs/modules/devel/modules/debugger.html> in Kamailio and see if there's any errors like Kam not being able to load certs and priv keys e.t.c Regards, Sergiu -- *Teams PBX connector plus full MS Direct Routing automation**Web*: https://teamsphone.net On Mon, Dec 18, 2023 at 8:21 PM faisal.jamil.khan--- via sr-users < sr-users(a)lists.kamailio.org&gt; wrote:

Here 's the problem From the logs of dispatcher, I have pasted below only one log of dispatcher failure. it seems to be timeout from microsoft. Dec 19 06:16:46 curemsteamssbc /usr/sbin/kamailio[30957]: DEBUG: dispatcher [dispatch.c:3680]: ds_options_callback(): OPTIONS-Request was finished with code 408 (to sip:sip3.pstnhub.microsoft.com;transport=tls, group 1) This dispatcher log clearly showing that Option request was finished with 408 from Microsoft. so it means Kamailio is not receiving back anything from Microsoft for it's Option request. what you suggest now ?

Hahah LOL seriously I am just sucked up. It's all good. We have not detected any issues. Hostname: Matches Common Name or/and SAN Expired: No (78 days till expiration) Public Key: We were unable to find any issues in the public key of end-entity certificate Trusted: Yes, we were able to verify the certificate Self-Signed: No, the end-entity certificate is not self-signed Chain Issues: No, we were unable to detect any issues in the certificate chain sent by the server Weak signatures: No, certificates sent by the server were not signed utilizing a weak hash function OCSP Status: OCSP Responder returned "good" status for the end-entity certificate I have flowroute Carrier, Can we setup trunk with Flowroute to test if it works fine or not. in this way at least we can test our kamailio if it works fine. should I create the Flowroute trunk in the same way as it also has techprefix, username and password.