Hi!
Attached sip.conf and interface config as well. In this case we use only
TLS, but I have checked with TCP - same situation, 192.168.0.172 is used as
a source. For UDP 192.168.0.177 is used as expected.
??, 13 ???. 2017 ?. ? 2:37, Joshua Colp <jcolp at digium.com>:
> On Sat, Mar 11, 2017, at 11:50 AM, Kseniya Blashchuk wrote:
> > Hey guys, any thoughts on that? Probably a bug or is it a default
> > behavior?
>
> I'd suggest providing the configuration to make sure it is correct.
>
>
> --
> Joshua Colp
> Digium, Inc. | Senior Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - US
> Check us out at: www.digium.com & www.asterisk.org
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at:
> https://community.asterisk.org/
>
> New to Asterisk? Start here:
> https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20170313/5e43e561/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config_sip
Type: application/octet-stream
Size: 864 bytes
Desc: not available
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20170313/5e43e561/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ip_a
Type: application/octet-stream
Size: 294 bytes
Desc: not available
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20170313/5e43e561/attachment-0001.obj>