[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Paul Chitescu <paulc@v...>
 Subject :  Re: [yate] accfile uplink, no callerID
 Date :  Fri, 6 Feb 2015 13:01:41 +0200
Hi!

What you describe is not the default behavior of the modules in question.

Can you check your config files for the one changing the caller parameter?

One way to figure out which module may did the change is to connect to 
rmanager and issue this command:

  sniffer on filter call\.\(.*route\|execute\)

And then make a call in the scenario that doesn't work.

This will display call.preroute, call.route and call.execute messages in their 
initial and final (after dispatch) form. Look at the "handlers" parameter in 
the final form to see which modules were involved when the "caller" was 
modified.

Paul


On Fri Feb 6, 2015 12:16:42 Yu Boot wrote:
> ANYONE?! I think that to replace inbound callerID with accfile SIP login
> is totally meaningless. How to change this Yate behavior? We really need
> to fix this problem :(
>
> 01.02.2015 18:47, Yu Boot пишет:
> > Anyone? Here's some more info about this problem:

> accfile.conf:
> [trunk1]
> enabled=yes
> protocol=sip
> formats=alaw
> registrar=1.X.X.X:9060
> outbound=1.X.X.X:9060
> interval=180
> username=014716
> authname=014716
> password=XXXXXXXXXX
>
> regexroute.conf:
> [to_client1]
> .*$=return;called=0000007;
>
> regfile.conf:
> [0000007]
> password=XXXXXX