[SR-Users] Re: Regretfully we were unable to process the URI

Hi, Check on your Kamailio.cfg if this response is set. Most of the responses to SIP messages are setted in this file. Also I’m not sure if it’s related to this, but usually 479 is related to bad registrations. Check in your BBDD if there’s a user that matches your extension’s name Hope this

[SR-Users] Info: Next Kamailio World Conference - April 18-19, 2024, Berlin, Germany

Hello, a short announcement to inform that the dates for next Kamailio World Conference have been set to April 18-19, 2024, the event to take place again in Berlin, Germany. It will be a different venue than the past editions, that one not being available. A pre-conference day is considered on

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

Here's my last and best trick, which eliminates Kamailio entirely from being the culprit: *sipexer -options -contact-uri "sip:customers.teamsphone.net:5061;transport=tls" -fd "customers.teamsphone.net " -td "sip.pstnhub.microsoft.com

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

Let me explain you in more detail here. I have created a user under the main account fai...@7v840c.onmicrosoft.com in the portal admin.microsoft.com The user created with the domain used for SBC is abcsbc.com and the new user is faisal.ah...@abcsbc.com This domain abcsbc.com was verified

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

Other ideas would be: - who signed your cert - running behind some NAT, AWS or alike? At that point, some TLS traffic dump would help. You could for example enable the SIPDUMP module and see what exactly is sent out/received. Regards, Sergiu -- Teams PBX connector plus full MS Direct Routing

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

What's the role of faisal.ah...@abcsbc.com, is it Global Administrator? On Mon, Dec 18, 2023 at 4:38 PM faisal.jamil.khan--- via sr-users < sr-users@lists.kamailio.org> wrote: > when i tried to login via the user faisal.ah...@abcsbc.com on > admin.teams.microsoft.com, it gives me the error that

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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:

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

but I am checking my sngrep and there are no sip traffic coming back from Microsoft. And if it's the issue on just Kamailio but why MS teams direct routing sbc shows any tls or network activity. __ Kamailio - Users Mailing List - Non

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

the Global administrator is fai...@7v840c.onmicrosoft.com and this faisal.ah...@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

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

There you go, sipexer test passed, which means all good on the MS side. Alice/Bob uri username doesn't change anything here, ignore it. Another idea: do you have *force_rport* anywhere in the Kamailio script? Would be helpful to see the full script as well. Regards, Sergiu -- *Teams PBX

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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.

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

when i tried to login via the user faisal.ah...@abcsbc.com on admin.teams.microsoft.com, it gives me the error that you don't have access to the Teams admin center. __ Kamailio - Users Mailing List - Non Commercial Discussions To

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

*> 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

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

this is my tls config https://pastebin.com/RWBJcpuS this is the kamctl file https://pastebin.com/Cy4aCtbm __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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/ *? By default,

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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 fai...@7v840c.onmicrosoft.com but the domain for which we created SBC is abcsbc.com and we have an active user faisal.ah...@abcsbc.com under the

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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 wrote: > Here's my last and best trick, which

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

so you mean I have to login from the user faisal.ah...@abcsbc.com and then create the sbc there. but I have verified the domain in my fai...@7v840c.onmicrosoft.com. and then created the SBC. __ Kamailio - Users Mailing List - Non

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

Voila, that's likely your problem. *.onmicrosoft.com * domains are not eligible for Direct Routing. When activating the SBC, the UPN's domain part must be the same as the FQDN of the SBC you're adding. Essentially, you have to do it all within the *abcsbc.com

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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",

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

Also, try removing the port from dispatcher's destinations, URI like *sip:sip.pstnhub.microsoft.com ;transport=tls* Regards, Sergiu -- *Teams PBX connector plus full MS Direct Routing automation**Web*: https://teamsphone.net On Mon, Dec 18, 2023 at 2:17 PM

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

In response to "Ooops, obviously adjust the *-contact-uri* and *-fd* to your FQDN" where I need to add this, any specific code or guide where to add this. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an

[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 Admin Center , do you have an enrolled SBC? What's the status of TLS, SIP OPTIONS and Enabled status? What's

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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. -- Removed and restarted Kamailio to test with this setting, no impact 2. Are you sure Kamailio can read the cert and key files from

[SR-Users] Re: Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP

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