<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello Sergey<br>
<br>
I tried to change the cidr attribute with my gateway public IP but
this change nothing. My provider did not provide a different SIP
accound for each DID number. I actually have 2 DID numbers on this
test platform but if i migrate my production servers from asterisk
to freeswitch i will manage about 50 DID numbers for this provider
and probably more in the future.<br>
<br>
I also tried to fetch a minimal configuration from freeswitch source
( $somewhere/freeswitch.git/conf/minimal/ ) to replace the default
configuration provided by the fusionpbx installer, then i just
copied my original trunk configuration in
/usr/local/freeswitch/conf/sip_profiles/external<br>
<br>
I did not set a dialplan for testing everything but it's seems to
work better: when i call 0557590xxx i got the following message<br>
<br>
2015-05-03 09:14:54.587286 [INFO] mod_dialplan_xml.c:635 Processing
0967212xxx <0967212xxx>-><b>0557590xxx</b> in context
public<br>
<br>
In comparison with<br>
<br>
2015-05-01 18:02:12.235827 [INFO] mod_dialplan_xml.c:635 Processing
0967212xxx <0967212xxx>-><b>0033972480xxx</b> in context
public<br>
<br>
There is probably something bad in the default configuration
provided by fusionpbx witch prevent auto_to_user to work properly. I
will compare configuration files from minimal freeswitch sample
configuration and from freeswitch and try to determine where is the
problem. This may deserve a but report :-)<br>
<br>
Thanks <br>
<br>
<br>
On 02/05/2015 20:55, Sergey Safarov wrote:
<blockquote
cite="mid:CAHtxdDcnQ2z33HqL0KtuzETpj5aCpMotzD_vZyvHQyU9p_=kEg@mail.gmail.com"
type="cite">
<div dir="ltr">In log you can see invite arrived from IP
address 91.121.129.20
<div>Change IP <a moz-do-not-send="true"
href="http://10.7.1.60/32">10.7.1.60/32</a> to <a
moz-do-not-send="true" href="http://91.121.129.20/32">91.121.129.20/32</a></div>
<div><br>
</div>
<div><span style="font-size:12.8000001907349px">I'm not sure to
understand why i should use a so strange trick. Using
"internal" profile for external trunk can't be a security
leak ?</span></div>
<div>It is not problem. In this case profile used for
authenticate call by user "provider_gw1". Real call processing
executed in dialplan "provider_inbound_calls". In this
dialplan you can allow one DID number and block all other.</div>
<div><br>
</div>
<div><span style="font-size:12.8000001907349px">If my provider
change something about the 10.7.6.60 gateway, the trunk will
no longer work until i update my configuration ?</span><br>
</div>
<div>If provider can configure username and password for DID
call authentication you can remove "cird" attribute.</div>
<div>If username and password can't be configured, then say me
how much DID number provider assigned for you.</div>
<div><br>
</div>
<div>Sergey</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>