361
Other Yate server issues / Re: Yate & RFC-2806
« on: November 14, 2014, 03:42:40 AM »
Hi,
Can you describe what exactly do you need?
Can you describe what exactly do you need?
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
362
Yate users hangout place / Re: hangup event?
« on: November 13, 2014, 02:55:18 AM »
The message sent when a channel is hungup is chan.hangup.
For billing purposes you may se call.cdr messages.
Check the operation parameter. It will be "finalize" when the channel is hungup.
For billing purposes you may se call.cdr messages.
Check the operation parameter. It will be "finalize" when the channel is hungup.
363
Other Yate server issues / Re: Yate diconnects call with "nomediaUnsupported Media Type"
« on: November 11, 2014, 05:40:44 AM »
The issue is noted and will be fixed.
See mailing list response.
See mailing list response.
364
Yate users hangout place / Re: round robin routing using db query
« on: November 11, 2014, 05:40:05 AM »
I'm not a good php programmer but it seems fine to me.
If you want to call on both targets (and rotate them) using fork I suppose you can:
Global variable:
$firstProvider = true;
In handler:
$ev->SetParam("callto.2","|");
if ($firstProvider) {
$ev->SetParam("callto.1","sip/sip:1@mysip1.com");
$ev->SetParam("callto.3","sip/sip:1@mysip2.com");
}
else {
$ev->SetParam("callto.1","sip/sip:1@mysip2.com");
$ev->SetParam("callto.3","sip/sip:1@mysip1.com");
}
$firstProvider = !$firstProvider;
$ev->retval = "fork";
If you want to call on both targets (and rotate them) using fork I suppose you can:
Global variable:
$firstProvider = true;
In handler:
$ev->SetParam("callto.2","|");
if ($firstProvider) {
$ev->SetParam("callto.1","sip/sip:1@mysip1.com");
$ev->SetParam("callto.3","sip/sip:1@mysip2.com");
}
else {
$ev->SetParam("callto.1","sip/sip:1@mysip2.com");
$ev->SetParam("callto.3","sip/sip:1@mysip1.com");
}
$firstProvider = !$firstProvider;
$ev->retval = "fork";
365
Yate users hangout place / Re: round robin routing using db query
« on: November 10, 2014, 10:21:55 AM »
To set message parameters use the SetParam method.
To obtain message params use the GetValue method.
$ev->SetParam("osip_Yatebillid",$ev->GetValue("billid"));
To obtain message params use the GetValue method.
$ev->SetParam("osip_Yatebillid",$ev->GetValue("billid"));
366
Yate users hangout place / Re: incoming Registration send in roundrobin
« on: November 07, 2014, 08:31:37 AM »
You can't forward the REGISTER itself to another party: Yate is not a proxy.
You may try to write an external script to handle user.auth and user.register messages and make another REGISTER request.
This is not an easy job to do.
You may try to write an external script to handle user.auth and user.register messages and make another REGISTER request.
This is not an easy job to do.
367
Yate users hangout place / Re: round robin routing using db query
« on: November 07, 2014, 08:24:02 AM »
Yes, you can.
Set the call target in call.route event retval.
E.g.:
$ev->retval = "sip/sip:1@1.2.3.4";
$ev->handled = true;
$ev->Acknowledge();
Set the call target in call.route event retval.
E.g.:
$ev->retval = "sip/sip:1@1.2.3.4";
$ev->handled = true;
$ev->Acknowledge();
368
Yate users hangout place / Re: round robin routing using db query
« on: November 06, 2014, 07:58:52 AM »
Hi,
Your script is receiving the message and don't handle it.
See handlers='register:50,regexroute:100,cdrbuild:50,register:50,route.php:80,fileinfo:90,subscription:100,iax:100,regexroute:100'
The message is handled by regexroute.
Check the script to see why it doesn't handle the message.
Your script is receiving the message and don't handle it.
See handlers='register:50,regexroute:100,cdrbuild:50,register:50,route.php:80,fileinfo:90,subscription:100,iax:100,regexroute:100'
The message is handled by regexroute.
Check the script to see why it doesn't handle the message.
369
Yate users hangout place / Re: round robin routing using db query
« on: November 05, 2014, 08:10:32 AM »
Hi,
Enable message sniffer (telnet command: msgsniff on).
Check the call.route message 'handlers' parameter. On return it should show the name of the message handler(s) processing it.
Enable message sniffer (telnet command: msgsniff on).
Check the call.route message 'handlers' parameter. On return it should show the name of the message handler(s) processing it.
370
Linux / Re: the sip status abnormal
« on: October 10, 2014, 10:56:53 AM »
Hi,
Can you post a log file?
You should share your changes also.
Can you post a log file?
You should share your changes also.
371
Linux / Re: yate-qt4 popup
« on: October 03, 2014, 07:06:10 AM »
There is no easy way to disable the incoming call notification.
You can do it by preventing yate to build the notification window:
Edit qt4client.rc
Delete the [notification] section.
The file should be located in
/usr/share/yate/skins/default
You can do it by preventing yate to build the notification window:
Edit qt4client.rc
Delete the [notification] section.
The file should be located in
/usr/share/yate/skins/default
372
YateBTS / Re: Dial tone can't hear
« on: September 22, 2014, 03:40:24 AM »
There is no configuration for it.
If the called client don't provide ringback you may use fork.
See http://docs.yate.ro/wiki/Call_Forker#Providing_fake_ringback_tone_while_fallback_calling_through_different_gateways
If the called client don't provide ringback you may use fork.
See http://docs.yate.ro/wiki/Call_Forker#Providing_fake_ringback_tone_while_fallback_calling_through_different_gateways
373
YateBTS / Re: Encryption with YateBTS
« on: September 12, 2014, 03:36:40 AM »
YateBTS don't implement channel encryption.
If you need it you should talk to Diana.
If you need it you should talk to Diana.
374
YateBTS / Re: GSM/MULAW Audio Codec Problem?
« on: September 04, 2014, 05:06:50 PM »
The module gsmcodec.yate is missing.
If you built yate from sources you need libgsm devel.
If you built yate from sources you need libgsm devel.
375
Yate bugs / Re: Life without UDP 5060
« on: September 01, 2014, 05:33:29 PM »
It seems there is an issue with the Contact header.
Yate sends the Contact header with local ip/port.
The second log shows the ACK to OK comes on UDP (which uses the same port as TCP, 5060).
I suspect the failure in the first log is due to the fact the remote client sends the ACK on UDP port 5061.
If you can, try to set the contact header when answering:
regexroute example:
[extra]
call.answered=50
[call.answered]
.*=;osip_Contact=sip:103@s.s.s.s:5061$(chr,59)transport=TLS
Replace your s.s.s.s with your ip.
This should work.
If you try a Yate Client with a TLS only listener it will work anyway.
Yate sends the Contact header with local ip/port.
The second log shows the ACK to OK comes on UDP (which uses the same port as TCP, 5060).
I suspect the failure in the first log is due to the fact the remote client sends the ACK on UDP port 5061.
If you can, try to set the contact header when answering:
regexroute example:
[extra]
call.answered=50
[call.answered]
.*=;osip_Contact=sip:103@s.s.s.s:5061$(chr,59)transport=TLS
Replace your s.s.s.s with your ip.
This should work.
If you try a Yate Client with a TLS only listener it will work anyway.