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] 4 5 ... 35
31
YateBTS / Re: flash sms in yatebts?
« on: November 12, 2018, 01:45:23 AM »
When you are sending an already encoded SMS ('rpdu') ybts module don't look at it.
It forwards the rpdu to UE.

32
YateBTS / Re: flash sms in yatebts?
« on: November 09, 2018, 12:33:42 AM »
Sorry, just figure out that what I said is not correct.
Do you want to send an emergency message?
This is not implemented.

33
YateBTS / Re: flash sms in yatebts?
« on: November 07, 2018, 12:35:07 AM »
Hex string

34
Yes, Yate just relay SDP between devices.

You can't see negotiated (used) codec: RTP is not handled by Yate.
You may take a look at SIP signaling and assume the first codec in response (1xx with media and/or 200 OK) will be the used codec.

35
YateBTS / Re: flash sms in yatebts?
« on: November 05, 2018, 12:44:40 AM »
You need to send a RP-DATA PDU containing your SMS.

External:
Send RP-DATA in SIP signalling

Internal:
You need to build a msg.execute message with the following parameters:
callto: Target. Format: ybts/IMSInnnnnnn. Example: ybts/IMSI001010000000000
rpdu: Hexified string with RP-DATA

36
Yate users hangout place / Re: JSON Parser help
« on: November 02, 2018, 04:39:25 AM »
ExpOperation* op = JsParser::parseJSON(text);
op may be a JsArray or JsObject.
Use YOBJECT macro to check it.
I think you can use the params() method of ScriptContext to access parameters.

parseJSON() method was designed to be used in javascript.
It is not easy to use in another context.
Take a look at libs/yscript/yatescript.h: API for scripting objects.

37
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: November 02, 2018, 04:20:12 AM »
Please take a look at Message class API.

38
There may be changes in choosing the preferred codec.
You may disable alaw/mulaw codecs.
If the phones are in your network you may enabled rtp/sdp forward and let the phones deal with media negotiation.

39
YateBTS / Re: TRX clock interface timed out
« on: November 02, 2018, 01:11:08 AM »
Please post a log to see what happens

40
Yate users hangout place / Re: JSON Parser help
« on: November 02, 2018, 01:10:16 AM »
JSON parser is implemented in libyatescript.
You may link your module with it.
Take a look at modules/javascript.cpp on usage.

41
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: November 02, 2018, 01:07:50 AM »
Why would you want to masquerade a message when you already have the channel in hand?
chan.masquerade will be handled by your Driver anyway.
Don't forget to put channel in message's user data.

42
Other Yate server issues / Re: Problem: one-way audio connection
« on: October 30, 2018, 04:48:17 AM »
Sorry, forget about it: missed the part the problem was solved!

43
Other Yate server issues / Re: Problem: one-way audio connection
« on: October 29, 2018, 01:21:56 AM »
Can you please dump a log with an outgoing call?
Just to compare the IPs

44
Other Yate server issues / Re: Problem: one-way audio connection
« on: October 25, 2018, 12:31:29 AM »
2018-10-20_16:58:01.025520 <yrtp:INFO> Guessed local IP '192.168.91.52' for remote '212.9.44.38'
2018-10-20_16:58:01.025980 <yrtp:INFO> Session 'yrtp/1476115015' 0x67b9d8 bound to 192.168.91.52:17442 +RTCP [0x686470]
2018-10-20_16:58:01.035580 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x5d8938 to 217.10.79.9:5060 [0x5d2a98]
------
SIP/2.0 200 OK
...
o=yate 1540047481 1540047481 IN IP4 109.41.64.217
c=IN IP4 109.41.64.217

This shows local RTP addr is different (configured or detected).
May be a NAT issue.
Can you sahre your configuration: ysipchan.conf, yrtpchan.conf, accfile.conf?
If yes you should remove private data (password, username ...)

45
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: October 24, 2018, 06:00:53 AM »
For calling destructor see response on irc channel.
chan.hangup vever terminates a call leg: it's a notification sent by a call leg that protocol (external) call was terminated.
Use call.drop message to terminate a call leg.

Pages: 1 2 [3] 4 5 ... 35