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 - marian

Pages: [1] 2 3 ... 25
Other Yate server issues / Re: Record a call in regexroute
« on: July 05, 2017, 01:46:45 AM »
When a target is set in regexroute processing stops, route message returns with specified target.
Lines following the one returning a target to call are ignored!

Recording a call is not an easy thing to do.

Try this:

    .*=enqueue chan.masquerade;id=${id};message=chan.record;call=wave/record//var/records/inbound_${called}_${caller}$(timestamp).slin;peer=wave/record//var/records/outbound_${called}_${caller}$(timestamp).slin

- you MUST masquerade the chan.record message: the internal channel is required in order to attach its input to record
- media directions are not correlated. Each file stores media when is generated by input
- you may search the code for other modules implementing chan.record (I think dbwave can store recordings in a database)

See also:

YateBTS / Re: My BTS doesn't transmit DTMF
« on: June 30, 2017, 12:37:20 AM »
You should post a log (message sniffer and sip included) to see what happens.

DTMFs from MS are handled.
DTMFs to MS are not handled.

Yate bugs / Re: Rmanager mutex error
« on: June 28, 2017, 07:50:27 AM »
It will be fixed, of course.
Can't say when (as soon as possible!).

Yate bugs / Re: Rmanager mutex error
« on: June 27, 2017, 12:42:06 AM »
There is, indeed, a deadlock probability between call start by fork (possible some other module also) and status handling.
It may appear if full status is requested.
If you don't need full status you may use 'status overview'

Linux / Re: "headless" Sip-Client?
« on: June 21, 2017, 01:09:26 AM »
If all you need is to route incoming calls to local audio device ...

Load alsa or oss module:

Route all calls to it:

Yate users hangout place / Re: Cannot get NIB started on ubuntu16
« on: June 08, 2017, 01:04:42 AM »
See 'Failed to bind ...' debug messages. You have another yate instance running!

See also: Missing radio band or C0 configuration. Check ybts.conf

RPDU contains a RP message (TS 100 942 Section 2.2)
Specific RP messages are described in section 7.3.
For each informational element you must pay attention at Format column in tables: TLV means Type/Length/Value. If a letter is missing it means the corresponding part is not present! (e.g. LV meand length and value fields are present, type is not present)
RP-USER-DATA IE contains a TPDU (see TS 123 040 section 9.2.2)

You may always use Wireshark: this application can show you the binary data and its meaning (it has the ability to decode RP messages)
See tapping at

YateBTS / Re: Setting Rejection Code
« on: May 25, 2017, 06:51:02 AM »
Yes. The order is:
- start yate
- connect to rmanager module using telnet
- type commands

YateBTS / Re: Setting Rejection Code
« on: May 25, 2017, 05:44:52 AM »
telnet opens a connection to specified ip and port. Someone must listen on it!
Yate binds on by default
You must start yate in order to be able to connect to it!

YateBTS / Re: Setting Rejection Code
« on: May 25, 2017, 05:00:49 AM »
I'm not sure I understand.
What do you mean by: I'm not able to telnet into it before starting the bts?

YateBTS / Re: Setting Rejection Code
« on: May 25, 2017, 12:57:54 AM »
See 'Failed to bind ....'  messages: you have another yate running!
Make sure you are running o instance only.

The commands I gave you must be typed in a telnet console.

YateBTS / Re: Setting Rejection Code
« on: May 24, 2017, 04:54:41 AM »
If you are using the command 'mbts shutdown' this only stops the mbts application.
The BTS module will detect it stopped and will restart it!

If you want to stop/start the BTS use:
ybts start
ybts stop

You can't simply hexify a text and send it to MS.
Please see ETSI TS 100 942 and ETSI TS 124 011 on RPDU/TPDU format.

0x60=96: Invalid mandatory information
0x61=97: Message type non-existent or not implemented

You may use Wireshark to decode it. It will decode your RPDU and the response
You may enable tapping in ybts.conf and send GSM layer 3 packets to a machine running Wireshark

First octet of cause IE is the length. Second octet is the cause reason (code). It may be followed by a diagnostic

Pages: [1] 2 3 ... 25