Messages

121

Windows / Re: Windows client source code.

« on: February 12, 2018, 01:50:55 AM »

Qt widgets and css files are located in source code at:
share/skins/default

Common (all platforms): stylesheet.css
Windows override: stylesheet_oswindows.css

You may also change fonts by editing Qt widgets in Qt designer.

Keep in mind that not all controls adjust their size when font changes: make sure the text is properly displayed.

122

Other Yate server issues / Re: Overlapped - called incomplete

« on: February 06, 2018, 05:11:13 AM »

I think you have an error in your routing logic.
As seen in log you have a module (route_proc) handling call.route after regexroute and returning true with target set.
Please check it.

NOTE: This is not correct:
^060902146.*=external/nodata/overlapped.php;accept_call=false
^06090214635478500$=sip/sip:\0@172.16.22.2
The first rule will always match before the second one.

123

Other Yate server issues / Re: Overlapped - called incomplete

« on: February 06, 2018, 04:11:58 AM »

What do you mean by 'I can see the final number catches on chan.dtmf ...'?

If you mean you are seeing a chan.dtmf before routing: keep in mind that overlapped routes the initial number first!
Be prepared for it!
If you don't return a target for it a subsequent route attempt will be done by adding received DTMFs.

124

Other Yate server issues / Re: Overlapped - called incomplete

« on: February 06, 2018, 03:42:14 AM »

What exactly is the issue?

Initial number routing is handled and a route is returned.

125

Other Yate server issues / Re: Overlapped - called incomplete

« on: February 06, 2018, 02:56:59 AM »

Can you post a log with message sniffer enabled?

126

Windows / Re: yate client with jingle

« on: January 25, 2018, 03:16:46 AM »

Call option in contacts list context menu is enabled when the jingle module detects audio support is advertised by contact's client application.

You may want to post a log with jabber messages.

Check the Settings -> Debug Window option

127

Yate bugs / Re: Localhost as public...

« on: January 25, 2018, 03:09:30 AM »

You may take a look at http://docs.yate.ro/wiki/Ysipchan

Check the 'rtp_localip' and 'nat_address' parameters

128

Windows / Re: Yate Window 6 Font Size

« on: January 05, 2018, 02:17:15 AM »

There is no configuration for it.
Try to lower screen resolution.

129

Linux / Re: embedding Yateclient with rmanager controls

« on: November 29, 2017, 02:36:10 AM »

I suppose you are routing incoming calls to an audio device module (alsachan).
You may add an autoanswer=no parameter when routing the call.

You need some logic to anwer calls on demand.
You may write a javascript script to track calls (you may use call.cdr for that, 'chan' parameter is what you need.
The script should implement a command to answer (just send a chan.masquerade message with call,answered) a specific channel id.

130

Linux / Re: Unique ringtone device or action - how?

« on: November 21, 2017, 02:19:36 AM »

YateClient has no support for separate audio device for incoming call alert.

You may implement some script to track incoming calls and play some alert on a device you want.
Audio device modules are located in modules/client (for various platforms there are alsa/oss (Linux), coreaudio (Mac) and dsound (Windows)).
Your script should track incoming calls, play a sound on a device at your choice and stop it when call is answered.

You may find some documentation at docs.yate.ro
You may want to look at chan.* and call.* messages.

131

Other Yate server issues / Re: Record all call

« on: October 20, 2017, 07:43:09 AM »

gsm codec is not available
It is implemented in gsmcodec.yate module

132

Yate users hangout place / Re: yate as small pbx: context routing questions

« on: October 05, 2017, 01:11:39 AM »

An incoming call has 3 stages of processing:
1. Pre-route. This may be used to handle the call origin, adjust parameters ... The [contexts] section in regexroute.conf handles the call.preroute message. The pre-route stage stopes when a context is returned.
2. Route. This is used to return an internal target and additional parameters used to make the outgoing call. The [default] section or sections matching 'context' returned in pre-route are used by regexroute module to return (or not) a target. Route stops when a target or error is returned
3. Execute. Execute the call to specified target

The regfile module is a routing module. When call.route is handled and called party number indicates a registered user the module will return its location (target). Routing process stops. No other module will handle call.route.
If you want to handle the call.route in regexroute just lower its call.route priority (see the 'route' parameter in [priorities] section. This will make regexroute to handle the call.route message before regfile module.

An alternative is to install a call.execute message handler in regexroute:
[extra]
call.execute=30

[call.execute]
${context}^INTERNAL$= ............ Call was routed by regfile
${context}^BLACKHOLE$= .............. Call was routed by regexroute

133

Yate users hangout place / Re: masquerade message from external does not work

« on: September 20, 2017, 03:54:18 AM »

Didn't saw it in first post: message name parameter in chan.masquerade should be 'message' not 'messagae'

134

Other Yate server issues / Re: Yate Redirect SIP 300 Multiple Choices

« on: September 20, 2017, 03:29:56 AM »

You'll have to track the call to know its parameters.

A way to do it is to use a javascript routing script (see http://docs.yate.ro/wiki/How_to_do_routing_using_javascript)
The script will be attached to the incoming call leg. You may remember caller party in the script and handle redirect

You may also write a global script to track all call legs, remember their parameters and re-execute on disconnected.

I don't understand what do you mean by 'routing is not stopped'.
chan.disconnected is sent when the incoming call leg was detached: any internal routing process was terminated.
Please attach a log with message sniffer enabled.

135

Yate users hangout place / Re: masquerade message from external does not work

« on: September 20, 2017, 12:56:48 AM »

You should post a log to see what happens.