Messages

1

Other Yate server issues / Lksctp, S.O. and kernel version

« on: February 16, 2024, 12:56:43 PM »

Hi everyone,

What is the latest kernel version supported to use sigtran with M2UA protocol with Mediant?
About Debian, how is the latest release used in this case?

BR,

RP

2

Other Yate server issues / Re: help with m2pa connection

« on: February 16, 2024, 12:48:39 PM »

What is your SO and the kernel version?

Br,
 
RP

3

Other Yate server issues / Re: Different DTMF per leg on same Call

« on: May 20, 2023, 11:55:00 AM »

Solved!

Code: [Select]

msg["odtmfmethods"]="rfc2833";
msg["tonedetect_in"]="yes";
msg["tonedetect_out"]="yes";


4

Other Yate server issues / Re: Different DTMF per leg on same Call

« on: May 20, 2023, 07:50:48 AM »

In yate log I could see:
2023-05-20_10:30:36.072021 <sip/1515732:NOTE> Failed to send tones '4' methods=rfc2833 [0x7f847c01fc40]
Returned false 'chan.dtmf' delay=0.003155
  thread=0x28755e0 'Engine Worker'
  data=0x7f874c0dced0
  retval='(null)'
  param['id'] = 'sip/1515731'
  param['text'] = '4'
  param['detected'] = 'inband'
  param['handlers'] = 'sip:10,pbxassist:15,conf:75,sip:100,dumb:100,callfork:100,filetransfer:100,wave:100,iax:100,jingle:100,analog:100,mgcpgw:100,sig:100,yrtp:150'
  param['sequence'] = '1'
  param['duplicate'] = 'false'
  param['module'] = 'sip'
  param['status'] = 'answered'
  param['address'] = '10.11.255.249:64989'
  param['targetid'] = 'sip/1515732'
  param['billid'] = '1677205349-772582'
  param['peerid'] = 'sip/1515732'
  param['lastpeerid'] = 'sip/1515732'
  param['answered'] = 'true'
  param['direction'] = 'incoming'
  param['domain'] = '10.11.255.131'
  param['callid'] = 'sip/R3ArPBnexQwoArpH35rEcA../7665b20a/1797993596'

5

Other Yate server issues / Re: Different DTMF per leg on same Call

« on: May 20, 2023, 06:07:44 AM »

Only to clarify, this about dtmf transcoding.
Br,

Rodrigo

6

Other Yate server issues / Different DTMF per leg on same Call

« on: May 12, 2023, 08:39:36 AM »

Hi everyone, we have an yate server, and have two clients running with different DTMF types. A side A uses Inband, and side B uses RFC 2833 because the type os your cpe. Side B have a IVR, and when Side A calls to B, Yate need to offer RFC2833 because the limitantion of this IVR Server. Yate, is a B2BUA server on this scenario. Could Yate support  different DTMF Types for each call leg? Receive from A inband and send to B RFC2833? Today, we can't see it woking correctly. Inband clients work only Inband and RFC with RFC. Anyone could help about this scenario?

BR,
Rodrigo Passos

7

Yate bugs / Supervison restarting yate unexpectedly

« on: April 24, 2018, 08:06:29 AM »

Hi all,
i have yate restarting without any out message, only with supervisor issue.
In dump file, i can't identify the real cause of this.
Anyone could help to identify the cause of this problem or show if it is a bug?

BR,

Rodrigo

8

Other Yate server issues / Re: Overlapped - called incomplete

« on: February 06, 2018, 05:40:14 AM »

Mariam,
Problem solved. I'm returning false in my router script while length of called number is minor of 16, and after, i have the complete number catched in javascript.

Thank a lot again.

BR,

Rodrigo

9

Other Yate server issues / Re: Overlapped - called incomplete

« on: February 06, 2018, 05:01:02 AM »

Marian,

 I mean that i can see the last number in DTMF, but, the php script doesn't change the c?alled number how can see on sniffer. The php overlapped scrip will modify called number before exit

I'm waiting the final number with 0. If a put a regexroute like follow, but without any success.
${overlapped}yes=goto overlapped
^060902146.*=external/nodata/overlapped.php;accept_call=false
^06090214635478500$=sip/sip:\0@172.16.22.2

[overlapped]
.*=;error=incomplete

10

Other Yate server issues / Re: Overlapped - called incomplete

« on: February 06, 2018, 04:02:13 AM »

Marian,

I can see the final number catches on chan.dtmf, but i  can't see called number modified by overlapped script. I can get it on javascript?

BR,

Rodrigo

11

Other Yate server issues / Re: Overlapped - called incomplete

« on: February 06, 2018, 03:12:15 AM »

Hi Marian,

Follow the attached log file with a call example.

BR,

Rodrigo

12

Other Yate server issues / Overlapped - called incomplete

« on: February 05, 2018, 09:23:05 PM »

Hi Yate,

I have seen a called number  incomplete after call overlapped script. Initially, i make call overlapped script in regexroute and ffter, trying to use msg.called on javascript message. So, the same problem occurs if using regexrout only with sip/sip:\0@sip_server. I can't see called number completed after. Anyone knows what wrong?

Regards.

Rodrigo R Passos

13

Other Yate server issues / Re: TCP Calls using Yate

« on: June 28, 2017, 09:46:44 PM »

Hi Yate,

Problem solved using oconnection_id.
Regards,
Rodrigo

14

Other Yate server issues / TCP Calls using Yate

« on: June 28, 2017, 01:38:40 PM »

Hi Yate,

I'm trying to setup a call with Yate using TCP. Yate has listen all calls via TCP from Zoiper client, but, when i trying to forward a call to Zoiper, Yate send the invite using UDP.
In javascript, i'm seting up the transport to TCP using msg.ip_transport = "TCP", but without success. On call.execute message i can see param['ip_transport'] = 'TCP', but on invite packet     Via: SIP/2.0/UDP 10.45.0.11:5060;rport;branch=z9hG4bK1373430624.

Anyone knows how can correct this packet?

Regards,

Rodrigo

15

Yate bugs / Issue in Pending Operation

« on: February 06, 2017, 07:43:34 AM »

Hi Yate,

For a while, I've noticed a problem with CGU Pending message. Yate could not put ISUP circuit in available without restart the application. On the other Telco side, all circuits are ok, but in my side, i see all circuits with changing=true,flags=0x14.
Using control command i can't put circuits in available mode and in Yate log i see Pending operation 'CGU' cic=129 reason='' timed out. When i restart the application, in log, i have notice of a dequeue process in this isup circuit.
What happening with yate on this situation? Yate had block all internal signal? Exists any command to solve this problem? This is a real bug, and, to Yate  back to normal only with restart?

Regards,

Rodrigo R Passos