Yes, but I *am* testing [well, development] ;) - besides, before I
put things into production, I test them in testing, so I already
know it will work [at least, in theory].
After the restart of FS, it still didn't work.
On 07/12/11 06:49, Avi Marcus wrote:
Maybe in testing, but in production you kinda need
to know what you can change live... reloadxml does the dialplan,
reload mod_x does that mod, and "sofia $profile killgw $gw" I
think kills that gateway, then you can do a rescan..
I fully shut it
down freeswitch, and then started it up again (I've
found that the time wasted doing a complete shutdown is
more than offset by the hours you can waste trying to
figure out why your changes don't take effect
;-) )
On 06/12/11 22:01, Avi Marcus wrote:
Did you kill and restart the
gateway after adding the variable? (Or restart
the entire interface, or restart FS?)
Michael, I'm familiar with the info
application, and have been using this
to test my progress. It's gotten me a
long way, but not past this hurdle.
Avi, I tried that, or at least my
interpretation of that, and it didn't
work.
I found the gateway in question - it's
one of only two references to the
trunk - in sip_profiles/. The
declaration, including my addition of
the variables clause, looks like this:
I then called in via that interface,
using a DDI, with the info
application. I got lots of
information, but neither foo nor bar.
I did change the direction from
"inbound" to "both", to make it as
likely as possible to work.
The log output I got had lots of stuff
in it (see http://pastebin.freeswitch.org/17943
) but no foo, no bar, and no trunk_1.
It did have several occurrences of the
ip address of talk2, 10.10.9.1, but
that can change. I also see several
references to the ip address
(10.10.10.149) and sofia profile name
(sipinterface_3), but all gateways
will be on the same profile.
Hmm, gateways on the wiki
should be cleaned up.. I
couldn't find it on the
wiki, only via google.
-Avi
On
Tue, Dec 6, 2011 at
12:45 AM, Michael
Collins <msc@freeswitch.org>
wrote:
Try adding one of
these to the dialplan
that handles inbound
calls:
<action
application="info"/>
Then, watch the
console while an
inbound comes in and
you'll see quite a
lot of information.
Anything in that
info dump is
available to you for
"figuring out"
what's going on. If
you have any
questions then drop
that info output to
a pastebin and give
us the URL here.