Recent Posts

Pages: [1] 2 3 ... 10
1
Yate bugs / Re: Life without UDP 5060
« Last post by fheynert on October 18, 2017, 05:46:17 AM »
I like to bring this topic up again :-)


I do have a separate Listener Configured for TLS with NAT,
It Works if I call in via TLS-NAT and the internal Endpoint uses UDP Only..
As soon as I use TCP or TLS on the Internal Client I do have bidirectional RTP, but the call gets disconnected after 15 sec.

So question:
Optimising th call.answer section is probably on solution.
But I do not get the advantage / disadvantage of the contact type set with the transport type or not.

I updated to release 6.0 but it is still the same .
Could someone colaborate on this?

2
Linux / Re: YateENB
« Last post by Monica Tepelus on October 17, 2017, 04:30:09 AM »
Hi Aldo,

The NIB web application was replaced with the LMI web application that has the features of the old NIB + new ones to configure the ENB and other small improvments.
You can follow:
https://wiki.yatebts.com/index.php/LabKit_Quick_Start_Guide
From here you have links for both BTS/ENB configurations.

If you have additional questions you can post them here or in the private support tracker.
3
Linux / YateENB
« Last post by Aldo T on October 14, 2017, 04:16:46 PM »
Hi Team,

I bought my Labkit LTE in your page, just I received a few days ago,

The problem there is that the YATE NIB is not more longer supported,

My question is; If you have a manual or the code to interact with this new interface,

Now I have complet my YateBTS project only the last one is fro LTE,

Please I will appreciate your help because the documentation is not in Internet page,

Best Regards,

//ALdo T

4
Other Yate server issues / How can i set up GPRS for MC60 modem?
« Last post by suresofttech on October 10, 2017, 02:55:13 AM »
Hello, I am newbie this forum.
I have Yate BTS Lab kit with 2 test phone, 10 USIM card.
I have confirmed to connect A phone and B phone.(I can call to A from B and use internet)
The Labkit has connected to internet via eth0.
But I can’t use the lab kit on the other device(no test phone) that only use data packet.
The device has MC60 modem and can’t register USIM.
Also I got the return code about “modem registration fails” on the device when I call register function using AT-command.
So I think my GPRS configration is abnormal on the lab kit.
How can I set-up GPRS on the lab kit???
Help me...plz...
5
Yate users hangout place / [ YATE 6.0 ] Parameter Assign on Another Module
« Last post by ganapathi on October 09, 2017, 07:13:24 AM »
Hi

As i need to assign one value while listening one module(chan.disconnected) and need to assign the value on another module(call.cdr) by using external module.

Will you please guys help me for the same.


Yate::Install("chan.disconnected",80);

call_cdr->params["call_direction"]='xyz';
6
Yate users hangout place / Re: yate as small pbx: context routing questions
« Last post by fheynert on October 05, 2017, 08:44:44 AM »
Thank you Very much for your explanaition...

The flexibility of yate is great, but certanly raises questions :-)

Quote
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.

I guess I understood the Prioritiy
95  regexroute.conf
100 regfile.conf

So first look for the destination in Regexroute ( Do whatever with the called number, eg. Number to [Number|Name] Translation.  eg ^200$=return;called=100 )  In this case Returns means, Exchange called number and continue Searching regexroute.conf from this point down. If no match found in regexroute continue searching regfile.conf

So what would be the preferd way to have dialing permissions ?
e.g. Phone in Kitchen, and a Phone in the public space are only allowed to dial INTERNAL and Emergency Targets?
Office Phones are allowed to reach all Targets, etc.

But I will give the section [extra]a try...


7
Yate users hangout place / Re: yate as small pbx: context routing questions
« Last post by marian 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
8
Yate users hangout place / yate as small pbx: context routing questions
« Last post by fheynert on October 04, 2017, 06:14:19 AM »
Hi All,

Im watching the YATE Project since a while now. Right now I have my first litte use case.

I am building a small PBX for home use and may have some help guiding me.

I want to stick with regexroute.conf,accfile.conf and regfile.conf

As far as I understood a context in regexroute is just a section with route objectives/permissions wich can be chained together to form calling permissions. Great

So based on the calling number in [context] I can set permission.

Code: [Select]
${sip_user-agent}^.*scanner.*$=BLACKHOLE
${sip_user-agent}^friendly-scanner$=BLACKHOLE
${sip_user-agent}^.*sipcli.*$=BLACKHOLE
${sip_user-agent}^.*pplsip.*$=BLACKHOLE


[default]
; some stuff here

[BLACKHOLE]
^.*$=echo context:$context ${type} ${username} ${sip_to} called is ${called}:${calledname} from                  ${callername}:${caller}
.*=-;error=forbidden;reason=BLACKHOLE[BLACKHOLE]

This Works Great..
according to the guide http://docs.yate.ro/wiki/Call.route#Parameters the 'context' is a parameter
according to the regfile.conf docu I can set/modify any call.route parameter to a user

so

Code: [Select]
[100]
password=100
context=INTERN

IMHO should set the required conntext for a call comming in from this user
but this does not work


Im a using Yate 5.0.0 1 r5675

Could somebody help me with this?

best regards


9
Yate users hangout place / Re: call as a registered user
« Last post by Monica Tepelus on October 04, 2017, 01:20:58 AM »
SIP doesn't work like that. Authentication is different from placing the call. You can't do this in a single step.
Basically you want to make a call, the other party rejects the call asking for authentication, you authentify, and then you place the calls. This happends in multiple SIP messages.
10
Other Yate server issues / Re: External Module Communication
« Last post by Matt R. on October 03, 2017, 12:20:51 PM »
Solved!

This is so stupid. I assumed that including a newline in fprintf would flush, but it doesn't. Adding a fflush(stdout) fixed it.

Programming.
Pages: [1] 2 3 ... 10