Re: [OpenSIPS-Users] Ms Teams to SBC call not working

[Devang Dhandhalya via Users]

Hello Rehan,

Thank you for the response

I have configured this dialed pattern : ^+91(\d{10})$ and select My SBC
which I have configured in Direct routing.
I assigned a phone number and Direct routing for my user using Microsoft
Teams admin center portal.
I configure voice routing policy as well and not assign PSTN usage Record
in it
Also configured dialplan with dial pattern: ^+91(\d{10})$ and voice routing
policy and dialplan is also assigned to my user

Please let me know if I miss any further configuration in MS Teams.

Regards,
Devang Dhandhalya



On Mon, Apr 22, 2024 at 10:20 PM Ahmed Rehan  wrote:

> Check your Voice Routing policy to the user you are calling from and also
> check the Route which is matching your dialed number has been assigned the
> SBC you have configured.
>
> On Mon, Apr 22, 2024 at 4:54 PM Devang Dhandhalya via Users <
> users@lists.opensips.org> wrote:
>
>> Hello All,
>>
>> I Configured Direct routing and all status related to SBC connectivity
>> are good and also Configured Voice routes with SBC for my user.
>> I am facing one issue for calls from MS Teams to SBC and getting below
>> error on MS teams Screen:
>>
>>
>> *We couldn't connect the call.With your calling license, you can only
>> call people within your organization. Talk to your IT admin to change your
>> license.*
>> What are the possible reasons for this error?
>>
>> Note: SBC to MS Teams Calls are working fine.
>>
>> I have configured below License in MS Teams account
>>
>> 1 ) Microsoft Teams Phone Standard
>> 2 ) Microsoft Teams
>> 3 ) Microsoft 365 Audio Conferencing
>>
>> Can Anyone tell me if I am missing any other license for Making outbound
>> calls from MS Teams to SBC using Direct routing?
>> Let me know if you require any further information related to MS Teams
>> Configuration.
>> Any suggestions would be appreciated.
>>
>> Many Thanks,
>> Devang Dhandhalya
>>
>>
>> *[image: https://www.ecosmob.com/opensips-summit/]
>> *
>> *Disclaimer*
>> In addition to generic Disclaimer which you have agreed on our website,
>> any views or opinions presented in this email are solely those of the
>> originator and do not necessarily represent those of the Company or its
>> sister concerns. Any liability (in negligence, contract or otherwise)
>> arising from any third party taking any action, or refraining from taking
>> any action on the basis of any of the information contained in this email
>> is hereby excluded.
>>
>> *Confidentiality*
>> This communication (including any attachment/s) is intended only for the
>> use of the addressee(s) and contains information that is PRIVILEGED AND
>> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
>> of this communication is prohibited. Please inform originator if you have
>> received it in error.
>>
>> *Caution for viruses, malware etc.*
>> This communication, including any attachments, may not be free of
>> viruses, trojans, similar or new contaminants/malware, interceptions or
>> interference, and may not be compatible with your systems. You shall carry
>> out virus/malware scanning on your own before opening any attachment to
>> this e-mail. The sender of this e-mail and Company including its sister
>> concerns shall not be liable for any damage that may incur to you as a
>> result of viruses, incompleteness of this message, a delay in receipt of
>> this message or any other computer problems.
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
> --
> Regards
> Ahmed Rehan
>


-- 
Regards,
*Devang Dhandhalya*

[image: Ecosmob Technologies Pvt. Ltd.] 

Ecosmob Technologies Pvt. Ltd.
https://www.ecosmob.com

VoIP | Web | Mobile | IoT | Big Data

-- 
* 
*
*Disclaimer*

In addition to 
generic Disclaimer which you have agreed on our website, any views or 
opinions presented in this email are solely those of the originator and do 
not necessarily represent those of the Company or its sister concerns. Any 
liability (in negligence, contract or otherwise) arising from any third 
party taking any action, or refraining from taking any action on the basis 
of any of the information contained in this email is hereby excluded.



*Confidentiality*
This communication (including any attachment/s) is 
intended only for the use of the addressee(s) and contains information that 
is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, 
distribution, or copying of this communication is prohibited. Please inform 
originator if you have received it in error.


*Caution for viruses, 
malware etc.*
This communication, including any attachments, may not be 
free of viruses, trojans, similar or new contaminants/malware, 
interceptions or interference, and may not be compatible with your systems. 
You shall carry out virus/malware scan

Re: [OpenSIPS-Users] Ms Teams to SBC call not working

[Ahmed Rehan]

Check your Voice Routing policy to the user you are calling from and also
check the Route which is matching your dialed number has been assigned the
SBC you have configured.

On Mon, Apr 22, 2024 at 4:54 PM Devang Dhandhalya via Users <
users@lists.opensips.org> wrote:

> Hello All,
>
> I Configured Direct routing and all status related to SBC connectivity are
> good and also Configured Voice routes with SBC for my user.
> I am facing one issue for calls from MS Teams to SBC and getting below
> error on MS teams Screen:
>
>
> *We couldn't connect the call.With your calling license, you can only call
> people within your organization. Talk to your IT admin to change your
> license.*
> What are the possible reasons for this error?
>
> Note: SBC to MS Teams Calls are working fine.
>
> I have configured below License in MS Teams account
>
> 1 ) Microsoft Teams Phone Standard
> 2 ) Microsoft Teams
> 3 ) Microsoft 365 Audio Conferencing
>
> Can Anyone tell me if I am missing any other license for Making outbound
> calls from MS Teams to SBC using Direct routing?
> Let me know if you require any further information related to MS Teams
> Configuration.
> Any suggestions would be appreciated.
>
> Many Thanks,
> Devang Dhandhalya
>
>
> *[image: https://www.ecosmob.com/opensips-summit/]
> *
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our website,
> any views or opinions presented in this email are solely those of the
> originator and do not necessarily represent those of the Company or its
> sister concerns. Any liability (in negligence, contract or otherwise)
> arising from any third party taking any action, or refraining from taking
> any action on the basis of any of the information contained in this email
> is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for the
> use of the addressee(s) and contains information that is PRIVILEGED AND
> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
> of this communication is prohibited. Please inform originator if you have
> received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of viruses,
> trojans, similar or new contaminants/malware, interceptions or
> interference, and may not be compatible with your systems. You shall carry
> out virus/malware scanning on your own before opening any attachment to
> this e-mail. The sender of this e-mail and Company including its sister
> concerns shall not be liable for any damage that may incur to you as a
> result of viruses, incompleteness of this message, a delay in receipt of
> this message or any other computer problems.
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Regards
Ahmed Rehan
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Ms Teams to SBC call not working

[Devang Dhandhalya via Users]

Hello All,

I Configured Direct routing and all status related to SBC connectivity are
good and also Configured Voice routes with SBC for my user.
I am facing one issue for calls from MS Teams to SBC and getting below
error on MS teams Screen:


*We couldn't connect the call.With your calling license, you can only call
people within your organization. Talk to your IT admin to change your
license.*
What are the possible reasons for this error?

Note: SBC to MS Teams Calls are working fine.

I have configured below License in MS Teams account

1 ) Microsoft Teams Phone Standard
2 ) Microsoft Teams
3 ) Microsoft 365 Audio Conferencing

Can Anyone tell me if I am missing any other license for Making outbound
calls from MS Teams to SBC using Direct routing?
Let me know if you require any further information related to MS Teams
Configuration.
Any suggestions would be appreciated.

Many Thanks,
Devang Dhandhalya

-- 
* 
*
*Disclaimer*

In addition to 
generic Disclaimer which you have agreed on our website, any views or 
opinions presented in this email are solely those of the originator and do 
not necessarily represent those of the Company or its sister concerns. Any 
liability (in negligence, contract or otherwise) arising from any third 
party taking any action, or refraining from taking any action on the basis 
of any of the information contained in this email is hereby excluded.



*Confidentiality*
This communication (including any attachment/s) is 
intended only for the use of the addressee(s) and contains information that 
is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, 
distribution, or copying of this communication is prohibited. Please inform 
originator if you have received it in error.


*Caution for viruses, 
malware etc.*
This communication, including any attachments, may not be 
free of viruses, trojans, similar or new contaminants/malware, 
interceptions or interference, and may not be compatible with your systems. 
You shall carry out virus/malware scanning on your own before opening any 
attachment to this e-mail. The sender of this e-mail and Company including 
its sister concerns shall not be liable for any damage that may incur to 
you as a result of viruses, incompleteness of this message, a delay in 
receipt of this message or any other computer problems. 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams, reinvite after ACK

[Jeff Pyle]

Right.  Something like this:

if (list_hdr_has_option("Allow", "REFER"))
list_hdr_remove_option("Allow", "REFER");

We've used blind transfer successfully.  If I remember correctly it will
utilize re-INVITEs, possibly with Replaces.  I don't know that we've tested
attended transfer.

OpenSIPS is just a proxy (in this case), so it will pass the REFER just
fine.  You'd probably have to do a lot of cleanup of the Refer-to value to
make it usable in this case...I haven't checked.  It all depends on what
you have upstream and what it can handle.  We opted to strip REFER for
simplicity.


- Jeff


On Wed, Jun 2, 2021 at 5:38 AM Miha via Users 
wrote:

> yes. Thank you.
>
> is there any way to get also attended transfer working?
>
> Johan De Clercq je 6/2/2021 ob 11:21 AM napisal:
>
> remove Refer from your supported methods.
> Do note that attended transfer will not work in this case.
>
> wkr,
>
> Op wo 2 jun. 2021 om 10:15 schreef Miha via Users <
> users@lists.opensips.org>:
>
>> Hello
>>
>> i manage to fix this. I did not do t_relay() also seq Invites, after this
>> everything works ok.
>>
>> Just on question, regarding transfers, i see that MS Teams send REFER in
>> which trafter is defined. How do you deal with this? You do not allow REFER
>> from MS teams and hope that MS teams will send new INVITE?
>>
>>
>> thank you
>> miha
>>
>> Jeff Pyle je 6/1/2021 ob 3:26 PM napisal:
>>
>> Miha,
>>
>> First, do you need to use "mtsbc.test.com:5060" in the first
>> record_route_preset() param?  Can you use the IP address of your proxy
>> instead?  FQDNs are legal of course, but outside of MS Teams'
>> implementation, they're rarely required.  It's just another thing to go
>> wrong.  Especially while testing.
>>
>> The ACK to the 200 OK is a sequential (in-dialog) request.  It's not part
>> of the original INVITE transaction.  Your script will have a section like
>>
>> if (has_totag()) {
>> if (loose_route()) {
>> t_relay();
>> }
>> }
>>
>> for sequential requests through a loose-routing proxy.  This is very
>> oversimplified and yours will have more.  In this section, however, is
>> where you'll process the ACK because it has a to-tag (line 293) and a route
>> header (line 298) so the conditions match.
>>
>> Use xlogs or the debug tool of your choice to diagnose what's happening
>> in this section with the ACK.  In my scripts, I use global flag 0 to
>> indicate when I want logging.  So, I might have something like this:
>>
>>if (has_totag()) {
>>if (is_gflag(0)) xlog("L_NOTICE", " ...in-dialog $rm
>> request\n");
>># ...do all the things...maybe more logging like the line
>> above...
>>
>>
>> - Jeff
>>
>>
>> On Tue, Jun 1, 2021 at 4:57 AM Miha via Users 
>> wrote:
>>
>>> Hello
>>>
>>>
>>> I have an issue and I am unable to find out what is wrong. Incoming
>>> calls are working but when doing outbound call after 200OK, which is send
>>> to Teams I get back ACK and after that Teams do again initial. I guess this
>>> is not ok.
>>>
>>> I am doing this for outband calls:
>>>
>>>
>>> xlog("L_INFO", "rtp rtps record route");
>>> record_route_preset("mtsbc.test.com:5060","mtsbc.test.com
>>> :5061;transport=tls");
>>> add_rr_param(";r2=on");
>>>
>>> I am pasting here trace. Opensips is in the middle.
>>>
>>> Thank you for help!
>>>
>>> https://pastebin.com/qM0dMiCc
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams, reinvite after ACK

[Miha via Users]

yes. Thank you.

is there any way to get also attended transfer working?

Johan De Clercq je 6/2/2021 ob 11:21 AM napisal:

remove Refer from your supported methods.
Do note that attended transfer will not work in this case.

wkr,

Op wo 2 jun. 2021 om 10:15 schreef Miha via Users 
mailto:users@lists.opensips.org>>:


Hello

i manage to fix this. I did not do t_relay() also seq Invites,
after this everything works ok.

Just on question, regarding transfers, i see that MS Teams send
REFER in which trafter is defined. How do you deal with this? You
do not allow REFER from MS teams and hope that MS teams will send
new INVITE?


thank you
miha

Jeff Pyle je 6/1/2021 ob 3:26 PM napisal:

Miha,

First, do you need to use "mtsbc.test.com:5060
" in the first record_route_preset()
param?  Can you use the IP address of your proxy instead?  FQDNs
are legal of course, but outside of MS Teams' implementation,
they're rarely required.  It's just another thing to go wrong. 
Especially while testing.

The ACK to the 200 OK is a sequential (in-dialog) request.  It's
not part of the original INVITE transaction.  Your script will
have a section like

if (has_totag()) {
if (loose_route()) {
t_relay();
}
}

for sequential requests through a loose-routing proxy.  This is
very oversimplified and yours will have more.  In this section,
however, is where you'll process the ACK because it has a to-tag
(line 293) and a route header (line 298) so the conditions match.

Use xlogs or the debug tool of your choice to diagnose what's
happening in this section with the ACK.  In my scripts, I use
global flag 0 to indicate when I want logging.  So, I might have
something like this:

   if (has_totag()) {
   if (is_gflag(0)) xlog("L_NOTICE", "...in-dialog
$rm request\n");
# ...do all the things...maybe more logging like the line above...


- Jeff


On Tue, Jun 1, 2021 at 4:57 AM Miha via Users
mailto:users@lists.opensips.org>> wrote:

Hello


I have an issue and I am unable to find out what is wrong.
Incoming calls are working but when doing outbound call after
200OK, which is send to Teams I get back ACK and after that
Teams do again initial. I guess this is not ok.

I am doing this for outband calls:


xlog("L_INFO", "rtp rtps record route");
record_route_preset("mtsbc.test.com:5060
","mtsbc.test.com
:5061;transport=tls");
add_rr_param(";r2=on");

I am pasting here trace. Opensips is in the middle.

Thank you for help!

https://pastebin.com/qM0dMiCc 
___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams, reinvite after ACK

[Johan De Clercq]

remove Refer from your supported methods.
Do note that attended transfer will not work in this case.

wkr,

Op wo 2 jun. 2021 om 10:15 schreef Miha via Users :

> Hello
>
> i manage to fix this. I did not do t_relay() also seq Invites, after this
> everything works ok.
>
> Just on question, regarding transfers, i see that MS Teams send REFER in
> which trafter is defined. How do you deal with this? You do not allow REFER
> from MS teams and hope that MS teams will send new INVITE?
>
>
> thank you
> miha
>
> Jeff Pyle je 6/1/2021 ob 3:26 PM napisal:
>
> Miha,
>
> First, do you need to use "mtsbc.test.com:5060" in the first
> record_route_preset() param?  Can you use the IP address of your proxy
> instead?  FQDNs are legal of course, but outside of MS Teams'
> implementation, they're rarely required.  It's just another thing to go
> wrong.  Especially while testing.
>
> The ACK to the 200 OK is a sequential (in-dialog) request.  It's not part
> of the original INVITE transaction.  Your script will have a section like
>
> if (has_totag()) {
> if (loose_route()) {
> t_relay();
> }
> }
>
> for sequential requests through a loose-routing proxy.  This is very
> oversimplified and yours will have more.  In this section, however, is
> where you'll process the ACK because it has a to-tag (line 293) and a route
> header (line 298) so the conditions match.
>
> Use xlogs or the debug tool of your choice to diagnose what's happening in
> this section with the ACK.  In my scripts, I use global flag 0 to indicate
> when I want logging.  So, I might have something like this:
>
>if (has_totag()) {
>if (is_gflag(0)) xlog("L_NOTICE", " ...in-dialog $rm
> request\n");
># ...do all the things...maybe more logging like the line
> above...
>
>
> - Jeff
>
>
> On Tue, Jun 1, 2021 at 4:57 AM Miha via Users 
> wrote:
>
>> Hello
>>
>>
>> I have an issue and I am unable to find out what is wrong. Incoming calls
>> are working but when doing outbound call after 200OK, which is send to
>> Teams I get back ACK and after that Teams do again initial. I guess this is
>> not ok.
>>
>> I am doing this for outband calls:
>>
>>
>> xlog("L_INFO", "rtp rtps record route");
>> record_route_preset("mtsbc.test.com:5060","mtsbc.test.com
>> :5061;transport=tls");
>> add_rr_param(";r2=on");
>>
>> I am pasting here trace. Opensips is in the middle.
>>
>> Thank you for help!
>>
>> https://pastebin.com/qM0dMiCc
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams, reinvite after ACK

[Miha via Users]

ok, it does new seq invite, so not is is working.


thank you for help.
miha

Miha via Users je 6/2/2021 ob 10:11 AM napisal:

Hello

i manage to fix this. I did not do t_relay() also seq Invites, after 
this everything works ok.


Just on question, regarding transfers, i see that MS Teams send REFER 
in which trafter is defined. How do you deal with this? You do not 
allow REFER from MS teams and hope that MS teams will send new INVITE?



thank you
miha

Jeff Pyle je 6/1/2021 ob 3:26 PM napisal:

Miha,

First, do you need to use "mtsbc.test.com:5060 
" in the first record_route_preset() 
param?  Can you use the IP address of your proxy instead?  FQDNs are 
legal of course, but outside of MS Teams' implementation, they're 
rarely required.  It's just another thing to go wrong. Especially 
while testing.


The ACK to the 200 OK is a sequential (in-dialog) request.  It's not 
part of the original INVITE transaction. Your script will have a 
section like


if (has_totag()) {
if (loose_route()) {
t_relay();
}
}

for sequential requests through a loose-routing proxy.  This is very 
oversimplified and yours will have more.  In this section, however, 
is where you'll process the ACK because it has a to-tag (line 293) 
and a route header (line 298) so the conditions match.


Use xlogs or the debug tool of your choice to diagnose what's 
happening in this section with the ACK.  In my scripts, I use global 
flag 0 to indicate when I want logging.  So, I might have something 
like this:


   if (has_totag()) {
   if (is_gflag(0)) xlog("L_NOTICE", "...in-dialog $rm 
request\n");

# ...do all the things...maybe more logging like the line above...


- Jeff


On Tue, Jun 1, 2021 at 4:57 AM Miha via Users 
mailto:users@lists.opensips.org>> wrote:


Hello


I have an issue and I am unable to find out what is wrong.
Incoming calls are working but when doing outbound call after
200OK, which is send to Teams I get back ACK and after that Teams
do again initial. I guess this is not ok.

I am doing this for outband calls:


xlog("L_INFO", "rtp rtps record route");
record_route_preset("mtsbc.test.com:5060
","mtsbc.test.com
:5061;transport=tls");
add_rr_param(";r2=on");

I am pasting here trace. Opensips is in the middle.

Thank you for help!

https://pastebin.com/qM0dMiCc 
___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams, reinvite after ACK

[Miha via Users]

Hello

i manage to fix this. I did not do t_relay() also seq Invites, after 
this everything works ok.


Just on question, regarding transfers, i see that MS Teams send REFER in 
which trafter is defined. How do you deal with this? You do not allow 
REFER from MS teams and hope that MS teams will send new INVITE?



thank you
miha

Jeff Pyle je 6/1/2021 ob 3:26 PM napisal:

Miha,

First, do you need to use "mtsbc.test.com:5060 
" in the first record_route_preset() 
param?  Can you use the IP address of your proxy instead?  FQDNs are 
legal of course, but outside of MS Teams' implementation, they're 
rarely required. It's just another thing to go wrong.  Especially 
while testing.


The ACK to the 200 OK is a sequential (in-dialog) request. It's not 
part of the original INVITE transaction.  Your script will have a 
section like


if (has_totag()) {
if (loose_route()) {
t_relay();
}
}

for sequential requests through a loose-routing proxy.  This is very 
oversimplified and yours will have more.  In this section, however, is 
where you'll process the ACK because it has a to-tag (line 293) and a 
route header (line 298) so the conditions match.


Use xlogs or the debug tool of your choice to diagnose what's 
happening in this section with the ACK.  In my scripts, I use global 
flag 0 to indicate when I want logging.  So, I might have something 
like this:


   if (has_totag()) {
   if (is_gflag(0)) xlog("L_NOTICE", "...in-dialog $rm 
request\n");

# ...do all the things...maybe more logging like the line above...


- Jeff


On Tue, Jun 1, 2021 at 4:57 AM Miha via Users 
mailto:users@lists.opensips.org>> wrote:


Hello


I have an issue and I am unable to find out what is wrong.
Incoming calls are working but when doing outbound call after
200OK, which is send to Teams I get back ACK and after that Teams
do again initial. I guess this is not ok.

I am doing this for outband calls:


xlog("L_INFO", "rtp rtps record route");
record_route_preset("mtsbc.test.com:5060
","mtsbc.test.com
:5061;transport=tls");
add_rr_param(";r2=on");

I am pasting here trace. Opensips is in the middle.

Thank you for help!

https://pastebin.com/qM0dMiCc 
___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams, reinvite after ACK

[Jeff Pyle]

Miha,

First, do you need to use "mtsbc.test.com:5060" in the first
record_route_preset() param?  Can you use the IP address of your proxy
instead?  FQDNs are legal of course, but outside of MS Teams'
implementation, they're rarely required.  It's just another thing to go
wrong.  Especially while testing.

The ACK to the 200 OK is a sequential (in-dialog) request.  It's not part
of the original INVITE transaction.  Your script will have a section like

if (has_totag()) {
if (loose_route()) {
t_relay();
}
}

for sequential requests through a loose-routing proxy.  This is very
oversimplified and yours will have more.  In this section, however, is
where you'll process the ACK because it has a to-tag (line 293) and a route
header (line 298) so the conditions match.

Use xlogs or the debug tool of your choice to diagnose what's happening in
this section with the ACK.  In my scripts, I use global flag 0 to indicate
when I want logging.  So, I might have something like this:

   if (has_totag()) {
   if (is_gflag(0)) xlog("L_NOTICE", " ...in-dialog $rm
request\n");
   # ...do all the things...maybe more logging like the line
above...


- Jeff


On Tue, Jun 1, 2021 at 4:57 AM Miha via Users 
wrote:

> Hello
>
>
> I have an issue and I am unable to find out what is wrong. Incoming calls
> are working but when doing outbound call after 200OK, which is send to
> Teams I get back ACK and after that Teams do again initial. I guess this is
> not ok.
>
> I am doing this for outband calls:
>
>
> xlog("L_INFO", "rtp rtps record route");
> record_route_preset("mtsbc.test.com:5060","mtsbc.test.com
> :5061;transport=tls");
> add_rr_param(";r2=on");
>
> I am pasting here trace. Opensips is in the middle.
>
> Thank you for help!
>
> https://pastebin.com/qM0dMiCc
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] MS teams, reinvite after ACK

[Miha via Users]

Hello


I have an issue and I am unable to find out what is wrong. Incoming 
calls are working but when doing outbound call after 200OK, which is 
send to Teams I get back ACK and after that Teams do again initial. I 
guess this is not ok.


I am doing this for outband calls:


xlog("L_INFO", "rtp rtps record route");

record_route_preset("mtsbc.test.com:5060","mtsbc.test.com:5061;transport=tls");
add_rr_param(";r2=on");

I am pasting here trace. Opensips is in the middle.

Thank you for help!

https://pastebin.com/qM0dMiCc
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[Ben Newlin]

Yes. ☺

That piece of code is not within any route block. The local_route block is 
closed on the line before and no new route block is started.

Ben Newlin

From: Users 
Date: Thursday, September 17, 2020 at 11:35 AM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] MS teams
nope :(

here is the full content


### Routing Logic 



# main request routing logic



# Checks from MS Teams









local_route {

  $var(dst) = "pstnhub.microsoft.com<http://pstnhub.microsoft.com>";

  if (is_method("OPTIONS") && ($(ru{s.index, $var(dst)}) != NULL))

append_hf("Contact: 
http://mydomain.com:5061>;transport=tls>\r\n");



}



if (is_method("OPTIONS") && is_domain_local("$rd") && 
check_source_address("2")) {

  xlog("L_INFO",

"[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}



route{


On Thu, Sep 17, 2020 at 4:32 PM Ben Newlin 
mailto:ben.new...@genesys.com>> wrote:
Check the line *before* that snippet. You might be missing a `;` or a closing 
brace.

Ben Newlin

From: Users 
mailto:users-boun...@lists.opensips.org>>
Date: Thursday, September 17, 2020 at 11:27 AM
To: OpenSIPS users mailling list 
mailto:users@lists.opensips.org>>
Subject: Re: [OpenSIPS-Users] MS teams
The only thing I can see there is there's no newline ending in the log content. 
Don't know if that matters though.

On Thu, 2020-09-17 at 16:13 +0100, Andrew Colin wrote:
Hi Guys

i am trying to setup ms teams routing but keep getting this error on opensips 
3.1
it doesnt seem to like my config below


if(is_method("OPTIONS") && is_domain_local("$rd") && check_source_address("2")) 
{

  xlog("L_INFO", "[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}


Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl version: OpenSSL 1.1.1d  
10 Sep 2019

Sep 17 15:11:47 [4341] Traceback (last included file at the bottom):

Sep 17 15:11:47 [4341]  0. /etc/opensips/opensips.cfg

Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in 
/etc/opensips/opensips.cfg:151:1-3: syntax error

Sep 17 15:11:47 [4341]

Sep 17 15:11:47 [4341] # Checks from MS Teams

Sep 17 15:11:47 [4341] if(is_method("OPTIONS") && is_domain_local("$rd") && 
check_source_address("2")) {

Sep 17 15:11:47 [4341] ^~~

Sep 17 15:11:47 [4341]   xlog("L_INFO", "[MS TEAMS] OPTIONS In");

Sep 17 15:11:47 [4341]   send_reply("200", "OK");

Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in 
/etc/opensips/opensips.cfg:151:1-3:

Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad config file (2 errors)

Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse config file (null)

Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting

___

Users mailing list

Users@lists.opensips.org<mailto:Users@lists.opensips.org>




http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>



___
Users mailing list
Users@lists.opensips.org<mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[Fabian Gast]

Hi,

first:  it looks like your 'new'  IF - block is outside of any route. 
You close your local route before and start the main route after.. - But 
the new code block has to belong to some route block.


second:  on 3.1,
 send_reply("200", "OK");
does not work. - change this to send_reply(200, "OK");
( see 
https://opensips.org/html/docs/modules/3.1.x/signaling.html#func_send_reply 
)


same for  check_source_address("2") -this also has to be 
check_source_address(2)
( 
https://opensips.org/html/docs/modules/3.1.x/permissions#func_check_source_address)



All the best,

Fabian

On 2020-09-17 17:33, Andrew Colin wrote:

nope :(

here is the full content

### Routing Logic 

# main request routing logic

# Checks from MS Teams

local_route {

  $var(dst) = "pstnhub.microsoft.com [2]";

  if (is_method("OPTIONS") && ($(ru{s.index, $var(dst)}) != NULL))

append_hf("Contact: \r\n");

}

if (is_method("OPTIONS") && is_domain_local("$rd") &&
check_source_address("2")) {

  xlog("L_INFO",

"[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}

route{



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[Andrew Colin]

3.1



On Thu, Sep 17, 2020 at 4:53 PM Alexey Vasilyev 
wrote:

> But config is for 2.4
>
> A lot of things has changed.
> You should go through the whole config and follow first this:
> https://www.opensips.org/Documentation/Migration-2-4-0-to-3-0-0
> and then this:
> https://www.opensips.org/Documentation/Migration-3-0-0-to-3-1-0
>
>
>
> -
> ---
> Alexey Vasilyev
> --
> Sent from:
> http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[Alexey Vasilyev]

But config is for 2.4

A lot of things has changed.
You should go through the whole config and follow first this:
https://www.opensips.org/Documentation/Migration-2-4-0-to-3-0-0
and then this:
https://www.opensips.org/Documentation/Migration-3-0-0-to-3-1-0



-
---
Alexey Vasilyev
--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[Alain Bieuzent]

What version of opensips ?

 

De : Users  au nom de Andrew Colin 

Répondre à : OpenSIPS users mailling list 
Date : jeudi 17 septembre 2020 à 17:46
À : 
Cc : OpenSIPS users mailling list 
Objet : Re: [OpenSIPS-Users] MS teams

 

same thing

 

it all works fine until i add

 

if (is_method("OPTIONS") && is_domain_local("$rd") && 
check_source_address("2")) {

  xlog("L_INFO",

"[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}

 

On Thu, Sep 17, 2020 at 4:42 PM John Matich  wrote:

What about if you use braces after the if statement does it make any difference?

 

if(xx){

   append_hf(x);

}

 

On Thu, 2020-09-17 at 16:37 +0100, Andrew Colin wrote:

append_hf("Contact: \r\n");

 

On Thu, Sep 17, 2020 at 4:36 PM John Matich  wrote:

What's on line 151?

 

On Thu, 2020-09-17 at 16:33 +0100, Andrew Colin wrote:

nope :(

 

here is the full content

 

### Routing Logic 

 

# main request routing logic

 

# Checks from MS Teams

 

 

 

 

local_route {

  $var(dst) = "pstnhub.microsoft.com";

  if (is_method("OPTIONS") && ($(ru{s.index, $var(dst)}) != NULL))

append_hf("Contact: \r\n");

 

}

 

if (is_method("OPTIONS") && is_domain_local("$rd") && 
check_source_address("2")) {

  xlog("L_INFO",

"[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}

 

route{

 

 

On Thu, Sep 17, 2020 at 4:32 PM Ben Newlin  wrote:

Check the line *before* that snippet. You might be missing a `;` or a closing 
brace.

 

Ben Newlin 

 

From: Users 
Date: Thursday, September 17, 2020 at 11:27 AM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] MS teams

The only thing I can see there is there's no newline ending in the log content. 
Don't know if that matters though.

 

On Thu, 2020-09-17 at 16:13 +0100, Andrew Colin wrote:

Hi Guys

 

i am trying to setup ms teams routing but keep getting this error on opensips 
3.1

it doesnt seem to like my config below

 

if(is_method("OPTIONS") && is_domain_local("$rd") && check_source_address("2")) 
{

  xlog("L_INFO", "[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}

 

Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl version: OpenSSL 1.1.1d  
10 Sep 2019

Sep 17 15:11:47 [4341] Traceback (last included file at the bottom):

Sep 17 15:11:47 [4341]  0. /etc/opensips/opensips.cfg

Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in 
/etc/opensips/opensips.cfg:151:1-3: syntax error

Sep 17 15:11:47 [4341] 

Sep 17 15:11:47 [4341] # Checks from MS Teams

Sep 17 15:11:47 [4341] if(is_method("OPTIONS") && is_domain_local("$rd") && 
check_source_address("2")) {

Sep 17 15:11:47 [4341] ^~~

Sep 17 15:11:47 [4341]   xlog("L_INFO", "[MS TEAMS] OPTIONS In");

Sep 17 15:11:47 [4341]   send_reply("200", "OK");

Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in 
/etc/opensips/opensips.cfg:151:1-3: 

Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad config file (2 errors)

Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse config file (null)

Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting
___
Users mailing list
Users@lists.opensips.org
 

 
 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
 

 
 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___ Users mailing list 
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[Andrew Colin]

same thing

it all works fine until i add

if (is_method("OPTIONS") && is_domain_local("$rd") &&
check_source_address("2")) {

  xlog("L_INFO",

"[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}

On Thu, Sep 17, 2020 at 4:42 PM John Matich  wrote:

> What about if you use braces after the if statement does it make any
> difference?
>
> if(xx){
>append_hf(x);
> }
>
> On Thu, 2020-09-17 at 16:37 +0100, Andrew Colin wrote:
>
> append_hf("Contact: \r\n");
>
> On Thu, Sep 17, 2020 at 4:36 PM John Matich  wrote:
>
> What's on line 151?
>
> On Thu, 2020-09-17 at 16:33 +0100, Andrew Colin wrote:
>
> nope :(
>
> here is the full content
>
> ### Routing Logic 
>
>
> # main request routing logic
>
>
> # Checks from MS Teams
>
>
>
>
>
> local_route {
>
>   $var(dst) = "pstnhub.microsoft.com";
>
>   if (is_method("OPTIONS") && ($(ru{s.index, $var(dst)}) != NULL))
>
> append_hf("Contact: \r\n");
>
>
> }
>
>
> if (is_method("OPTIONS") && is_domain_local("$rd") &&
> check_source_address("2")) {
>
>   xlog("L_INFO",
>
> "[MS TEAMS] OPTIONS In");
>
>   send_reply("200", "OK");
>
>   exit;
>
> }
>
>
> route{
>
>
> On Thu, Sep 17, 2020 at 4:32 PM Ben Newlin  wrote:
>
> Check the line **before** that snippet. You might be missing a `;` or a
> closing brace.
>
>
>
> Ben Newlin
>
>
>
> *From: *Users 
> *Date: *Thursday, September 17, 2020 at 11:27 AM
> *To: *OpenSIPS users mailling list 
> *Subject: *Re: [OpenSIPS-Users] MS teams
>
> The only thing I can see there is there's no newline ending in the log
> content. Don't know if that matters though.
>
>
>
> On Thu, 2020-09-17 at 16:13 +0100, Andrew Colin wrote:
>
> Hi Guys
>
>
>
> i am trying to setup ms teams routing but keep getting this error on
> opensips 3.1
>
> it doesnt seem to like my config below
>
>
>
> if(is_method("OPTIONS") && is_domain_local("$rd") &&
> check_source_address("2")) {
>
>   xlog("L_INFO", "[MS TEAMS] OPTIONS In");
>
>   send_reply("200", "OK");
>
>   exit;
>
> }
>
>
>
> Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl version: OpenSSL
> 1.1.1d  10 Sep 2019
>
> Sep 17 15:11:47 [4341] Traceback (last included file at the bottom):
>
> Sep 17 15:11:47 [4341]  0. /etc/opensips/opensips.cfg
>
> Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> /etc/opensips/opensips.cfg:151:1-3: syntax error
>
> Sep 17 15:11:47 [4341]
>
> Sep 17 15:11:47 [4341] # Checks from MS Teams
>
> Sep 17 15:11:47 [4341] if(is_method("OPTIONS") && is_domain_local("$rd")
> && check_source_address("2")) {
>
> Sep 17 15:11:47 [4341] ^~~
>
> Sep 17 15:11:47 [4341]   xlog("L_INFO", "[MS TEAMS] OPTIONS In");
>
> Sep 17 15:11:47 [4341]   send_reply("200", "OK");
>
> Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> /etc/opensips/opensips.cfg:151:1-3:
>
> Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad config file (2
> errors)
>
> Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse config file (null)
>
> Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting
>
> ___
>
> Users mailing list
>
> 
>
> *Users@lists.opensips.org *
>
>
>
>
>
> <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>
> *http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>*
>
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[John Matich]

What about if you use braces after the if statement does it make any
difference?
if(xx){   append_hf(x);}
On Thu, 2020-09-17 at 16:37 +0100, Andrew Colin wrote:
> append_hf("Contact: \r\n");
> On Thu, Sep 17, 2020 at 4:36 PM John Matich 
> wrote:
> > What's on line 151?
> > On Thu, 2020-09-17 at 16:33 +0100, Andrew Colin wrote:
> > > nope :(
> > > here is the full content
> > > 
> > > ### Routing Logic 
> > > # main request routing logic
> > > # Checks from MS Teams
> > > 
> > > 
> > > 
> > > local_route {  $var(dst) = "pstnhub.microsoft.com";  if
> > > (is_method("OPTIONS") && ($(ru{s.index, $var(dst)}) != NULL))   
> > > append_hf("Contact: \r\n");
> > > }
> > > if (is_method("OPTIONS") && is_domain_local("$rd") &&
> > > check_source_address("2")) {  xlog("L_INFO","[MS
> > > TEAMS] OPTIONS In");  send_reply("200", "OK");  exit;}
> > > route{
> > > 
> > > On Thu, Sep 17, 2020 at 4:32 PM Ben Newlin <
> > > ben.new...@genesys.com> wrote:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Check the line *before* that snippet. You might be missing a
> > > > `;` or a closing brace.
> > > >  
> > > > Ben Newlin 
> > > >  
> > > > 
> > > > From:
> > > > Users 
> > > > 
> > > > Date: Thursday, September 17, 2020 at 11:27 AM
> > > > 
> > > > To: OpenSIPS users mailling list 
> > > > 
> > > > Subject: Re: [OpenSIPS-Users] MS teams
> > > > 
> > > > 
> > > > The only thing I can see there is there's no newline ending in
> > > > the log content. Don't know if that matters though.
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > On Thu, 2020-09-17 at 16:13 +0100, Andrew Colin wrote:
> > > > 
> > > > > 
> > > > > 
> > > > > Hi Guys
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > i am trying to setup ms teams routing but keep getting this
> > > > > error on opensips 3.1
> > > > > 
> > > > > 
> > > > > it doesnt seem to like my config below
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > 
> > > > > if(is_method("OPTIONS") && is_domain_local("$rd") &&
> > > > > check_source_address("2"))
> > > > > {
> > > > > 
> > > > >  
> > > > > xlog("L_INFO", "[MS TEAMS]
> > > > >  OPTIONS In");
> > > > > 
> > > > >  
> > > > > send_reply("200", "OK");
> > > > > 
> > > > >  
> > > > > exit;
> > > > > 
> > > > > }
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > 
> > > > > Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl
> > > > > version: OpenSSL 1.1.1d 
> > > > > 10 Sep 2019
> > > > > 
> > > > > Sep 17 15:11:47 [4341] Traceback (last included file at the
> > > > > bottom):
> > > > > 
> > > > > Sep 17 15:11:47 [4341] 
> > > > > 0. /etc/opensips/opensips.cfg
> > > > > 
> > > > > Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> > > > > /etc/opensips/opensips.cfg:151:1-3: syntax error
> > > > > 
> > > > > Sep 17 15:11:47 [4341] 
> > > > > 
> > > > > Sep 17 15:11:47 [4341] # Checks from MS Teams
> > > > > 
> > > > > Sep 17 15:11:47 [4341] if(is_method("OPTIONS") &&
> > > > > is_domain_local("$rd") && check_source_address("2")) {
> > > > > 
> > > > > Sep 17 15:11:47 [4341] ^~~
> > > > > 
> > > > > Sep 17 15:11:47 [4341]
> > > > >  
> > > > > xlog("L_INFO", "[MS TEAMS] OPTIONS In");
> > > > > 
> > > > > Sep 17 15:11:47 [4341]
> > > > >  
> > > > > send_reply("200", "OK");
> > > > > 
> > > > > Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> > > > > /etc/opensips/opensips.cfg:151:1-3: 
> > > > > 
> > > > > Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad
> > > > > config file (2 errors)
> > > > > 
> > > > > Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse
> > > > > config file (null)
> > > > > 
> > > > > Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > ___
> > > > > Users mailing list
> > > > > 
> > > > > Users@lists.opensips.org
> > > > >  
> > > > >  
> > > > > 
> > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> > > > >  
> > > > >  
> > > > 
> > > > 
> > > > 
> > > > ___
> > > > 
> > > > Users mailing list
> > > > 
> > > > Users@lists.opensips.org
> > > > 
> > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> > > > 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[Andrew Colin]

append_hf("Contact: \r\n");

On Thu, Sep 17, 2020 at 4:36 PM John Matich  wrote:

> What's on line 151?
>
> On Thu, 2020-09-17 at 16:33 +0100, Andrew Colin wrote:
>
> nope :(
>
> here is the full content
>
> ### Routing Logic 
>
>
> # main request routing logic
>
>
> # Checks from MS Teams
>
>
>
>
>
> local_route {
>
>   $var(dst) = "pstnhub.microsoft.com";
>
>   if (is_method("OPTIONS") && ($(ru{s.index, $var(dst)}) != NULL))
>
> append_hf("Contact: \r\n");
>
>
> }
>
>
> if (is_method("OPTIONS") && is_domain_local("$rd") &&
> check_source_address("2")) {
>
>   xlog("L_INFO",
>
> "[MS TEAMS] OPTIONS In");
>
>   send_reply("200", "OK");
>
>   exit;
>
> }
>
>
> route{
>
>
> On Thu, Sep 17, 2020 at 4:32 PM Ben Newlin  wrote:
>
> Check the line **before** that snippet. You might be missing a `;` or a
> closing brace.
>
>
>
> Ben Newlin
>
>
>
> *From: *Users 
> *Date: *Thursday, September 17, 2020 at 11:27 AM
> *To: *OpenSIPS users mailling list 
> *Subject: *Re: [OpenSIPS-Users] MS teams
>
> The only thing I can see there is there's no newline ending in the log
> content. Don't know if that matters though.
>
>
>
> On Thu, 2020-09-17 at 16:13 +0100, Andrew Colin wrote:
>
> Hi Guys
>
>
>
> i am trying to setup ms teams routing but keep getting this error on
> opensips 3.1
>
> it doesnt seem to like my config below
>
>
>
> if(is_method("OPTIONS") && is_domain_local("$rd") &&
> check_source_address("2")) {
>
>   xlog("L_INFO", "[MS TEAMS] OPTIONS In");
>
>   send_reply("200", "OK");
>
>   exit;
>
> }
>
>
>
> Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl version: OpenSSL
> 1.1.1d  10 Sep 2019
>
> Sep 17 15:11:47 [4341] Traceback (last included file at the bottom):
>
> Sep 17 15:11:47 [4341]  0. /etc/opensips/opensips.cfg
>
> Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> /etc/opensips/opensips.cfg:151:1-3: syntax error
>
> Sep 17 15:11:47 [4341]
>
> Sep 17 15:11:47 [4341] # Checks from MS Teams
>
> Sep 17 15:11:47 [4341] if(is_method("OPTIONS") && is_domain_local("$rd")
> && check_source_address("2")) {
>
> Sep 17 15:11:47 [4341] ^~~
>
> Sep 17 15:11:47 [4341]   xlog("L_INFO", "[MS TEAMS] OPTIONS In");
>
> Sep 17 15:11:47 [4341]   send_reply("200", "OK");
>
> Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> /etc/opensips/opensips.cfg:151:1-3:
>
> Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad config file (2
> errors)
>
> Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse config file (null)
>
> Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting
>
> ___
>
> Users mailing list
>
> 
>
> *Users@lists.opensips.org *
>
>
>
>
>
> <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>
> *http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>*
>
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[John Matich]

What's on line 151?

On Thu, 2020-09-17 at 16:33 +0100, Andrew Colin wrote:
> nope :(
> here is the full content
> 
> ### Routing Logic 
> # main request routing logic
> # Checks from MS Teams
> 
> 
> 
> local_route {  $var(dst) = "pstnhub.microsoft.com";  if
> (is_method("OPTIONS") && ($(ru{s.index, $var(dst)}) != NULL))   
> append_hf("Contact: \r\n");
> }
> if (is_method("OPTIONS") && is_domain_local("$rd") &&
> check_source_address("2")) {  xlog("L_INFO","[MS
> TEAMS] OPTIONS In");  send_reply("200", "OK");  exit;}
> route{
> 
> On Thu, Sep 17, 2020 at 4:32 PM Ben Newlin 
> wrote:
> > 
> > 
> > 
> > 
> > 
> > 
> > Check the line *before* that snippet. You might be missing a `;` or
> > a closing brace.
> >  
> > Ben Newlin 
> >  
> > 
> > From:
> > Users 
> > 
> > Date: Thursday, September 17, 2020 at 11:27 AM
> > 
> > To: OpenSIPS users mailling list 
> > 
> > Subject: Re: [OpenSIPS-Users] MS teams
> > 
> > 
> > The only thing I can see there is there's no newline ending in the
> > log content. Don't know if that matters though.
> > 
> > 
> >  
> > 
> > 
> > On Thu, 2020-09-17 at 16:13 +0100, Andrew Colin wrote:
> > 
> > > 
> > > 
> > > Hi Guys
> > > 
> > >  
> > > 
> > > 
> > > i am trying to setup ms teams routing but keep getting this error
> > > on opensips 3.1
> > > 
> > > 
> > > it doesnt seem to like my config below
> > > 
> > > 
> > >  
> > > 
> > > 
> > > 
> > > if(is_method("OPTIONS") && is_domain_local("$rd") &&
> > > check_source_address("2"))
> > > {
> > > 
> > >  
> > > xlog("L_INFO", "[MS TEAMS]
> > >  OPTIONS In");
> > > 
> > >  
> > > send_reply("200", "OK");
> > > 
> > >  
> > > exit;
> > > 
> > > }
> > > 
> > > 
> > >  
> > > 
> > > 
> > > 
> > > Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl version:
> > > OpenSSL 1.1.1d 
> > > 10 Sep 2019
> > > 
> > > Sep 17 15:11:47 [4341] Traceback (last included file at the
> > > bottom):
> > > 
> > > Sep 17 15:11:47 [4341] 
> > > 0. /etc/opensips/opensips.cfg
> > > 
> > > Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> > > /etc/opensips/opensips.cfg:151:1-3: syntax error
> > > 
> > > Sep 17 15:11:47 [4341] 
> > > 
> > > Sep 17 15:11:47 [4341] # Checks from MS Teams
> > > 
> > > Sep 17 15:11:47 [4341] if(is_method("OPTIONS") &&
> > > is_domain_local("$rd") && check_source_address("2")) {
> > > 
> > > Sep 17 15:11:47 [4341] ^~~
> > > 
> > > Sep 17 15:11:47 [4341]
> > >  
> > > xlog("L_INFO", "[MS TEAMS] OPTIONS In");
> > > 
> > > Sep 17 15:11:47 [4341]
> > >  
> > > send_reply("200", "OK");
> > > 
> > > Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> > > /etc/opensips/opensips.cfg:151:1-3: 
> > > 
> > > Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad config
> > > file (2 errors)
> > > 
> > > Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse config
> > > file (null)
> > > 
> > > Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting
> > > 
> > > 
> > > 
> > > 
> > > ___
> > > Users mailing list
> > > 
> > > Users@lists.opensips.org
> > >  
> > >  
> > > 
> > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> > >  
> > >  
> > 
> > 
> > 
> > ___
> > 
> > Users mailing list
> > 
> > Users@lists.opensips.org
> > 
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> > 
> 
> 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[Andrew Colin]

nope :(

here is the full content

### Routing Logic 


# main request routing logic


# Checks from MS Teams





local_route {

  $var(dst) = "pstnhub.microsoft.com";

  if (is_method("OPTIONS") && ($(ru{s.index, $var(dst)}) != NULL))

append_hf("Contact: \r\n");


}


if (is_method("OPTIONS") && is_domain_local("$rd") &&
check_source_address("2")) {

  xlog("L_INFO",

"[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}


route{


On Thu, Sep 17, 2020 at 4:32 PM Ben Newlin  wrote:

> Check the line **before** that snippet. You might be missing a `;` or a
> closing brace.
>
>
>
> Ben Newlin
>
>
>
> *From: *Users 
> *Date: *Thursday, September 17, 2020 at 11:27 AM
> *To: *OpenSIPS users mailling list 
> *Subject: *Re: [OpenSIPS-Users] MS teams
>
> The only thing I can see there is there's no newline ending in the log
> content. Don't know if that matters though.
>
>
>
> On Thu, 2020-09-17 at 16:13 +0100, Andrew Colin wrote:
>
> Hi Guys
>
>
>
> i am trying to setup ms teams routing but keep getting this error on
> opensips 3.1
>
> it doesnt seem to like my config below
>
>
>
> if(is_method("OPTIONS") && is_domain_local("$rd") &&
> check_source_address("2")) {
>
>   xlog("L_INFO", "[MS TEAMS] OPTIONS In");
>
>   send_reply("200", "OK");
>
>   exit;
>
> }
>
>
>
> Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl version: OpenSSL
> 1.1.1d  10 Sep 2019
>
> Sep 17 15:11:47 [4341] Traceback (last included file at the bottom):
>
> Sep 17 15:11:47 [4341]  0. /etc/opensips/opensips.cfg
>
> Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> /etc/opensips/opensips.cfg:151:1-3: syntax error
>
> Sep 17 15:11:47 [4341]
>
> Sep 17 15:11:47 [4341] # Checks from MS Teams
>
> Sep 17 15:11:47 [4341] if(is_method("OPTIONS") && is_domain_local("$rd")
> && check_source_address("2")) {
>
> Sep 17 15:11:47 [4341] ^~~
>
> Sep 17 15:11:47 [4341]   xlog("L_INFO", "[MS TEAMS] OPTIONS In");
>
> Sep 17 15:11:47 [4341]   send_reply("200", "OK");
>
> Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> /etc/opensips/opensips.cfg:151:1-3:
>
> Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad config file (2
> errors)
>
> Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse config file (null)
>
> Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting
>
> ___
>
> Users mailing list
>
> 
>
> *Users@lists.opensips.org *
>
>
>
>
>
> <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>
> *http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
> <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>*
>
>
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[Ben Newlin]

Check the line *before* that snippet. You might be missing a `;` or a closing 
brace.

Ben Newlin

From: Users 
Date: Thursday, September 17, 2020 at 11:27 AM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] MS teams
The only thing I can see there is there's no newline ending in the log content. 
Don't know if that matters though.

On Thu, 2020-09-17 at 16:13 +0100, Andrew Colin wrote:
Hi Guys

i am trying to setup ms teams routing but keep getting this error on opensips 
3.1
it doesnt seem to like my config below


if(is_method("OPTIONS") && is_domain_local("$rd") && check_source_address("2")) 
{

  xlog("L_INFO", "[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}


Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl version: OpenSSL 1.1.1d  
10 Sep 2019

Sep 17 15:11:47 [4341] Traceback (last included file at the bottom):

Sep 17 15:11:47 [4341]  0. /etc/opensips/opensips.cfg

Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in 
/etc/opensips/opensips.cfg:151:1-3: syntax error

Sep 17 15:11:47 [4341]

Sep 17 15:11:47 [4341] # Checks from MS Teams

Sep 17 15:11:47 [4341] if(is_method("OPTIONS") && is_domain_local("$rd") && 
check_source_address("2")) {

Sep 17 15:11:47 [4341] ^~~

Sep 17 15:11:47 [4341]   xlog("L_INFO", "[MS TEAMS] OPTIONS In");

Sep 17 15:11:47 [4341]   send_reply("200", "OK");

Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in 
/etc/opensips/opensips.cfg:151:1-3:

Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad config file (2 errors)

Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse config file (null)

Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting

___

Users mailing list
<mailto:Users@lists.opensips.org>

Users@lists.opensips.org<mailto:Users@lists.opensips.org>



<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS teams

[John Matich]

The only thing I can see there is there's no newline ending in the log
content. Don't know if that matters though.
On Thu, 2020-09-17 at 16:13 +0100, Andrew Colin wrote:
> Hi Guys
> i am trying to setup ms teams routing but keep getting this error on
> opensips 3.1
> it doesnt seem to like my config below
> 
> if(is_method("OPTIONS") && is_domain_local("$rd") &&
> check_source_address("2")) {
>   xlog("L_INFO", "[MS TEAMS] OPTIONS In");
>   send_reply("200", "OK");
>   exit;
> }
> 
> Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl version:
> OpenSSL 1.1.1d  10 Sep 2019
> Sep 17 15:11:47 [4341] Traceback (last included file at the bottom):
> Sep 17 15:11:47 [4341]  0. /etc/opensips/opensips.cfg
> Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> /etc/opensips/opensips.cfg:151:1-3: syntax error
> Sep 17 15:11:47 [4341] 
> Sep 17 15:11:47 [4341] # Checks from MS Teams
> Sep 17 15:11:47 [4341] if(is_method("OPTIONS") &&
> is_domain_local("$rd") && check_source_address("2")) {
> Sep 17 15:11:47 [4341] ^~~
> Sep 17 15:11:47 [4341]   xlog("L_INFO", "[MS TEAMS] OPTIONS In");
> Sep 17 15:11:47 [4341]   send_reply("200", "OK");
> Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
> /etc/opensips/opensips.cfg:151:1-3: 
> Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad config file
> (2 errors)
> Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse config file
> (null)
> Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting
> 
> ___Users mailing 
> listus...@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] MS teams

[Andrew Colin]

Hi Guys

i am trying to setup ms teams routing but keep getting this error on
opensips 3.1
it doesnt seem to like my config below

if(is_method("OPTIONS") && is_domain_local("$rd") &&
check_source_address("2")) {

  xlog("L_INFO", "[MS TEAMS] OPTIONS In");

  send_reply("200", "OK");

  exit;

}

Sep 17 15:11:47 [4341] INFO:tls_mgm:mod_load: openssl version: OpenSSL
1.1.1d  10 Sep 2019

Sep 17 15:11:47 [4341] Traceback (last included file at the bottom):

Sep 17 15:11:47 [4341]  0. /etc/opensips/opensips.cfg

Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
/etc/opensips/opensips.cfg:151:1-3: syntax error

Sep 17 15:11:47 [4341]

Sep 17 15:11:47 [4341] # Checks from MS Teams

Sep 17 15:11:47 [4341] if(is_method("OPTIONS") && is_domain_local("$rd") &&
check_source_address("2")) {

Sep 17 15:11:47 [4341] ^~~

Sep 17 15:11:47 [4341]   xlog("L_INFO", "[MS TEAMS] OPTIONS In");

Sep 17 15:11:47 [4341]   send_reply("200", "OK");

Sep 17 15:11:47 [4341] CRITICAL:core:yyerror: parse error in
/etc/opensips/opensips.cfg:151:1-3:

Sep 17 15:11:47 [4341] ERROR:core:parse_opensips_cfg: bad config file (2
errors)

Sep 17 15:11:47 [4341] ERROR:core:main: failed to parse config file (null)

Sep 17 15:11:47 [4341] NOTICE:core:main: Exiting
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams outgoing calls fails

[Pasan Meemaduma via Users]

Hi Alexey,
Thanks for the prompt reply. your are a legend as always :). Sorry for not 
digging into old emails. The searches I did, didn't come with above posts.
Thank you again.
Regards,Pasan

   Distinguishing What && How ! 

On Friday, 17 July 2020, 11:27:16 am GMT+5:30, Alexey Vasilyev 
 wrote:  
 
 Hi Pasan,

This was explained here:
http://opensips-open-sip-server.1449251.n2.nabble.com/TLS-handshake-failure-td7619394.html




-
---
Alexey Vasilyev
--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
  ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams outgoing calls fails

[Alexey Vasilyev]

Hi Pasan,

This was explained here:
http://opensips-open-sip-server.1449251.n2.nabble.com/TLS-handshake-failure-td7619394.html




-
---
Alexey Vasilyev
--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] ms teams outgoing calls fails

[Pasan Meemaduma via Users]

Hi Guys,
Set up
msteams client  <--> msteams sbc <--> opensips <--> asterisk  <--> pstn


I recently ran in to an issue with handling outgoing calls to msteams, call 
fails as msteams unable to send ACK after 200 OK reply. below is the debug log 
I got from opensips as per logs it seems like opensips unable to accept the 
connection back from msteams sbc to read ACK.

Jul 16 13:55:38 msteams-sbc opensips[28748]: Jul 16 13:55:38 [28764] 
ERROR:proto_tls:tls_accept: New TLS connection from 52.114.14.70:5248 failed to 
accept
Jul 16 13:55:38 msteams-sbc opensips[28748]: Jul 16 13:55:38 [28764] 
ERROR:proto_tls:tls_read_req: failed to do pre-tls reading

There's no other error other than above. Any clue as to what could be wrong ?
incoming calls toward teams works fine.
Thanks
Regards,Pasan



Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:tm:insert_timer_unsafe: [2]: 0x7f6b6be7b0b0 (55)
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:core:tcp_conn_get: con found in state 0
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:core:tcp_conn_get: tcp connection found (0x7f6b6be79a28), acquiring fd
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:core:tcp_conn_get: c= 0x7f6b6be79a28, n=16, Usock=56
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28766] 
DBG:core:handle_worker: read response= 7f6b6be79a28, 1, fd -1 from 12 (28763)
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:core:tcp_conn_get: after receive_fd: c= 0x7f6b6be79a28 n=8 fd=63
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:proto_tls:proto_tls_send: sending via fd 63...
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:proto_tls:tls_update_fd: New fd is 63
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:proto_tls:tls_write: write was successful (1113 bytes)
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:proto_tls:proto_tls_send: after write: c= 0x7f6b6be79a28 n=1113 fd=63
Jul 16 13:55:37 msteams-sbc opensips[28748]: Jul 16 13:55:37 [28763] 
DBG:proto_tls:proto_tls_send: buf=
Jul 16 13:55:37 msteams-sbc opensips[28748]: SIP/2.0 200 OK
Jul 16 13:55:37 msteams-sbc opensips[28748]: Via: SIP/2.0/TLS 
52.114.14.70:5061;rport=5888;received=52.114.14.70;branch=z9hG4bK642d4611
Jul 16 13:55:37 msteams-sbc opensips[28748]: Record-Route: 

Jul 16 13:55:37 msteams-sbc opensips[28748]: Record-Route: 

Jul 16 13:55:37 msteams-sbc opensips[28748]: From: Pasan 
Meemaduma;tag=87bcce1e760c4752b396766bedd72f73
Jul 16 13:55:37 msteams-sbc opensips[28748]: To: 
;tag=as3b49d4e8
Jul 16 13:55:37 msteams-sbc opensips[28748]: Call-ID: 
8696a372ea105ccf99693a5189831870
Jul 16 13:55:37 msteams-sbc opensips[28748]: CSeq: 1 INVITE
Jul 16 13:55:37 msteams-sbc opensips[28748]: Server: Asterisk PBX 13.32.0
Jul 16 13:55:37 msteams-sbc opensips[28748]: Allow: INVITE, ACK, CANCEL, 
OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Jul 16 13:55:37 msteams-sbc opensips[28748]: Supported: replaces
Jul 16 13:55:37 msteams-sbc opensips[28748]: Contact: 

Jul 16 13:55:37 msteams-sbc opensips[28748]: Content-Type: application/sdp
Jul 16 13:55:37 msteams-sbc opensips[28748]: Content-Length: 327
Jul 16 13:55:37 msteams-sbc opensips[28748]: #015
Jul 16 13:55:37 msteams-sbc opensips[28748]: v=0
Jul 16 13:55:37 msteams-sbc opensips[28748]: o=root 1092739735 1092739735 IN 
IP4 175.103.19.67
Jul 16 13:55:37 msteams-sbc opensips[28748]: s=Asterisk PBX 13.32.0
Jul 16 13:55:37 msteams-sbc opensips[28748]: c=IN IP4 175.103.19.67
Jul 16 13:55:37 msteams-sbc opensips[28748]: t=0 0
Jul 16 13:55:37 msteams-sbc opensips[28748]: m=audio 17398 RTP/SAVP 8 101
Jul 16 13:55:37 msteams-sbc opensips[28748]: a=crypto:1 AES_CM_128_HMAC_SHA1_80 
inline:qiRc8pQTLEPOxR+Yov731H1YTSgkrDvolTefqIVo
Jul 16 13:55:37 msteams-sbc opensips[28748]: a=rtpmap:8 PCMA/8000
Jul 16 13:55:37 msteams-sbc opensips[28748]: a=rtpmap:101 telephone-event/8000
Jul 16 13:55:37 msteams-sbc opensips[28748]: a=fmtp:101 0-16
Jul 16 13:55:37 msteams-sbc opensips[28748]: a=maxptime:150
Jul 16 13:55:37 msteams-sbc opensips[28748]: a=sendrecv

Jul 16 13:55:38 msteams-sbc opensips[28748]: Jul 16 13:55:38 [28764] 
DBG:proto_tls:tls_update_fd: New fd is 64
Jul 16 13:55:38 msteams-sbc opensips[28748]: Jul 16 13:55:38 [28764] 
DBG:proto_tls:tls_update_fd: New fd is 64
Jul 16 13:55:38 msteams-sbc opensips[28748]: Jul 16 13:55:38 [28764] 
DBG:proto_tls:tcp_handle_req: We didn't manage to read a full request
Jul 16 13:55:38 msteams-sbc opensips[28748]: Jul 16 13:55:38 [28764] 
DBG:proto_tls:tls_read_req: tls_read_req end
Jul 16 13:55:38 msteams-sbc opensips[28748]: Jul 16 13:55:38 [28764] 
DBG:proto_tls:tls_read_req: Using the per connection buff
Jul 16 13:55:38 msteams-sbc opensips[28748]: Jul 16 13:55:38 [28764] 
DBG:proto_tls:tls_update_fd: New fd is 64
Jul 16 13:55:38 msteams-sbc opensips[28748]: Jul 16 1

Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.

[Johan De Clercq]

Can you send a trace (pcap)?

Outlook voor iOS<https://aka.ms/o0ukef> downloaden

Van: Users  namens Yuriy Nasida 

Verzonden: Monday, May 11, 2020 8:50:44 AM
Aan: OpenSIPS users mailling list 
Onderwerp: Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.

Guys,

Hold/Unhold, blind transfers is fine without REFER support
But... Please note that attended  (consult) transfer will not work.
I did many tests and MS does 3th call to connect  Transferee and Transfer 
Target. Not sure why. I tried same things from regular softphone - and it works 
great without 3th call.



On Sat, 9 May 2020 at 00:02, Slava Bendersky via Users 
mailto:users@lists.opensips.org>> wrote:
Hello Johan,
Thank you for reply and help.
Based on MS Teams   Allow header will disable REFER and MS Teams will send 
invite in dialog.
The following code  snippet on 200 OK reply  is resolve the issue.

$var(refer-allow) = "INVITE, ACK, CANCEL, BYE, INFO, 
NOTIFY, PRACK, UPDATE, OPTIONS";
remove_hf("Allow");
insert_hf("Allow: $var(refer-allow)\r\n");



volga629

From: "johan" mailto:jo...@democon.be>>
To: "OpenSIPS users mailling list" 
mailto:users@lists.opensips.org>>
Sent: Friday, May 8, 2020 9:58:56 AM
Subject: Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.


try with replying that you don't support refer.

On 8/05/2020 11:19, Slava Bendersky via Users wrote:
Hello Everyone,
I am trying put tougher transfer feature with in MS Teams.
And based on my research and testing right now is not possible with opensips.
MS Teams are sending on hold  in case of transfer and onhold as a=inactive.
Major problem they require encode/decode params in REFER-TO REFER-BY.

MS Teams expect observe REFER with 202 and decode params  with future action.

Here official requirements doc.

https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip#call-transfer

Any suggestion welcome.

volga629.





___
Users mailing list
Users@lists.opensips.org<mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org<mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org<mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.

[Johan De Clercq]

Refer-to must be populated with c number else it can never work.

Outlook voor iOS<https://aka.ms/o0ukef> downloaden

Van: Slava Bendersky 
Verzonden: Friday, May 8, 2020 10:59:31 PM
Aan: OpenSIPS users mailling list 
CC: johan 
Onderwerp: Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.

Hello Johan,
Thank you for reply and help.
Based on MS Teams   Allow header will disable REFER and MS Teams will send 
invite in dialog.
The following code  snippet on 200 OK reply  is resolve the issue.

$var(refer-allow) = "INVITE, ACK, CANCEL, BYE, INFO, 
NOTIFY, PRACK, UPDATE, OPTIONS";
remove_hf("Allow");
insert_hf("Allow: $var(refer-allow)\r\n");



volga629

From: "johan" 
To: "OpenSIPS users mailling list" 
Sent: Friday, May 8, 2020 9:58:56 AM
Subject: Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.


try with replying that you don't support refer.

On 8/05/2020 11:19, Slava Bendersky via Users wrote:
Hello Everyone,
I am trying put tougher transfer feature with in MS Teams.
And based on my research and testing right now is not possible with opensips.
MS Teams are sending on hold  in case of transfer and onhold as a=inactive.
Major problem they require encode/decode params in REFER-TO REFER-BY.

MS Teams expect observe REFER with 202 and decode params  with future action.

Here official requirements doc.

https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip#call-transfer

Any suggestion welcome.

volga629.





___
Users mailing list
Users@lists.opensips.org<mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.

[Yuriy Nasida]

Guys,

Hold/Unhold, blind transfers is fine without REFER support
But... Please note that attended  (consult) transfer will not work.
I did many tests and MS does 3th call to connect  Transferee and Transfer
Target. Not sure why. I tried same things from regular softphone - and
it works great without 3th call.



On Sat, 9 May 2020 at 00:02, Slava Bendersky via Users <
users@lists.opensips.org> wrote:

> Hello Johan,
> Thank you for reply and help.
> Based on MS Teams   Allow header will disable REFER and MS Teams will send
> invite in dialog.
> The following code  snippet on 200 OK reply  is resolve the issue.
>
> $var(refer-allow) = "INVITE, ACK, CANCEL, BYE,
> INFO, NOTIFY, PRACK, UPDATE, OPTIONS";
> remove_hf("Allow");
> insert_hf("Allow: $var(refer-allow)\r\n");
>
>
>
> volga629
> --
> *From: *"johan" 
> *To: *"OpenSIPS users mailling list" 
> *Sent: *Friday, May 8, 2020 9:58:56 AM
> *Subject: *Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.
>
> try with replying that you don't support refer.
> On 8/05/2020 11:19, Slava Bendersky via Users wrote:
>
> Hello Everyone,
> I am trying put tougher transfer feature with in MS Teams.
> And based on my research and testing right now is not possible with
> opensips.
> MS Teams are sending on hold  in case of transfer and onhold as a=inactive.
> Major problem they require encode/decode params in REFER-TO REFER-BY.
>
> MS Teams expect observe REFER with 202 and decode params  with future
> action.
>
> Here official requirements doc.
>
>
> https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip#call-transfer
>
> Any suggestion welcome.
>
> volga629.
>
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.

[Slava Bendersky via Users]

Hello Johan, 
Thank you for reply and help. 
Based on MS Teams Allow header will disable REFER and MS Teams will send invite 
in dialog. 
The following code snippet on 200 OK reply is resolve the issue. 

$var(refer-allow) = "INVITE, ACK, CANCEL, BYE, INFO, NOTIFY, PRACK, UPDATE, 
OPTIONS"; 
remove_hf("Allow"); 
insert_hf("Allow: $var(refer-allow)\r\n"); 


volga629 

From: "johan"  
To: "OpenSIPS users mailling list"  
Sent: Friday, May 8, 2020 9:58:56 AM 
Subject: Re: [OpenSIPS-Users] MS Teams REFER transfer on hold. 



try with replying that you don't support refer. 
On 8/05/2020 11:19, Slava Bendersky via Users wrote: 





Hello Everyone, 
I am trying put tougher transfer feature with in MS Teams. 
And based on my research and testing right now is not possible with opensips. 
MS Teams are sending on hold in case of transfer and onhold as a=inactive. 
Major problem they require encode/decode params in REFER-TO REFER-BY. 

MS Teams expect observe REFER with 202 and decode params with future action. 

Here official requirements doc. 
[ 
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip#call-transfer
 | 
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip#call-transfer
 ] 

Any suggestion welcome. 

volga629. 



___
Users mailing list [ mailto:Users@lists.opensips.org | Users@lists.opensips.org 
] [ http://lists.opensips.org/cgi-bin/mailman/listinfo/users | 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users ] 

___ 
Users mailing list 
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] MS Teams REFER transfer on hold.

[johan]

try with replying that you don't support refer.

On 8/05/2020 11:19, Slava Bendersky via Users wrote:

Hello Everyone,
I am trying put tougher transfer feature with in MS Teams.
And based on my research and testing right now is not possible with 
opensips.
MS Teams are sending on hold  in case of transfer and onhold as 
a=inactive.

Major problem they require encode/decode params in REFER-TO REFER-BY.

MS Teams expect observe REFER with 202 and decode params  with future 
action.


Here official requirements doc.
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip#call-transfer

Any suggestion welcome.

volga629.



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] MS Teams REFER transfer on hold.

[Slava Bendersky via Users]

Hello Everyone, 
I am trying put tougher transfer feature with in MS Teams. 
And based on my research and testing right now is not possible with opensips. 
MS Teams are sending on hold in case of transfer and onhold as a=inactive. 
Major problem they require encode/decode params in REFER-TO REFER-BY. 

MS Teams expect observe REFER with 202 and decode params with future action. 

Here official requirements doc. 
[ 
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip#call-transfer
 | 
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip#call-transfer
 ] 

Any suggestion welcome. 

volga629. 


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] MS Teams REFER transfer on hold.

[Slava Bendersky via Users]

Hello Everyone, 
I am trying put tougher transfer feature with MS Teams. 
And based right now not possible with opensips. 
MS Teams are sending on hold in case of transfer and onhold. 
Major problem they require encode/decode params in REFER-TO REFER-BY. 

Here official requirements doc. 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Santi Anton]

Hi James,

Check where you are calling the do_routing function (if you are using
dynamic routing module) and be sure that only INVITEs are routed by this
function.
My mistake was that ACK (and lately I noticed that BYEs too) was being
routed by do_routing changing the Request URI.





--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[James Hogbin]

Precisely my issue.

Do you have an example opensips.conf you are could share?

James

James Hogbin
Director 
 
IP Sentinel 
t. +44 (0)20 3011 4150
m. +44 7786910895
w. https://www.ip-sentinel.com

> On 29 Apr 2020, at 15:49, Santi Anton  wrote:
> 
> Hi Ben,
> 
> I found the mistake. As you said, the ACK Request URI was different from 200
> OK contact header, checking my script I noticed that ACK was being routed by
> dynamic routing module changing its Request URI.
> 
> Thanks for the hint.
> 
> 
> 
> --
> Sent from: 
> http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

IP Sentinel Disclaimer 
This communication is for the information of the person to whom it has been 
delivered and neither it nor any of its contents should be passed on to or used 
by any other person. IP Sentinel Ltd is a limited company registered in England 
and Wales under Registered Number 08648097. Registered Office: Newnhams Wood, 
Horsted Keynes, West Sussex, RH17 7BT. 
Disclaimer: Q3dhRSrm_disclaimer
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Santi Anton]

Hi Ben,

I found the mistake. As you said, the ACK Request URI was different from 200
OK contact header, checking my script I noticed that ACK was being routed by
dynamic routing module changing its Request URI.

Thanks for the hint.



--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Santi Anton]

Hi Kevin,

Thanks, in that case it has been a copy/paste error. I checked it again and
all Call-IDs are exactly the same.




--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[volga629 via Users]

Try check you preset route.


volga629


On 4/29/20 10:59 AM, Santi Anton wrote:

Hello Ben,

I agree. These are the INVITE and 200 OK. I only could see that to and from
tag an Call-ID are the same. I think that in the article there is nothing
about modifying ACK headers to make it work.


INVITE sip:5...@sip.pstnhub.microsoft.com SIP/2.0
Record-Route:

Record-Route: 
Via: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.0
Via: SIP/2.0/UDP
80.xx.xx.xx.xx:5060;received=80.xx.xx.xx.xx;branch=z9hG4bK4df6ca5c;rport=5060
Max-Forwards: 69
From: ;tag=as7659f57d
To: 
Contact: 
Call-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx.xx:5060
CSeq: 102 INVITE
User-Agent: FPBX-12.0.76.6(11.20.0)
Date: Mon, 27 Apr 2020 16:25:24 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO,
PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 1470


SIP/2.0 200 OK
FROM: ;tag=as7659f57d
TO: ;tag=50fe42a7fdb64fe583c1089a0b47f44a
CSEQ: 102 INVITE
CALL-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx.xx:5060
VIA: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.0,SIP/2.0/UDP
80.xx.xx.xx.xx:5060;received=80.xx.xx.xx.xx;branch=z9hG4bK4df6ca5c;rport=5060
RECORD-ROUTE:
,,
CONTACT:

CONTENT-LENGTH: 827
SUPPORTED: timer
CONTENT-TYPE: application/sdp
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
SESSION-EXPIRES: 3600;refresher=uas
SERVER: Microsoft.PSTNHub.SIPProxy v.2020.4.20.2 i.EUWE.6

Best Regards,



--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Ben Newlin]

I have not read the MS Teams article, but from a SIP perspective your ACK is 
malformed. The Request URI in the ACK - and any other sequential requests - 
must be the Contact URI from the 200 OK response. Your ACK Request URI has the 
parameters from the Contact header, but the domain/host is different. I'm 
guessing your script may be modifying that value as it passes the ACK through?

Also, your ACK does not contain the complete Route set from the 200 OK, it only 
contains the first entry.

Ben Newlin 

On 4/29/20, 10:00 AM, "Users on behalf of Santi Anton" 
 wrote:

Hello Ben,

I agree. These are the INVITE and 200 OK. I only could see that to and from
tag an Call-ID are the same. I think that in the article there is nothing
about modifying ACK headers to make it work.


INVITE sip:5...@sip.pstnhub.microsoft.com SIP/2.0
Record-Route:

Record-Route: 
Via: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.0
Via: SIP/2.0/UDP

80.xx.xx.xx.xx:5060;received=80.xx.xx.xx.xx;branch=z9hG4bK4df6ca5c;rport=5060
Max-Forwards: 69
From: ;tag=as7659f57d
To: 
Contact: 
Call-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx.xx:5060
CSeq: 102 INVITE
User-Agent: FPBX-12.0.76.6(11.20.0)
Date: Mon, 27 Apr 2020 16:25:24 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO,
PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 1470


SIP/2.0 200 OK
FROM: ;tag=as7659f57d
TO: ;tag=50fe42a7fdb64fe583c1089a0b47f44a
CSEQ: 102 INVITE
CALL-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx.xx:5060
VIA: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.0,SIP/2.0/UDP

80.xx.xx.xx.xx:5060;received=80.xx.xx.xx.xx;branch=z9hG4bK4df6ca5c;rport=5060
RECORD-ROUTE:

,,
CONTACT:


CONTENT-LENGTH: 827
SUPPORTED: timer
CONTENT-TYPE: application/sdp
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
SESSION-EXPIRES: 3600;refresher=uas
SERVER: Microsoft.PSTNHub.SIPProxy v.2020.4.20.2 i.EUWE.6

Best Regards,



--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Santi Anton]

Hello Ben,

I agree. These are the INVITE and 200 OK. I only could see that to and from
tag an Call-ID are the same. I think that in the article there is nothing
about modifying ACK headers to make it work.


INVITE sip:5...@sip.pstnhub.microsoft.com SIP/2.0
Record-Route:

Record-Route: 
Via: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.0
Via: SIP/2.0/UDP
80.xx.xx.xx.xx:5060;received=80.xx.xx.xx.xx;branch=z9hG4bK4df6ca5c;rport=5060
Max-Forwards: 69
From: ;tag=as7659f57d
To: 
Contact: 
Call-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx.xx:5060
CSeq: 102 INVITE
User-Agent: FPBX-12.0.76.6(11.20.0)
Date: Mon, 27 Apr 2020 16:25:24 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO,
PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 1470


SIP/2.0 200 OK
FROM: ;tag=as7659f57d
TO: ;tag=50fe42a7fdb64fe583c1089a0b47f44a
CSEQ: 102 INVITE
CALL-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx.xx:5060
VIA: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.0,SIP/2.0/UDP
80.xx.xx.xx.xx:5060;received=80.xx.xx.xx.xx;branch=z9hG4bK4df6ca5c;rport=5060
RECORD-ROUTE:
,,
CONTACT:

CONTENT-LENGTH: 827
SUPPORTED: timer
CONTENT-TYPE: application/sdp
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
SESSION-EXPIRES: 3600;refresher=uas
SERVER: Microsoft.PSTNHub.SIPProxy v.2020.4.20.2 i.EUWE.6

Best Regards,



--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Kevin Vines]

The call IDs don't match. Your ACK has an extra :5060 appended.

Just a thought...




Kevin V.
+15195726354



  Original Message  


From: santi.an...@quarea.com
Sent: April 29, 2020 4:13 a.m.
To: users@lists.opensips.org
Reply to: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] ms teams ACK


Hello,

If it helps, these are the ACK sent to MSTeams and BYE received after 20
seconds.

sbc..com:5067 Opensips TLS interface
195.xx.xx.xx:5068 Opensips UDP interface
80.xx.xx.xx:5060 Asterisk


ACK
sip:sip.pstnhub.microsoft.com;x-i=0c135a71-ddec-454c-a506-91079cb038d7;x-c=385a4453fc885c0bb6276a40d7796d3a/s/1/e1c45d052842415e9c0b3b0b04e32791
SIP/2.0
Via: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.2
Via: SIP/2.0/UDP
80.xx.xx.xx:5060;received=80.xx.xx.xx;branch=z9hG4bK0a1d079a;rport=5060
Route: 
Max-Forwards: 69
From: ;tag=as7659f57d
To: ;tag=50fe42a7fdb64fe583c1089a0b47f44a
Contact: 
Call-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx:5060:5060
CSeq: 102 ACK
User-Agent: FPBX-12.0.76.6(11.20.0)
Content-Length: 0


BYE sip:935441...@80.xx.xx.xx:5060 SIP/2.0
FROM:
;tag=50fe42a7fdb64fe583c1089a0b47f44a
TO: ;tag=as7659f57d
CSEQ: 3 BYE
CALL-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx:5060
MAX-FORWARDS: 69
VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bKf36698cf
REASON: Q.850;cause=18;text="0c135a71-ddec-454c-a506-91079cb038d7;*Call
Controller timed out while waiting for acknowledgement.*"
ROUTE:
,
CONTACT:

CONTENT-LENGTH: 0
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.20.2 i.EUWE.6
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY

Best Regards,



--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Ben Newlin]

A BYE ~30s after the ACK usually means the ACK was not accepted or associated 
with the call. This is usually due to some problem with the ACK. The ACK 
responses must be built according to specific requirements based on the INVITE 
and 200 OK values, so it is not possible to say for sure whether there is 
anything wrong with the ACK with only the ACK and BYE.

Ben Newlin 

On 4/29/20, 4:14 AM, "Users on behalf of Santi Anton" 
 wrote:

Hello,

If it helps, these are the ACK sent to MSTeams and BYE received after 20
seconds.

sbc..com:5067 Opensips TLS interface
195.xx.xx.xx:5068 Opensips UDP interface
80.xx.xx.xx:5060 Asterisk


ACK

sip:sip.pstnhub.microsoft.com;x-i=0c135a71-ddec-454c-a506-91079cb038d7;x-c=385a4453fc885c0bb6276a40d7796d3a/s/1/e1c45d052842415e9c0b3b0b04e32791
SIP/2.0
Via: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.2
Via: SIP/2.0/UDP
80.xx.xx.xx:5060;received=80.xx.xx.xx;branch=z9hG4bK0a1d079a;rport=5060
Route: 
Max-Forwards: 69
From: ;tag=as7659f57d
To: ;tag=50fe42a7fdb64fe583c1089a0b47f44a
Contact: 
Call-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx:5060:5060
CSeq: 102 ACK
User-Agent: FPBX-12.0.76.6(11.20.0)
Content-Length: 0


BYE sip:935441...@80.xx.xx.xx:5060 SIP/2.0
FROM:
;tag=50fe42a7fdb64fe583c1089a0b47f44a
TO: ;tag=as7659f57d
CSEQ: 3 BYE
CALL-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx:5060
MAX-FORWARDS: 69
VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bKf36698cf
REASON: Q.850;cause=18;text="0c135a71-ddec-454c-a506-91079cb038d7;*Call
Controller timed out while waiting for acknowledgement.*"
ROUTE:

,
CONTACT:

CONTENT-LENGTH: 0
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.20.2 i.EUWE.6
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY

Best Regards,



--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Santi Anton]

Hello,

If it helps, these are the ACK sent to MSTeams and BYE received after 20
seconds.

sbc..com:5067 Opensips TLS interface
195.xx.xx.xx:5068 Opensips UDP interface
80.xx.xx.xx:5060 Asterisk


ACK
sip:sip.pstnhub.microsoft.com;x-i=0c135a71-ddec-454c-a506-91079cb038d7;x-c=385a4453fc885c0bb6276a40d7796d3a/s/1/e1c45d052842415e9c0b3b0b04e32791
SIP/2.0
Via: SIP/2.0/TLS 195.xx.xx.xx:5067;branch=z9hG4bK2f83.ee24a46.2
Via: SIP/2.0/UDP
80.xx.xx.xx:5060;received=80.xx.xx.xx;branch=z9hG4bK0a1d079a;rport=5060
Route: 
Max-Forwards: 69
From: ;tag=as7659f57d
To: ;tag=50fe42a7fdb64fe583c1089a0b47f44a
Contact: 
Call-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx:5060:5060
CSeq: 102 ACK
User-Agent: FPBX-12.0.76.6(11.20.0)
Content-Length: 0


BYE sip:935441...@80.xx.xx.xx:5060 SIP/2.0
FROM:
;tag=50fe42a7fdb64fe583c1089a0b47f44a
TO: ;tag=as7659f57d
CSEQ: 3 BYE
CALL-ID: 433371746cb44b7d76fdc42013bf9...@80.xx.xx.xx:5060
MAX-FORWARDS: 69
VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bKf36698cf
REASON: Q.850;cause=18;text="0c135a71-ddec-454c-a506-91079cb038d7;*Call
Controller timed out while waiting for acknowledgement.*"
ROUTE:
,
CONTACT:

CONTENT-LENGTH: 0
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.20.2 i.EUWE.6
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY

Best Regards,



--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Santi Anton]

Hello,

Same case here. I'm sending the ACK to MSTeams but after 20 seconds Opensips
gets a BYE with the same reason as you.
In my scenario both Opensips and Asterisk have public IP addresses and there
is no NAT between them.
Hope we can find why is MSTeams ignoring the ACK or what are we doing wrong.

Regards, 



--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[volga629 via Users]

Hello Everyone,

Thank you all for the help.

Here are some highlight

1. Avoid call NAT in reply with 200 OK with option 1 or 3

2. Preset routing header toward Microsoft Teams.

3. Use record route toward you asterisk or feeeswitch.

4. Append contact header in keepalive messages.

5. Use dialplan feature to remove append + to normalize phone numbers.


volga629


On 4/19/20 9:40 AM, volga629 via Users wrote:


Hello Johan,

Thank you for reply.


The only NAT problem can be on MS Teams Client,  because on Opensips 
side pretty sure all good.



volga629


On 4/19/20 3:04 AM, Johan De Clercq wrote:
Can’t it be a NAT problem? The IP address where the bye is coming 
from doesn’t seem a pstnhub to me.


Outlook voor iOS <https://aka.ms/o0ukef> downloaden

*Van:* Users  namens volga629 via 
Users 

*Verzonden:* Saturday, April 18, 2020 11:01:19 PM
*Aan:* OpenSIPS users mailling list ; 
Alexey Vasilyev 

*Onderwerp:* Re: [OpenSIPS-Users] ms teams ACK

Hello Alexey,

Thank you on reply,

I undone all changes regard headers changes and MS Teams send BYE 
directly to asterisk.


No Route header present.

But INVITE ACK 183 180 all travel with  proper routing information.


2020/04/18 17:54:28.599711 190.109.70.77:5060 -> 190.109.68.250:5060
BYE sip:11988582770@190.109.68.250:5060 
 SIP/2.0
FROM:  
;tag=4d7fb0763c224e39a13a03c669c4b387
TO:  
;tag=as41e97ff5

CSEQ: 3 BYE
CALL-ID: 2e6c1a8d2383a4752403e94512ced077@190.109.70.77 
<mailto:2e6c1a8d2383a4752403e94512ced077@190.109.70.77>

MAX-FORWARDS: 69
Via: SIP/2.0/UDP 
190.109.70.77:5060;branch=z9hG4bK050e.e400e373.0;i=66c9c603
VIA: SIP/2.0/TLS 
52.114.14.70:5061;rport=8208;received=52.114.14.70;branch=z9hG4bK9594cd7
REASON: 
Q.850;cause=18;text="fcb37a2a-4bc4-49b6-a5e3-aabddc8f7a22;Call 
Controller timed out while waiting for acknowledgement."
CONTACT: 
 


CONTENT-LENGTH: 0
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.13.7 i.ASSE.3
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY


volga629


On 4/18/20 5:13 PM, Alexey Vasilyev wrote:

Hi volga629,

There were nothing special for ACK. You don't need to change
To/From/Contact. All the necessary steps were in the article
https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/  and for most
people it still works.
So I'm not sure, that MS changed anything, because all the hardware SBCs
should change behaviour, so they need new firmware. SBC vendors should
inform customers to update etc. So this is not so simple process. And it
definitely make no sense for anybody.
And in the test lab for the article I've used absolutely the same
architecture with asterisk, the only difference was RTPEngine to transcode
SRTP-RTP.
And within test lab I've tested not only calls, but transfers worked fine
too.



-
---
Alexey Vasilyev
--
Sent 
from:http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org  <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Johan De Clercq]

Thanks for the response John, but it is for Volga.

Outlook voor iOS<https://aka.ms/o0ukef> downloaden

Van: John Quick 
Verzonden: Monday, April 20, 2020 10:51:01 AM
Aan: users@lists.opensips.org ; 'Johan De Clercq' 

Onderwerp: Re: [OpenSIPS-Users] ms teams ACK

Johan,

Check that you're not calling fix_nated_contact() in the onreply_route that
handles the 200 OK from Teams Proxy.
You must not fix the Contact in the 200 OK because then the ACK from your
end will be mis-routed.

John Quick
Smartvox Limited
Web: www.smartvox.co.uk<http://www.smartvox.co.uk>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[John Quick]

Johan,

Check that you're not calling fix_nated_contact() in the onreply_route that
handles the 200 OK from Teams Proxy.
You must not fix the Contact in the 200 OK because then the ACK from your
end will be mis-routed.

John Quick
Smartvox Limited
Web: www.smartvox.co.uk


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[volga629 via Users]

  
  
Hello Johan,
Thank you for reply.
  

  
The only NAT problem can be on MS Teams
Client,  because on Opensips side pretty sure all good.

  
volga629



On 4/19/20 3:04 AM, Johan De Clercq
  wrote:


  
  

  Can’t it be a NAT problem? The IP address where the bye
is coming from doesn’t seem a pstnhub to me.
  
  
  Outlook
  voor iOS downloaden

  
  
  Van: Users
   namens volga629 via
  Users 
  Verzonden: Saturday, April 18, 2020 11:01:19 PM
  Aan: OpenSIPS users mailling list
  ; Alexey Vasilyev
  
  Onderwerp: Re: [OpenSIPS-Users] ms teams ACK
 
  
  
Hello Alexey,
Thank you on reply,
I undone all changes regard headers
changes and MS Teams send BYE directly to asterisk.
  
No Route header present.
But INVITE ACK 183 180 all travel
with  proper routing information.
  

  
2020/04/18 17:54:28.599711
190.109.70.77:5060 -> 190.109.68.250:5060
BYE 
  sip:11988582770@190.109.68.250:5060 SIP/2.0
FROM: ;tag=4d7fb0763c224e39a13a03c669c4b387
TO: ;tag=as41e97ff5
CSEQ: 3 BYE
CALL-ID: 
  2e6c1a8d2383a4752403e94512ced077@190.109.70.77
MAX-FORWARDS: 69
Via: SIP/2.0/UDP
190.109.70.77:5060;branch=z9hG4bK050e.e400e373.0;i=66c9c603
VIA: SIP/2.0/TLS
52.114.14.70:5061;rport=8208;received=52.114.14.70;branch=z9hG4bK9594cd7
REASON:
Q.850;cause=18;text="fcb37a2a-4bc4-49b6-a5e3-aabddc8f7a22;Call
Controller timed out while waiting for acknowledgement."
CONTACT: 

CONTENT-LENGTH: 0
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.13.7
i.ASSE.3
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
  

  
volga629
  


On 4/18/20 5:13 PM, Alexey
  Vasilyev wrote:


  Hi volga629,

There were nothing special for ACK. You don't need to change
To/From/Contact. All the necessary steps were in the article
https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/ and for most
people it still works.
So I'm not sure, that MS changed anything, because all the hardware SBCs
should change behaviour, so they need new firmware. SBC vendors should
inform customers to update etc. So this is not so simple process. And it
definitely make no sense for anybody.
And in the test lab for the article I've used absolutely the same
architecture with asterisk, the only difference was RTPEngine to transcode
SRTP-RTP.
And within test lab I've tested not only calls, but transfers worked fine
too.



-
---
Alexey Vasilyev
--
Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


  

  


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Johan De Clercq]

Can’t it be a NAT problem? The IP address where the bye is coming from doesn’t 
seem a pstnhub to me.

Outlook voor iOS<https://aka.ms/o0ukef> downloaden

Van: Users  namens volga629 via Users 

Verzonden: Saturday, April 18, 2020 11:01:19 PM
Aan: OpenSIPS users mailling list ; Alexey Vasilyev 

Onderwerp: Re: [OpenSIPS-Users] ms teams ACK


Hello Alexey,

Thank you on reply,

I undone all changes regard headers changes and MS Teams send BYE directly to 
asterisk.

No Route header present.

But INVITE ACK 183 180 all travel with  proper routing information.


2020/04/18 17:54:28.599711 190.109.70.77:5060 -> 190.109.68.250:5060
BYE sip:11988582770@190.109.68.250:5060 SIP/2.0
FROM: 
;tag=4d7fb0763c224e39a13a03c669c4b387
TO: 
;tag=as41e97ff5
CSEQ: 3 BYE
CALL-ID: 
2e6c1a8d2383a4752403e94512ced077@190.109.70.77<mailto:2e6c1a8d2383a4752403e94512ced077@190.109.70.77>
MAX-FORWARDS: 69
Via: SIP/2.0/UDP 190.109.70.77:5060;branch=z9hG4bK050e.e400e373.0;i=66c9c603
VIA: SIP/2.0/TLS 
52.114.14.70:5061;rport=8208;received=52.114.14.70;branch=z9hG4bK9594cd7
REASON: Q.850;cause=18;text="fcb37a2a-4bc4-49b6-a5e3-aabddc8f7a22;Call 
Controller timed out while waiting for acknowledgement."
CONTACT: 

CONTENT-LENGTH: 0
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.13.7 i.ASSE.3
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY


volga629


On 4/18/20 5:13 PM, Alexey Vasilyev wrote:

Hi volga629,

There were nothing special for ACK. You don't need to change
To/From/Contact. All the necessary steps were in the article
https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/ and for most
people it still works.
So I'm not sure, that MS changed anything, because all the hardware SBCs
should change behaviour, so they need new firmware. SBC vendors should
inform customers to update etc. So this is not so simple process. And it
definitely make no sense for anybody.
And in the test lab for the article I've used absolutely the same
architecture with asterisk, the only difference was RTPEngine to transcode
SRTP-RTP.
And within test lab I've tested not only calls, but transfers worked fine
too.



-
---
Alexey Vasilyev
--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org<mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[volga629 via Users]

  
  
Hello Alexey,
Thank you on reply,
I undone all changes regard headers
changes and MS Teams send BYE directly to asterisk.
  
No Route header present.
But INVITE ACK 183 180 all travel with 
proper routing information.
  

  
2020/04/18 17:54:28.599711
190.109.70.77:5060 -> 190.109.68.250:5060
BYE sip:11988582770@190.109.68.250:5060 SIP/2.0
FROM:
;tag=4d7fb0763c224e39a13a03c669c4b387
TO: ;tag=as41e97ff5
CSEQ: 3 BYE
CALL-ID: 2e6c1a8d2383a4752403e94512ced077@190.109.70.77
MAX-FORWARDS: 69
Via: SIP/2.0/UDP
190.109.70.77:5060;branch=z9hG4bK050e.e400e373.0;i=66c9c603
VIA: SIP/2.0/TLS
52.114.14.70:5061;rport=8208;received=52.114.14.70;branch=z9hG4bK9594cd7
REASON:
Q.850;cause=18;text="fcb37a2a-4bc4-49b6-a5e3-aabddc8f7a22;Call
Controller timed out while waiting for acknowledgement."
CONTACT:

CONTENT-LENGTH: 0
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.13.7 i.ASSE.3
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
  

  
volga629
  


On 4/18/20 5:13 PM, Alexey Vasilyev
  wrote:


  Hi volga629,

There were nothing special for ACK. You don't need to change
To/From/Contact. All the necessary steps were in the article
https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/ and for most
people it still works.
So I'm not sure, that MS changed anything, because all the hardware SBCs
should change behaviour, so they need new firmware. SBC vendors should
inform customers to update etc. So this is not so simple process. And it
definitely make no sense for anybody.
And in the test lab for the article I've used absolutely the same
architecture with asterisk, the only difference was RTPEngine to transcode
SRTP-RTP.
And within test lab I've tested not only calls, but transfers worked fine
too.



-
---
Alexey Vasilyev
--
Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


  


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Alexey Vasilyev]

Hi volga629,

There were nothing special for ACK. You don't need to change
To/From/Contact. All the necessary steps were in the article
https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/ and for most
people it still works.
So I'm not sure, that MS changed anything, because all the hardware SBCs
should change behaviour, so they need new firmware. SBC vendors should
inform customers to update etc. So this is not so simple process. And it
definitely make no sense for anybody.
And in the test lab for the article I've used absolutely the same
architecture with asterisk, the only difference was RTPEngine to transcode
SRTP-RTP.
And within test lab I've tested not only calls, but transfers worked fine
too.



-
---
Alexey Vasilyev
--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[volga629 via Users]

  
  
Hello Ovidiu,
Thank you for reply
Call flow 

Asterisk <-> Opensips <-> MS Teams 

Call from MS Teams works 100 % include rtp, but to MS teams no. 

I am adding required record routes on INITIAL INVITE, but that
  not enough based on Johan posted docs.
I accommodated proper rewrite of From/To again based on spec doc
  in initial request.
All those parts based on debug doc.
Has to be something changed on Microsoft side.


volga629



volga629
  



On 4/18/20 4:33 PM, Ovidiu Sas wrote:


  You don't need to mess with the Contact header (unless you are
connecting NATed endpoints with MS servers).
You need to populate proper Record-Route headers in the initial INVITE
as explained int the blog:
https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/

-ovidiu

On Sat, Apr 18, 2020 at 3:26 PM volga629 via Users
 wrote:

  

Thank you for reply,

I fixed Contact header in ACK, but Microsoft still unhappy call drops after 20 sec.

ACK debug

https://paste.centos.org/view/21b816d1

volga629

On 4/18/20 5:54 AM, Johan De Clercq wrote:

Please find  the necessary manips in this doc.

https://www.oracle.com/webfolder/technetwork/acmepacket/Microsoft/SBC-MSFTTeams-NON-MB.pdf

https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/


Outlook voor iOS downloaden

Van: Users  namens volga629 via Users 
Verzonden: Saturday, April 18, 2020 3:38:33 AM
Aan: OpenSIPS users mailling list 
Onderwerp: [OpenSIPS-Users] ms teams ACK


Hello Everyone,

Is possible rewrite ACK contact header in dialog ?

My guess it expecting FQDN.

MS Teams disconnect the call after 20 sec

REASON: Q.850;cause=18;text="bc427610-edae-47b9-9daa-7ea74d40dcc7;Call Controller timed out while waiting for acknowledgement."

In this case ACK come from asterisk box.

Opensips Log:

/usr/sbin/opensips[3321]: [IN-DIALOG] [ACK] Contact header ~> [

volga629

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

  
  




  


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Ovidiu Sas]

You don't need to mess with the Contact header (unless you are
connecting NATed endpoints with MS servers).
You need to populate proper Record-Route headers in the initial INVITE
as explained int the blog:
https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/

-ovidiu

On Sat, Apr 18, 2020 at 3:26 PM volga629 via Users
 wrote:
>
> Thank you for reply,
>
> I fixed Contact header in ACK, but Microsoft still unhappy call drops after 
> 20 sec.
>
> ACK debug
>
> https://paste.centos.org/view/21b816d1
>
> volga629
>
> On 4/18/20 5:54 AM, Johan De Clercq wrote:
>
> Please find  the necessary manips in this doc.
>
> https://www.oracle.com/webfolder/technetwork/acmepacket/Microsoft/SBC-MSFTTeams-NON-MB.pdf
>
> https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/
>
>
> Outlook voor iOS downloaden
> 
> Van: Users  namens volga629 via Users 
> 
> Verzonden: Saturday, April 18, 2020 3:38:33 AM
> Aan: OpenSIPS users mailling list 
> Onderwerp: [OpenSIPS-Users] ms teams ACK
>
>
> Hello Everyone,
>
> Is possible rewrite ACK contact header in dialog ?
>
> My guess it expecting FQDN.
>
> MS Teams disconnect the call after 20 sec
>
> REASON: Q.850;cause=18;text="bc427610-edae-47b9-9daa-7ea74d40dcc7;Call 
> Controller timed out while waiting for acknowledgement."
>
> In this case ACK come from asterisk box.
>
> Opensips Log:
>
> /usr/sbin/opensips[3321]: [IN-DIALOG] [ACK] Contact header ~> 
> [
>
> volga629
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



-- 
VoIP Embedded, Inc.
http://www.voipembedded.com

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[volga629 via Users]

  
  
Thank you for reply,
I fixed Contact header in ACK, but Microsoft still unhappy call drops after 20 sec.
ACK debug

https://paste.centos.org/view/21b816d1
volga629

On 4/18/20 5:54 AM, Johan De Clercq
  wrote:


  
  

  Please find  the necessary manips
in this doc.
  
  
  https://www.oracle.com/webfolder/technetwork/acmepacket/Microsoft/SBC-MSFTTeams-NON-MB.pdf
  
  
  https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/
  
  



Outlook
voor iOS downloaden
  
  
  Van: Users
   namens volga629 via
  Users 
  Verzonden: Saturday, April 18, 2020 3:38:33 AM
  Aan: OpenSIPS users mailling list
  
  Onderwerp: [OpenSIPS-Users] ms teams ACK
 
  
  
Hello Everyone,
Is possible rewrite ACK contact header in dialog ?
My guess it expecting FQDN. 
MS Teams disconnect the call after 20 sec 

REASON: Q.850;cause=18;text="bc427610-edae-47b9-9daa-7ea74d40dcc7;Call Controller timed out while waiting for acknowledgement."

In this case ACK come from asterisk box.  
Opensips Log:
/usr/sbin/opensips[3321]: [IN-DIALOG] [ACK] Contact header ~> [

volga629 
  

  


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] ms teams ACK

[Johan De Clercq]

Please find  the necessary manips in this doc.

https://www.oracle.com/webfolder/technetwork/acmepacket/Microsoft/SBC-MSFTTeams-NON-MB.pdf

https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/


Outlook voor iOS<https://aka.ms/o0ukef> downloaden

Van: Users  namens volga629 via Users 

Verzonden: Saturday, April 18, 2020 3:38:33 AM
Aan: OpenSIPS users mailling list 
Onderwerp: [OpenSIPS-Users] ms teams ACK


Hello Everyone,

Is possible rewrite ACK contact header in dialog ?

My guess it expecting FQDN.

MS Teams disconnect the call after 20 sec

REASON: Q.850;cause=18;text="bc427610-edae-47b9-9daa-7ea74d40dcc7;Call 
Controller timed out while waiting for acknowledgement."

In this case ACK come from asterisk box.

Opensips Log:

/usr/sbin/opensips[3321]: [IN-DIALOG] [ACK] Contact header ~> 
[

volga629
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] ms teams ACK

[volga629 via Users]

  
  
Hello Everyone,
Is possible rewrite ACK contact header in dialog ?
My guess it expecting FQDN.

MS Teams disconnect the call after 20 sec

REASON: Q.850;cause=18;text="bc427610-edae-47b9-9daa-7ea74d40dcc7;Call Controller timed out while waiting for acknowledgement."

In this case ACK come from asterisk box.  

Opensips Log:
/usr/sbin/opensips[3321]: [IN-DIALOG] [ACK] Contact header ~> [

volga629

  


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users