<div dir="ltr"><div><div><div>FS or anything else, opposite of profile configurations, arbitrarily, changes sip port 5060 to 10037!<br></div>this is my sip profile:<br>freeswitch@internal> sofia status<br> Name Type Data State<br>
=================================================================================================<br> 89.165.7.58 alias sipinterface_2 ALIASED<br> voicemail_1 alias sipinterface_2 ALIASED<br>
voicemail_2 alias sipinterface_2 ALIASED<br> sipinterface_2 profile <a href="http://sip:mod_sofia@192.168.2.73:5070">sip:mod_sofia@192.168.2.73:5070</a> RUNNING (0)<br>
sipinterface_5 profile <a href="http://sip:mod_sofia@192.168.2.73:10037">sip:mod_sofia@192.168.2.73:10037</a> RUNNING (0)<br> sipinterface_5::trunk_3 gateway <a href="mailto:sip%3ATCAPI_User@192.168.2.10">sip:TCAPI_User@192.168.2.10</a> NOREG<br>
sipinterface_3 profile <a href="http://sip:mod_sofia@192.168.2.73:5080">sip:mod_sofia@192.168.2.73:5080</a> RUNNING (0)<br>=================================================================================================<br>
3 profiles 3 aliases<br><br></div><div>Also, in a few weeks ago, i saw that sip crawlers with high sip registration requests can meddle on FS SQLite db reactions belongs to sip interfaces! In that event, i was forced to delete sipinterface_1 identified with SQLite DB and define new interface named sipinterface_5 with port 5060. This paragraph is just one report although everyone knows FS is a great man!<br>
<br></div>I will send you XML config file, if it's needed!<br></div>Good luck,<br></div>