Where I can check that ?

yes I followed all the steps from this article.

This is the only complete guide available so far.

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;ping_from=sip:abcsbc.com", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls: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;ping_from=sip:abcsbc.com", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls: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;ping_from=sip:abcsbc.com", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls: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?

Also, try removing the port from dispatcher's destinations, URI like

*sip:sip.pstnhub.microsoft.com http://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 Sergiu Pojoga pojogas@gmail.com wrote:

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@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;ping_from=sip: abcsbc.com", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls: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;ping_from=sip: abcsbc.com", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls: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;ping_from=sip: abcsbc.com", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls: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@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:

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 http://customers.teamsphone.net" -td "sip.pstnhub.microsoft.com http://sip.pstnhub.microsoft.com;transport=tls" -tls-insecure -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"*

If you don't get a reply from Microsoft.PSTNHub then something is awkwardly wrong in your setup, not related to Kamailio, likely Teams backend config or networking.

Note:

(1) adjust certs path to your case

(2) install sipexer if you don't have it: https://github.com/miconda/sipexer

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:23 PM faisal.jamil.khan--- via sr-users < sr-users@lists.kamailio.org> 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 __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to 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:

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.

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.

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(): ---]]

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 automation *Web*: https://teamsphone.net

On Mon, Dec 18, 2023 at 2:53 PM faisal.jamil.khan@gmail.com 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 pojogas@gmail.com *Sent:* Tuesday, December 19, 2023 12:18 AM *To:* Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org *Cc:* faisal.jamil.khan@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?

On Mon, Dec 18, 2023 at 1:05 PM faisal.jamil.khan--- via sr-users < 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;ping_from=sip: abcsbc.com", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls: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;ping_from=sip: abcsbc.com", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls: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;ping_from=sip: abcsbc.com", "DUID": null, "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls: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@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:

Voila, that's likely your problem.

*.onmicrosoft.com http://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 http://abcsbc.com* AAD tenant, logged in as a superuser part of the same *abcsbc.com http://abcsbc.com* domain, matching the SBC's 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:47 PM faisal.jamil.khan--- via sr-users < sr-users@lists.kamailio.org> wrote:

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

We have created the SBC under voice routing on this account faisal@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@abcsbc.com. __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to 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:

Let me explain you in more detail here.

I have created a user under the main account faisal@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.ahmad@abcsbc.com

This domain abcsbc.com was verified from the main account faisal@7v840c.onmicrosoft.com and I have added all the routes to my AWS domain registrar from Microsoft.

So what do you think now?

What's the role of faisal.ahmad@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.ahmad@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 unsubscribe send an email to 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:

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 connector plus full MS Direct Routing automation**Web*: https://teamsphone.net

On Mon, Dec 18, 2023 at 5:33 PM faisal.jamil.khan--- via sr-users < sr-users@lists.kamailio.org> wrote:

the Global administrator is faisal@7v840c.onmicrosoft.com and this faisal.ahmad@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(): ---]] __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to 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:

this is my tls config

https://pastebin.com/RWBJcpuS

this is the kamctl file https://pastebin.com/Cy4aCtbm

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

-- Yes, it's reading the certificates because otherwise it gives the permissions error at Kamailio start and won't listen on tls port. tls: 172.31.19.8:5061 advertise abcsbc.com:5061

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.

-- I already tested this with default but because it's on AWS so it looks for tls and sni back at the local ip at the socket. and when we don't define it, it will give the following error which I already opened the case and fixed it with these settings and now tls hanshake is successful.

Error: Dec 12 19:32:55 abcsbc.com /usr/sbin/kamailio[23865]: ERROR: tls [tls_util.h:49]: tls_err_ret(): TLS write:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed (sni: unknown)

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

-- I have enabled the debugging logs with the following configs and after the restart kamailio.log is in the pastebin link. ####### Global Parameters #########

/* LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR, ... */ #debug=DBGLEVEL debug=3

/* set to 'yes' to print log messages to terminal or use '-E' cli option */ log_stderror=no

memdbg=5 memlog=5

log_facility=LOG_LOCAL0 log_prefix="{$mt $hdr(CSeq) $ci} "

https://pastebin.com/t9Kjmh1J

*> what you suggest now ?*

Start praying? LOL

Do an SSL test, any issues? https://decoder.link/sslchecker/abcsbc.com/5061

Regards,

On Tue, Dec 19, 2023 at 1:46 AM faisal.jamil.khan--- via sr-users < sr-users@lists.kamailio.org> 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 ? __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to 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: