Recent Posts

Pages: [1] 2 3 ... 10
1
Yate bugs / Re: Routing Area Identification Not Set Correctly
« Last post by Ramzeth on Today at 09:01:16 AM »
Have the same issue here.

Code: [Select]
Yate 6.0.1 devel1 r6316
Built from sources https://wiki.yatebts.com/index.php/Installing with patch applied - http://yate.null.ro/mantis/view.php?id=416

Code: [Select]
Linux 4.15.0-kali3-amd64 #1 SMP Debian 4.15.17-1kali1 (2018-04-25) x86_64 GNU/Linux
2
YateBTS / yateBTS network operator name of 712712 ALWAYS - changeable? Where?
« Last post by kpz on June 18, 2018, 03:31:27 PM »
I setup yatebts NiPC, all is up and running. The only thing i cant seem to change is the Network Operator name. Even when changing the MCC and MNC in the ybts.conf file, that changes the name of the BTS that is transmitted to my phone in the "search for networks" settings menu. My BTS pops up as "320201" for a network operator, but once i register to it and bring the information up in a cell network app, The name of the network is "712712 costarica" which makes sense becuase for the 712 mcc, but no where in the code did I set that value to 712. I have NO idea where it is coming from or originating. This even happens right out of the box with the NiPC default settings. Ive tried looking through nibc.js and subcribers.conf but found nothing. Any help is appreciated.

I also cant change the name with the BTS GUI because that is not working for me yet.

Hopefully that makes sense, please dont rail me if not, ill just explain it again if needed.
Thanks
KP
3
Yate users hangout place / Re: CDRBuild - Holdtime Modification - 6.0.1
« Last post by ganapathi on June 13, 2018, 12:24:44 PM »
Sorry misunderstanding.

Due to behaviour of Hold initiation from SIP channel i assigned status as hold/unhold only. And i don't have idea to copy, it should be hard to do tht i think.

Will try to adjust on db side.

Anyway thanks . i was tried to get this done so long, had no clue earlier...
4
Yate users hangout place / Re: CDRBuild - Holdtime Modification - 6.0.1
« Last post by ganapathi on June 13, 2018, 09:05:56 AM »
Hi

As i tested and it's working fine as i excepted. But identified some more mistake hold time value not passed to both direction of  call. only one leg whether incoming,outgoing leg only available. How to copy that variable into both leg of same call like billtime.

Sniffer Output :

  param['duration'] = '37.652'
  param['billtime'] = '21.992'
  param['ringtime'] = '3.653'
  param['holdtime'] = '7.510'
  param['status'] = 'answered'
  param['out_leg.duration'] = '37.642'
  param['out_leg.billtime'] = '21.987'
  param['out_leg.ringtime'] = '3.653'
  param['out_leg.holdtime'] = '0.000'
5
Yate users hangout place / Re: CDRBuild - Holdtime Modification - 6.0.1
« Last post by ganapathi on June 13, 2018, 04:23:34 AM »
Thanks .

Will modify as you suggested.That would save some. At initial stage it was used to check some more condition and validation.

Update you the status once tested.
6
Yate users hangout place / Re: CDRBuild - Holdtime Modification - 6.0.1
« Last post by marian on June 13, 2018, 03:09:26 AM »
I think you should test it.

A suggestion:
m_unhold = Time::msecNow();
if(m_holdsec)
    m_holdsec = m_holdsec + m_unhold - m_hold;
else
    m_holdsec = m_unhold - m_hold;

may just be (simpler, you don't need an extra variable):
m_holdsec += Time::msecNow() - m_hold;

Question: m_holdsec is in seconds? if so, use Time::secNow() instead of Time::msecNow()
7
Yate users hangout place / Re: CDRBuild - Holdtime Modification - 6.0.1
« Last post by ganapathi on June 13, 2018, 02:54:21 AM »
Ooh. i forgot that scenario.

So am planning to put condition for that, Finalize operation is the correct option to identify the call is terminated in emit function.?

With that Modified the condition. As i hope it would match those necessary condition properly.
8
Yate users hangout place / Re: CDRBuild - Holdtime Modification - 6.0.1
« Last post by marian on June 13, 2018, 12:59:22 AM »
You may want to change:
if (String(operation) == YSTRING("update") && !s_cdrUpdates && String(m_status) == YSTRING("hold") && String(m_status) == YSTRING("unhold"))
to
if (String(operation) == YSTRING("update") && !s_cdrUpdates && m_status != YSTRING("hold") && m_status != YSTRING("unhold"))

I suppose you want not to return for status=hold/unhold

You may also want to handle call termination while on hold: the 'unhold' status won't be received!
9
Yate users hangout place / Re: CDRBuild - Holdtime Modification - 6.0.1
« Last post by ganapathi on June 13, 2018, 12:39:27 AM »
Hi

unable to use svn patch due to that ,Attached git patch.

I hope it's should be same as i guess.
10
Yate users hangout place / Re: CDRBuild - Holdtime Modification - 6.0.1
« Last post by marian on June 13, 2018, 12:11:45 AM »
Sorry, can't follow!
Please post a diff from svn.
You may use:
svn diff -x -p
Pages: [1] 2 3 ... 10