<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I disagree. The blog pre assumes a MASSIVE amount of knowledge and configuration
<div class=""><br class="">
</div>
<div class="">with a pre-existing opensips.conf routing set up</div>
<div class=""><br class="">
</div>
<div class="">Goodness knows what that is. It isn’t the Proxy set up or the Residential set up. I’ve tried both and neither work.</div>
<div class=""><br class="">
</div>
<div class="">It would be really helpful if the Blog started with which config file it is based on and went from there.</div>
<div class=""><br class="">
</div>
<div class="">With a lot of blind hacking around on the script I’ve got to the stage where</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">Teams outbound works fine with a </div>
<div class="">
<div class=""> $rd="<a href="http://pbx.ip-sentinel.com" class="">pbx.ip-sentinel.com</a>";</div>
<div class=""> $rp=5081;</div>
</div>
</div>
<div class=""><br class="">
</div>
<div class=""> However to have the Inbound accepted by MS Teams I have to modify the TO, FROM add a ROUTE AND force the CONTACT</div>
<div class="">
<div class=""> <span class="Apple-tab-span" style="white-space:pre"> </span>strip(1);</div>
<div class=""> prefix("+44");</div>
<div class=""> uac_replace_from( , "<a href="sip:$fU@sbc.ip-sentinel.com:5091" class="">sip:$fU@sbc.ip-sentinel.com:5091</a>");</div>
<div class=""> uac_replace_to( , "<a href="sip:$rU@sip.pstnhub.microsoft.com" class="">sip:$rU@sip.pstnhub.microsoft.com</a>");</div>
<div class=""> $rd="<a href="http://sip.pstnhub.microsoft.com" class="">sip.pstnhub.microsoft.com</a>";</div>
<div class=""> $rp=5061;</div>
<div class=""> record_route_preset("<a href="http://sbc.ip-sentinel.com:5091" class="">sbc.ip-sentinel.com:5091</a>;transport=tls”);</div>
<div class="">And in the route</div>
<div class="">
<div class=""> <span class="Apple-tab-span" style="white-space:pre"> </span>if(check_source_address(0)){</div>
<div class=""> xlog("[INFO] FIX ACK CONTACT");</div>
<div class=""> remove_hf("Contact");</div>
<div class=""> append_hf("Contact: <<a href="sip:$fU@sbc.ip-sentinel.com:5091;transport=tls" class="">sip:$fU@sbc.ip-sentinel.com:5091;transport=tls</a>>\r\n”);</div>
<div class="">And onroute_reply</div>
<div class="">
<div class=""> <span class="Apple-tab-span" style="white-space: pre;"> </span>
if(check_source_address(0)){</div>
<div class=""> xlog("[INFO] FIX ACK CONTACT");</div>
<div class=""> remove_hf("Contact");</div>
<div class=""> append_hf("Contact: <<a href="sip:$fU@sbc.ip-sentinel.com:5091;transport=tls" class="">sip:$fU@sbc.ip-sentinel.com:5091;transport=tls</a>>\r\n”);</div>
</div>
</div>
</div>
<div class=""><br class="">
</div>
<div class="">However even with that I eventually miss an ACK and the whole thing falls over. Most frustrating!</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<br>
<p style="font-family: Open Sans,sans-serif;">
<b><span style="font-family: Open Sans,sans-serif; font-size:10.0pt;color:#888888">James Hogbin</span></b>
<b><span style="font-family: Open Sans,sans-serif;font-size:8.0pt;color:#888888;"><br>Director</span></b>
</p>
<table border="0" cellspacing="0" cellpadding="0"><tr><td><a href="http://ip-sentinel.com"><IMG border="0" alt="IP Sentinel Logo" src="cid:120051118424100357@uk-mta-247.uk.mimecast.lan" ></A></td></tr></table>
<span style="font-family: Open Sans,sans-serif;font-size:8.0pt;color:#222222;"><br>t. <a href="tel:+442030114150" target="_blank">+44 (0)20 3011 4150</a><br></span><span style="font-family: Open Sans,sans-serif;font-size:8.0pt;color:#222222;">m. +44 7786910895<br></span><span style="font-family: Open Sans,sans-serif;font-size:8.0pt;color:#222222">w. <a href="https://www.ip-sentinel.com/" target="_blank">https://www.ip-sentinel.com</a><br></span><table>
<tbody><tr>
</tr>
<tr>
</tr>
<tr>
</tr>
<tr>
</tr>
</tbody></table>
<br>
On 11 May 2020, at 18:14, Ovidiu Sas <<a href="mailto:osas@voipembedded.com" class="">osas@voipembedded.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">
<div dir="auto" class="">Microsoft’s SIP routing is RFC compliment.</div>
</div>
<div dir="auto" class="">There’s no special routing for approved SBCs. The routing Is based on the type of SBC: B2BUA vs proxy, which again, is rfc complient.</div>
<div dir="auto" class="">For OpenSiPS, which is a proxy, all the configuration steps are very well outlined in the blog. No need to mess with Via or Contact headers! Follow the loose routing rules as outlined in the rfc and all is good.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">Regards,</div>
<div dir="auto" class="">Ovidiu Sas</div>
<div class=""><br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, May 11, 2020 at 05:51 Slava Bendersky via Users <<a href="mailto:users@lists.opensips.org" class="">users@lists.opensips.org</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<div style="font-family: "lucida console", sans-serif; font-size: 12pt;" class="">
<div class="">Hello All,</div>
<div class="">Microsoft is rely on approved sbc vendors, where most sbc are use VIA and headers to route traffic. That why Contact header is important, also they use from and to.</div>
<div class="">Opensips is rely on route headers and use different way to route it.</div>
<div class=""><br class="">
</div>
<div class="">volga629 </div>
<div class=""><br class="">
</div>
<hr id="m_-2318876661958670388zwchr" class="">
<div class=""><b class="">From: </b>"John Quick" <<a href="mailto:john.quick@smartvox.co.uk" target="_blank" class="">john.quick@smartvox.co.uk</a>><br class="">
<b class="">To: </b>"OpenSIPS users mailling list" <<a href="mailto:users@lists.opensips.org" target="_blank" class="">users@lists.opensips.org</a>>,
<a href="mailto:james@ip-sentinel.com" target="_blank" class="">james@ip-sentinel.com</a><br class="">
<b class="">Sent: </b>Monday, May 11, 2020 6:19:50 AM<br class="">
<b class="">Subject: </b>Re: [OpenSIPS-Users] OpenSIPS as Teams SBC<br class="">
</div>
</div>
</div>
<div class="">
<div style="font-family: "lucida console", sans-serif; font-size: 12pt;" class="">
<div class=""><br class="">
</div>
<div class="">I agree completely with Ovidiu.<br class="">
The Microsoft documentation says to use a FQDN in the Contact header, but<br class="">
this is wrong when the SBC is acting as a SIP Proxy.<br class="">
The blog post on the OpenSIPS website explains that actually the<br class="">
Record-Route header needs the FQDN.<br class="">
The one exception to this is the handling of OPTIONS pings - for these,<br class="">
OpenSIPS is the end point so it must use a FQDN in Contact.<br class="">
<br class="">
If you change the Contact header in call setup then you risk breaking the<br class="">
path for sequential requests, such as ACK.<br class="">
If ACK does not reach its destination, the call drops at one end after about<br class="">
20 seconds - exactly what you are seeing.<br class="">
<br class="">
I have not yet found a good way to capture TLS encoded SIP. In theory, you<br class="">
can use sngrep with the -k option to identify the path to the private key<br class="">
file.<br class="">
It would be necessary to start sngrep first, then start (or restart)<br class="">
OpenSIPS. However, this never works for me.<br class="">
I had more success using the siptrace module to capture the packets to a DB<br class="">
table. Presenting it as a sequence diagram may be possible using the<br class="">
OpenSIPS Control Panel.<br class="">
Wireshark also has the ability to capture, decode and present TLS encrypted<br class="">
SIP.<br class="">
Another option might be to mirror the traffic to Homer in HEP format and<br class="">
then use Homer to create the sequence diagram.<br class="">
<br class="">
John Quick<br class="">
Smartvox Limited<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
Users mailing list<br class="">
<a href="mailto:Users@lists.opensips.org" target="_blank" class="">Users@lists.opensips.org</a><br class="">
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank" class="">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br class="">
</div>
</div>
</div>
_______________________________________________<br class="">
Users mailing list<br class="">
<a href="mailto:Users@lists.opensips.org" target="_blank" class="">Users@lists.opensips.org</a><br class="">
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank" class="">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br class="">
</blockquote>
</div>
</div>
-- <br class="">
<div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">VoIP Embedded, Inc.<br class="">
<a href="http://www.voipembedded.com/" target="_blank" class="">http://www.voipembedded.com</a></div>
_______________________________________________<br class="">
Users mailing list<br class="">
<a href="mailto:Users@lists.opensips.org" class="">Users@lists.opensips.org</a><br class="">
http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br class="">
</div>
</blockquote>
</div>
<br class="">
<p style="font-family: Open Sans, Arial, sans-serif;padding: 5px;background:#D5EAFF">
<span style="font-family: Open Sans,sans-serif;font-size:8.0pt;color:red">IP Sentinel Disclaimer <br></span>
<span style="font-family: Open Sans,sans-serif;font-size:6.0pt;color:black">The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. Unintended recipients are prohibited from taking action on the basis of information in this e-mail. If you are not the intended recipient or have received this email in error, please notify the sender immediately by return email and delete the email from your computer.
E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. We do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of computer viruses or other defects.
. 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. </span>
</p><span style="font-size:1.0pt;color:white">Q3dhRSrm_disclaimer</span>
</body></html>