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.


Messages - Monica Tepelus

Pages: 1 [2] 3 4 ... 13
16
Yate based projects / Re: About mini cell network
« on: May 29, 2018, 03:34:36 AM »
Yes, the call is lost. The feature that does this is called handover (moving one call from one bts to another) but you would need a YateUCN for this to work.

17
Features requests / Re: Fix yate mailserver...
« on: May 01, 2018, 04:58:59 AM »
Thank you for pointing this out. We'll see when we have time to fix it.

18
YateBTS / Re: Yatebts only showing hni, not network name
« on: May 01, 2018, 04:43:29 AM »
Hi,

The option to set network name is only available in the private version.

19
Yate users hangout place / Re: copyparams propagation
« on: May 01, 2018, 03:44:40 AM »
Hi,

They are copied to call.cdr message, routing and call.execute. Maybe you can change your implementation and use call.cdr instead of call.answered. I think a call.cdr with operation update is emited when call is answered

20
Yate users hangout place / Re: internal audio type encoding
« on: April 02, 2018, 06:56:05 AM »
Hi,

We used to record files in one of the supported formats and then when call ended we used sox / other programs to convert audio/merge multiple files. When call ended we triggered an external script that triggered processing.

The format should be signed linear, rate 8000, but i'm not 100% sure. You should try to verify this.

22
Other Yate server issues / Re: Javascript http request
« on: March 20, 2018, 06:34:36 AM »
Hi,

You can't do the actual call from javascript because javascript is embedded in Yate, and yate doesn't have http support. What you can do is have an external php script, with a handler for a custom message. Ex: http.request. Send the message from javascript and let the php scrit do the call.

23
YateBTS / Re: System requirements?
« on: March 08, 2018, 04:10:11 AM »
Hi,

You need to configure multiple arfcns in yatebts. By default you can only have:
* Call capacity:   7 concurrent full rate call

YateBTS doesn't support half rate, so you can't increase call capacity this way. From yate's point of view 20 ivrs aren't a big number, but running multiple arfcns takes more resources and decreases coverage. In the end you'll need to experiment. Let us know how it goes.

Good luck

24
Yate users hangout place / Re: Play wave on chan.disconnected
« on: February 28, 2018, 04:34:29 AM »
Hi,

Please provide telnet log with sniffer activated.

25
YateBTS / Re: no service
« on: February 23, 2018, 02:07:23 AM »

26
YateBTS / Re: MS.IP.Base configuration
« on: February 23, 2018, 01:53:45 AM »
Hi,

This is the base ip from which ip addresses will be generated and then assigned to the Mobile stations connecting over gprs to your BTS.

27
Yate users hangout place / Re: Is Yate Community dead?
« on: February 02, 2018, 09:12:12 AM »
Hi Badhills,

Yate is allve and well.

It's true that we haven't been very vocal in the opensource area in the last period of time but we've been busy building many products based on Yate. Some of the new features and the fixes are pushed to the public version of Yate as well. This are mostly related to the Javascript interpretor that we highly recommed.

The good news is that we'll soon release Yate 6.1.

28
Other Yate server issues / Re: Routing some calls by javascript module
« on: January 03, 2018, 04:36:24 AM »
Hi,

To choose the best way you need to know the criterias for routing in js/regexroute. You can have different priorities of the call.route message. The smaller the number, the higher the priority.

You could set the javascript route first (just install the handler with priority 90). Default priority for call.route in regexroute is 100.
Route all the calls that you want from js, all those not routed (return false;  -- in code), will pass on to be routed in regexroute. If you "return true;" with/without an error, then call won't pass on to

Various combinations are possible. You can fix handling call.route/call.preroute and playing with the priorities when installing handlers.

You also need to choose the type of javascript script to use: global script/routing script. If many calls reach the script you should use a global script. The routing script allows you to route and build small ivr but it starts an instance for every call. If you just want to route, global script is more eficient.

29
The routing is done automatically in the nipc.js script. Regexroute is not involved at all. You leave registration with regexp (that is also done in the nipc script), and don't modify anything in the regexroute.

If the outbund connection is set and it's connected, then calls that can't be routed inside will automatically go to them. If you set in regexroute to route all calls outside, it's normal not to be able to route anything to the registered users.

Post an archive with all you configuration files and a yate log with sniffer and debug on as instructed in the previos post. Just a single screenshot doesn't help.

30
If the Outbound connection is up, then all calls that can't be routed inside the network (defined subscribers phone numbers - msisdns  or their short numbers) will be routed to the outbound connection.

The regexroute is wrong. You should not need to define anything in regexroute to get calls to go to the outbound connection.

Can you post a log with "sniffer on" and "debug sip level 9" from telnet?
http://docs.yate.ro/wiki/Debugging_and,_or_Investigation_of_messages

Pages: 1 [2] 3 4 ... 13