Messages

136

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

« on: September 19, 2017, 04:48:51 AM »

Javascript is not an external module. Yate has a javascript module. See http://docs.yate.ro/wiki/Javascript

A regexroute example:

[extra]
chan.disconnected=

[chan.disconnected]
${cause_sip}^300$={
  ; TODO:
  ; - Logic to detect choices from message
  ; - Logic to setup called target from choices (route)
  ; On success set 'CALLTO' parameter in handled message
  ${CALLTO}.=dispatch chan.masquerade;message=call.execute;id=${id};callto=${CALLTO}
}

You can find more at docs.yate.ro

http://docs.yate.ro/wiki/Regular_expressions
http://docs.yate.ro/wiki/How_to_convert_SIP_headers_into_SIP_parameters_names_in_messages
http://docs.yate.ro/wiki/Debugging_and,_or_Investigation_of_messages

137

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

« on: September 19, 2017, 02:03:22 AM »

I don't know how choices are returned in contact header.

A call may be re-executed using chan.masquerade message.
Here is a javascript example of handling chan.disconnected:

function onChanDisc(msg)
{
    if (300 == msg.cause_sip) {
        var callto;
        // TODO:
        // - Logic to detect choices from message
        // - Logic to setup callto from choices (route)
        if (callto) {
            var m = new Message("chan.masquerade");
            m.message = "call.execute";
            m.id = msg.id;
            m.callto = callto;
            m.dispatch();
        }
   }
}

You may re-execute

138

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

« on: September 19, 2017, 01:02:19 AM »

You may handle yate internal messages.
Received contact may be found in 'sip_contact' parameter of:
chan.hangup message sent by outgoing sip call leg
chan.disconnected message sent by incoming call leg when disconnected from outgoing channel.

I would recommend to watch the chann.disconnected message: you may re-execute the incoming call leg

139

Yate users hangout place / Re: 4 digit dialing

« on: September 13, 2017, 12:34:50 AM »

You must escape chars used by regexp:

^\([0-9]\{4\}=goto ....

Note that this regexp will match any target starting with 4 digits. If you to match exactly 4 digits you must add a $ char at the end

140

YateBTS / Re: Hi I have problem with mine BladeRF

« on: September 08, 2017, 01:19:24 AM »

Maybe you should still post a log: it may show some warning...

141

YateBTS / Re: Hi I have problem with mine BladeRF

« on: September 07, 2017, 08:37:28 AM »

I can't help you you with the RSSI warning. Hope someone will tell something about it.

Maybe you should post a yate log to see what happens.

142

Yate users hangout place / Re: SIP line logon failure 401: Unauthorized

« on: September 07, 2017, 04:01:23 AM »

Don't know what to say.
Did you tried another SIP client (X-lite) as suggested by provider? If it doesn't work this will definitely indicate a server failure.

You may also take a look at RFC 2617.
For 'qop'='auth' the response is calculated by:
response = md5(md5(username:realm:password):nonce:nc:cnonce:qop:md5(method:uri))
You may check Yate's response using log data (fields in Authorization header) and known password

You may also check (and dump here if possible) failed REGISTER transactions.
You may check for differences or patterns.

143

Yate users hangout place / Re: SIP line logon failure 401: Unauthorized

« on: September 07, 2017, 01:17:03 AM »

Can you post the log before last 401 (full REGISTER transaction)?
Can you say what is wrong with nonce handling?

144

YateBTS / Re: Hi I have problem with mine BladeRF

« on: September 07, 2017, 01:14:00 AM »

Radio (ybladerf) module is missing.
Possible causes: not loaded, not installed, not built.
Are you running yatebts from installed package or locally compiled?

145

Yate users hangout place / Re: Fallback only if SIP response 408 TIMEOUT

« on: September 05, 2017, 12:42:25 AM »

Take a look at call fork module
http://docs.yate.ro/wiki/Call_Forker
You may use fork.stop=timeout

146

YateBTS / Re: YateBTS with LimeSDR problem

« on: August 14, 2017, 12:39:39 AM »

bladeRF (radio) module is not available: not built or not installed.
If you are building yate: bladerf module depends on libusb. Make sure libusb devel package is installed.

147

YateBTS / Re: DTMF problem

« on: August 04, 2017, 08:27:31 AM »

You may try to following (not tested):

regexroute.conf:

[extra]
chan.dtmf=

[chan.dtmf]
${peerid}^ybts/=enqueue chan.masquerade;id=${peerid};message=chan.attach;override=tone/dtmfstr/${text}

148

YateBTS / Re: DTMF problem

« on: August 02, 2017, 08:25:26 AM »

You may try to generate inband dtmf:
Catch chan.dtmf message, and attach a tonegen source to indicated peerid.
See:
http://docs.yate.ro/wiki/Chan.masquerade
http://docs.yate.ro/wiki/Tonegen#Override_data_source (override=tone/dtmf/handled_digit_in_chan_dtmf)
http://docs.yate.ro/wiki/Chan.attach

Bottom line
Send a chan.masquerade with message 'chan.attach' to peerid taken from handled chan.dtmf to attach a tone generator for received DTMF.

149

YateBTS / Re: DTMF problem

« on: August 02, 2017, 12:42:22 AM »

DTMF forward to MS is not implemented.

150

YateBTS / Re: Problem : Registration fail

« on: July 28, 2017, 12:46:27 AM »

Try a different format (slin).
Check if received data (audio) is good: record is as good as received audio data!