Re: [OpenSIPS-Users] CDR

2024-03-19 Thread Marcin Groszek

Look in to ACC module.

On 3/19/2024 7:39 AM, Prathibha B wrote:


How to get the Call Detail Record in Opensips?
--
Regards,
B.Prathibha

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


--
Best Regards:
Marcin Groszek
Business Phone Service
https://www.voipplus.net

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR

2024-03-19 Thread Prathibha B
How to get the Call Detail Record in Opensips?
-- 
Regards,
B.Prathibha
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR stopped writing files

2022-11-30 Thread Saint Michael
LOOKING FOR A CONSULTANT
My usual engineer Vlad is on vacation util Dec 5th,
Today I lost around $1000, of which the client only agreed to pay 50%
(they never think that they sent so much traffic), because opensips
3.1 decided to stop writing calls to the hard drive.
My question is: what may cause this and what can I do to preclude this
from happening again?

I checked the directory "/cdr" where opensips is supposed to write CDR
it remained empty.

I saved the syslog messages from opensips but there was nothing that
would indicate a problem.

Yours
Philip

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR not generated on 302 redirect

2022-03-15 Thread Ben Newlin
CDRs are generated for calls based on the dialogs. A call receiving a 302 
Redirect does not establish a dialog so there will be no CDR.

OpenSIPS will generate an accounting record for any transaction if you want it 
to. Please review the documentation of the ACC module [1].

“failed - flag which indicates if the transaction should also be accounted in 
case of failure (status>=300);”

[1] - https://opensips.org/docs/modules/3.2.x/acc.html#func_do_accounting

Ben Newlin

From: Users  on behalf of Saint Michael 

Date: Tuesday, March 15, 2022 at 10:15 AM
To: OpenSIPS users mailling list 
Subject: [OpenSIPS-Users] CDR not generated on 302 redirect
EXTERNAL EMAIL - Please use caution with links and attachments


My new business is to provide 302 Redirect services and Opensips does not 
genrate a CDR for those calls. Other type of calls do generate a record. Is 
this by design or is it a bug?
Every call that goes through Opensips should generate a record.
Any idea about what is going on?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR not generated on 302 redirect

2022-03-15 Thread David Villasmil
Look very carefully at the config. There’s probably somewhere it’s enabled.

Maybe  this
https://github.com/OpenSIPS/opensips/blob/master/examples/acc.cfg might
give you some ideas…

On Tue, 15 Mar 2022 at 14:14, Saint Michael  wrote:

> My new business is to provide 302 Redirect services and Opensips does not
> genrate a CDR for those calls. Other type of calls do generate a record. Is
> this by design or is it a bug?
> Every call that goes through Opensips should generate a record.
> Any idea about what is going on?
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 
Regards,

David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR not generated on 302 redirect

2022-03-15 Thread Alex Balashov

> On Mar 15, 2022, at 10:13 AM, Saint Michael  wrote:
> 
> Every call that goes through Opensips should generate a record. 

Is this just your opinion, or…?

-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR not generated on 302 redirect

2022-03-15 Thread Saint Michael
My new business is to provide 302 Redirect services and Opensips does not
genrate a CDR for those calls. Other type of calls do generate a record. Is
this by design or is it a bug?
Every call that goes through Opensips should generate a record.
Any idea about what is going on?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR rotation

2020-10-06 Thread Saint Michael
it works perfectly, thanks.


On Tue, Oct 6, 2020 at 6:18 AM Richard Revels  wrote:

> https://opensips.org/docs/modules/3.1.x/db_flatstore.html#mi_flat_rotate
>
> 1) move CDR files to different directory (opensips continues to write to
> them)
> 2) issue fifo command to cause opensips to write to new files
> 3) insure an accounting record is written to see that new files in
> original directory are indeed created
> 4) work with old files in different directory
>
>
>
>
>
> [image: BandwidthMaroon.png]
>
>
>
> Richard Revels  •  System Architect II
>
> 900 Main Campus Drive, Suite 100, Raleigh, NC 27606
>
>
>
> m: 919-578-3421  •  o: 919-727-4614
>
> e: rrev...@bandwidth.com
>
>
> On Fri, Oct 2, 2020 at 12:53 AM Saint Michael  wrote:
>
>> I need to close the CDR files so I can start processing them.
>>
>> I want a new file generated every 60 seconds, if there are calls.
>> is there any way to have opensips behave this way?
>>
>>>
>>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR rotation

2020-10-06 Thread Richard Revels
https://opensips.org/docs/modules/3.1.x/db_flatstore.html#mi_flat_rotate

1) move CDR files to different directory (opensips continues to write to
them)
2) issue fifo command to cause opensips to write to new files
3) insure an accounting record is written to see that new files in original
directory are indeed created
4) work with old files in different directory





[image: BandwidthMaroon.png]



Richard Revels  •  System Architect II

900 Main Campus Drive, Suite 100, Raleigh, NC 27606



m: 919-578-3421  •  o: 919-727-4614

e: rrev...@bandwidth.com


On Fri, Oct 2, 2020 at 12:53 AM Saint Michael  wrote:

> I need to close the CDR files so I can start processing them.
>
> I want a new file generated every 60 seconds, if there are calls.
> is there any way to have opensips behave this way?
>
>>
>> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR rotation

2020-10-01 Thread Saint Michael
>
> I need to close the CDR files so I can start processing them.

I want a new file generated every 60 seconds, if there are calls.
is there any way to have opensips behave this way?

>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR no longer work for permission denied

2020-06-23 Thread Saint Michael
Please ask Vlad Paiu. He fixed it. It turns out that in the new kernel
5.4.0-37-generic of Ubuntu 20.04, the fifo has a lock, so he took these
steps:
mkdir /home/opensips
chown -R opensips:opensips /home/opensips/
/etc/opensips/opensips.cfg , changed to modparam("mi_fifo", "fifo_name",
"/home/opensips/opensips_fifo")
/usr/local/etc/opensips/opensipsctlrc , added
OSIPS_FIFO="/home/opensips/opensips_fifo"

I think this should the canonical way this should work.




On Tue, Jun 23, 2020 at 4:12 AM Răzvan Crainea  wrote:

> Can you provide more information abut the environment you're running on?
> Is it debian or redhat based, could you send us the fifo file
> permissions, as well as the user OpenSIPS is running with?
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
> On 6/14/20 2:16 PM, Saint Michael wrote:
> > /usr/local/sbin/opensipsctl fifo flat_rotate
> > /usr/local//lib64/opensips/opensipsctl/opensipsctl.fifo: line 121:
> > /tmp/opensips_fifo: Permission denied
> > This happened after upgrading my kernel to 5.4.0-37-generic
> > although I cannot see the connection.
> >
> >
> >
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR no longer work for permission denied

2020-06-23 Thread Răzvan Crainea

Can you provide more information abut the environment you're running on?
Is it debian or redhat based, could you send us the fifo file 
permissions, as well as the user OpenSIPS is running with?


Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 6/14/20 2:16 PM, Saint Michael wrote:

/usr/local/sbin/opensipsctl fifo flat_rotate
/usr/local//lib64/opensips/opensipsctl/opensipsctl.fifo: line 121: 
/tmp/opensips_fifo: Permission denied

This happened after upgrading my kernel to 5.4.0-37-generic
although I cannot see the connection.




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR no longer work for permission denied

2020-06-14 Thread Saint Michael
/usr/local/sbin/opensipsctl fifo flat_rotate
/usr/local//lib64/opensips/opensipsctl/opensipsctl.fifo: line 121:
/tmp/opensips_fifo: Permission denied
This happened after upgrading my kernel to 5.4.0-37-generic
although I cannot see the connection.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR capturing not working

2020-04-29 Thread Bogdan-Andrei Iancu

Hi there,

What is this cdr_worker.sh file you are talking about ??

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com

On 4/29/20 6:17 AM, Saint Michael wrote:
I checked the database and I missed the CDR for many calls.  Later I 
found them sitting in files in /var/log/opensips

I run it manually cdr_worker.sh and got this error ./cdr_worker.sh
lockfile: Sorry, giving up on "/var/run/opensips_cdr_worker.lock"which 
means is not firing because the lock is being held, but there is no 
traffic. I stopped opensips and still the same error , so the script 
is not working as it should. The locking mechanism is stuck. I 
restarted opensips, placed another call, and odbc did not get 
executed, so recycling opensips does not free the lock.

Any idea how can I get my CDR inserted 100% for sure into my database?



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR capturing not working

2020-04-28 Thread Saint Michael
I checked the database and I missed the CDR for many calls.  Later I found
them sitting in files in /var/log/opensips
I run it manually cdr_worker.sh and got this error ./cdr_worker.sh
lockfile: Sorry, giving up on "/var/run/opensips_cdr_worker.lock"which
means is not firing because the lock is being held, but there is no
traffic. I stopped opensips and still the same error , so the script is not
working as it should. The locking mechanism is stuck. I restarted opensips,
placed another call, and odbc did not get executed, so recycling opensips
does not free the lock.
Any idea how can I get my CDR inserted 100% for sure into my database?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR is not generated in rabbitmq server while call detected as fraud

2019-11-17 Thread Darpan Patel
I have subscribed events like E_ACC_CDR ,E_ACC_EVENT , E_ACC_MISSED_EVENT
in startup_route to connect rabbitmq server for sending CDR related
information of calls and also used event_routes E_FRD_WARNING and
E_FRD_CRITICAL to detect fraud calls. while call detected as a fraud  after
hang up the same call's cdr is not generated in queue of rabbitmq server
(ISSUE FOUND IN OPENSIPS 2.4 AND OPENSIPS 3.0)

Thanks & Regards,
Darpan Patel
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR in Flat files

2017-06-08 Thread Kirill Galinurov
Yes i change my rsyslog.conf and now. Everything looks OK
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR in Flat files

2017-06-06 Thread Michele Pinassi
Did you check your rsyslog (/etc/rsyslogd.conf) configuration ?

Michele


On 05/06/2017 10:52, Kirill Galinurov wrote:
> Hi ALL.
>  I try to store cdr in flat files.
> My config is
> loadmodule "acc.so"
> modparam("acc", "detect_direction", 0)
> modparam("acc", "extra_fields", "log: src_ip; dst_ip")
> modparam("acc", "leg_fields", "log: caller; callee")
> modparam("acc", "log_facility", "LOG_DAEMON")
>
>if(is_method("INVITE"))  {
>if (check_address("0","$si","$sp","any")){
>force_send_socket(udp:*Servizio Antispam attenzione!: i
> link numerici sono spesso insicuri!:* 172.20.20.30:5060
> );
>setflag(CALL_AST);
>create_dialog("B");
>do_accounting("log", "cdr");
> }
>
> in cosole debug I see
> ACC: call ended:
> created=1496654777;call_start_time=1496654780;duration=7;ms_duration=7393;setuptime=3;method=I
> NVITE;from_tag=SDipn2901-1544324631353641441C2115;to_tag=as51263d7c;call_id=SDipn2901-3f6bad0e2bf09ec16aeaedd37abb0661-v300g00030;code=
> 200;reason=OK;src_ip=;dst_ip=;caller=;callee=
>  
> But no records in log file
>

-- 
Michele Pinassi
Responsabile Telefonia di Ateneo
Servizio Reti, Sistemi e Sicurezza Informatica - Università degli Studi di Siena
tel: 0577.(23)5000 - central...@unisi.it

Per trovare una soluzione rapida ai tuoi problemi tecnici consulta le FAQ di 
Ateneo, http://www.faq.unisi.it 



signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR in Flat files

2017-06-05 Thread Kirill Galinurov
Hi ALL.
 I try to store cdr in flat files.
My config is
loadmodule "acc.so"
modparam("acc", "detect_direction", 0)
modparam("acc", "extra_fields", "log: src_ip; dst_ip")
modparam("acc", "leg_fields", "log: caller; callee")
modparam("acc", "log_facility", "LOG_DAEMON")

   if(is_method("INVITE"))  {
   if (check_address("0","$si","$sp","any")){
   force_send_socket(udp:172.20.20.30:5060);
   setflag(CALL_AST);
   create_dialog("B");
   do_accounting("log", "cdr");
}

in cosole debug I see
ACC: call ended:
created=1496654777;call_start_time=1496654780;duration=7;ms_duration=7393;setuptime=3;method=I
NVITE;from_tag=SDipn2901-1544324631353641441C2115;to_tag=as51263d7c;call_id=SDipn2901-3f6bad0e2bf09ec16aeaedd37abb0661-v300g00030;code=
200;reason=OK;src_ip=;dst_ip=;caller=;callee=

But no records in log file
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR when terminating dialog

2016-02-17 Thread Dragomir Haralambiev
Hi,

Thanks for your replay.

When internet connection is broken with UA, is appear follow message:

INFO:dialog:reply_from_caller: terminating dialog ( due to timeout ) with
callid = [698777468

Openips send BYE but not make CDR. I try with modparam("acc",
"failed_transaction_flag", "FAIL_TRANS_FLAG") but CDR is not generate.

Any idea?


2016-02-17 16:37 GMT+02:00 Jim DeVito :

> That looks like you would receive a response indication a timeout. (408
> maybe?) If so setting this flag on the transaction should do it.
> http://www.opensips.org/html/docs/modules/2.2.x/acc#id294062
>
> ---
> Jim DeVito
>
>
>
> On 2016-02-17 05:27, Dragomir Haralambiev wrote:
>
>> Hello,
>>
>> How to setup  Opensips 2.2 to make CDR when dialog is terminate by
>> timeout.
>>
>> On log I see follow message:
>> INFO:dialog:reply_from_caller: terminating dialog  ( due to timeout )
>> with callid=
>>
>> Best regards,
>> Dragomir
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR when terminating dialog

2016-02-17 Thread Jim DeVito
That looks like you would receive a response indication a timeout. (408 
maybe?) If so setting this flag on the transaction should do it. 
http://www.opensips.org/html/docs/modules/2.2.x/acc#id294062


---
Jim DeVito


On 2016-02-17 05:27, Dragomir Haralambiev wrote:

Hello,

How to setup  Opensips 2.2 to make CDR when dialog is terminate by
timeout.

On log I see follow message:
INFO:dialog:reply_from_caller: terminating dialog  ( due to timeout )
with callid=

Best regards,
Dragomir
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR when terminating dialog

2016-02-17 Thread Dragomir Haralambiev
Hello,

How to setup  Opensips 2.2 to make CDR when dialog is terminate by timeout.

On log I see follow message:
INFO:dialog:reply_from_caller: terminating dialog  ( due to timeout ) with
callid=

Best regards,
Dragomir
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR search slow in CDRTool

2015-12-01 Thread Tomas Andersen
Hi again,

Thank you for the information.

Yes, the delay is happening between the select rpid queries. So I see the 
request/responses from open sips DB immediately and then 10 seconds “void”, 
before next query.
The search resolves in two different flows and the timeout is 10 s for both of 
them. I see ‘outgoing’ flow and 'on-net-diverted-off-net’ flow.
php5-geoip seems to lookup the correct country when testing a lookup of an ip 
address with a simple php script.

I tried to add some debug info in the rating class, but now I suddenly got 
another problem with CDRTool starting to get connection reset to the rating 
engine. Seems like the ratingEngine stops when trying to do a search.
I am investigating this atm.

Regards,
Tomas


From: 
mailto:users-boun...@lists.opensips.org>> on 
behalf of Tijmen de Mes
Reply-To: OpenSIPS users mailling list
Date: Monday 30 November 2015 at 16:19
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] CDR search slow in CDRTool

Hi,

As for the usability questions, from trusted peers it matches the ip to a 
reseller so this can be billed. The subscriber table is used to find the RPID 
from the local caller and get quotas.

As for the delay, to me it sounds like a timeout of some sort if it is 10s each 
time. So you see the delay after this query? Can you tell me what it shows for 
‘flow', and does the delay change based on the flow?

Also does php5-geoip work?

Best regards,

Tijmen de Mes
—
AG Projects

On 30 nov. 2015, at 13:43, Tomas Andersen 
mailto:tomas.ander...@ipco.no>> wrote:

Sorry for “spamming” the list, but the sql query request/response itself to the 
subscriber list is fast.
So as you say there must be some more logic before the next caller is checked 
that takes time.
CDRTool “waits” 10 seconds between each query.

Regards,
Tomas


From: 
mailto:users-boun...@lists.opensips.org>> on 
behalf of Tomas Andersen
Reply-To: OpenSIPS users mailling list
Date: Monday 30 November 2015 at 13:31
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] CDR search slow in CDRTool

Hi.

Thank you for responding. I have now tried to add the parameter you specified 
in my global.inc file. I have also added “skipNormalize” => 1.
The search does still use forever, and according to my RadiusAcct table all 
CDRs are already normalized, as the value is set to 1. I don’t see why it still 
should use that much time..
as they already are normalized..?

By checking wireshark, the calls to OpenSIPS db still searches for rpid in the 
subscriber table and each call takes 10 minutes.
The latest search i did now resulted in 8 CDRs and the search took 8x10seconds 
= 1m 20s.

My concern is that CDRTool relies on a strict way to use OpenSIPS, as it need 
certain tables to be filled out?

We have made another approach to OpenSIPS and are using the grp table for 
listing our subscribers (not the subscriber table).
We are also using dr_gateways to list our external Gateways (e.g other SIP 
servers or external GWs).

We do not use the trusted_peers or subscriber tables which I see are queried 
from cdrtool.

My hope was to use CDRTool to rate calls differently if the call is placed 
internally (userloc-userloc) or from an internal user to an external user (and 
then lookup destinations with country code).

Do you see any limitations based on how we use OpenSIPS?

I really appreciate if you could assist me in the question.

Regards,
Tomas Andersen

From: 
mailto:users-boun...@lists.opensips.org>> on 
behalf of Tijmen de Mes
Reply-To: OpenSIPS users mailling list
Date: Monday 30 November 2015 at 13:01
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] CDR search slow in CDRTool

Hi Tomas,

That query should not take 10 seconds. Here it completes in 0.02s according to 
mysql. The query is used to determine the flow of the calls. After the query is 
executed in CDRTool, more logic follows. It can easily be that the delay is in 
there.

If web normalizing is enabled and the call is not normalized,  it will also try 
to normalize and rate the calls while searching. This can be disabled if you 
don’t need/want it. Perhaps you can disable this to check if this causes the 
delay.

To disable it add to the opensips datasource in global.inc:  
"skipNormalizeOnPageLoad" => 1


Best regards,

Tijmen de Mes
—
AG Projects


On 30 nov. 2015, at 10:26, Tomas Andersen 
mailto:tomas.ander...@ipco.no>> wrote:

Hi again.

I have set up wireshark to check why the CDR rating engine uses so much time.

The following SQL queries are run from CDRTool to my OpenSIPS server:
select * from domain;
select * from trusted_peers;
Select rpid from subscriber where username = ‘+47’ and domain = 
‘example.sip.com<http://example.sip.com/>’

(with username and domain scrambled here)

The rpid select statement is run for each caller in the search period. What is 
strange is that these selects are only run each 10 second, and 

Re: [OpenSIPS-Users] CDR search slow in CDRTool

2015-11-30 Thread Tijmen de Mes
Hi,

As for the usability questions, from trusted peers it matches the ip to a 
reseller so this can be billed. The subscriber table is used to find the RPID 
from the local caller and get quotas.

As for the delay, to me it sounds like a timeout of some sort if it is 10s each 
time. So you see the delay after this query? Can you tell me what it shows for 
‘flow', and does the delay change based on the flow?

Also does php5-geoip work?

Best regards,

Tijmen de Mes
—
AG Projects

> On 30 nov. 2015, at 13:43, Tomas Andersen  wrote:
> 
> Sorry for “spamming” the list, but the sql query request/response itself to 
> the subscriber list is fast.
> So as you say there must be some more logic before the next caller is checked 
> that takes time.
> CDRTool “waits” 10 seconds between each query.
> 
> Regards,
> Tomas
> 
> 
> From:  <mailto:users-boun...@lists.opensips.org>> on behalf of Tomas Andersen
> Reply-To: OpenSIPS users mailling list
> Date: Monday 30 November 2015 at 13:31
> To: OpenSIPS users mailling list
> Subject: Re: [OpenSIPS-Users] CDR search slow in CDRTool
> 
> Hi.
> 
> Thank you for responding. I have now tried to add the parameter you specified 
> in my global.inc file. I have also added “skipNormalize” => 1.
> The search does still use forever, and according to my RadiusAcct table all 
> CDRs are already normalized, as the value is set to 1. I don’t see why it 
> still should use that much time..
> as they already are normalized..?
> 
> By checking wireshark, the calls to OpenSIPS db still searches for rpid in 
> the subscriber table and each call takes 10 minutes.
> The latest search i did now resulted in 8 CDRs and the search took 
> 8x10seconds = 1m 20s.
> 
> My concern is that CDRTool relies on a strict way to use OpenSIPS, as it need 
> certain tables to be filled out?
> 
> We have made another approach to OpenSIPS and are using the grp table for 
> listing our subscribers (not the subscriber table).
> We are also using dr_gateways to list our external Gateways (e.g other SIP 
> servers or external GWs).
> 
> We do not use the trusted_peers or subscriber tables which I see are queried 
> from cdrtool.
> 
> My hope was to use CDRTool to rate calls differently if the call is placed 
> internally (userloc-userloc) or from an internal user to an external user 
> (and then lookup destinations with country code).
> 
> Do you see any limitations based on how we use OpenSIPS?
> 
> I really appreciate if you could assist me in the question.
> 
> Regards,
> Tomas Andersen
> 
> From:  <mailto:users-boun...@lists.opensips.org>> on behalf of Tijmen de Mes
> Reply-To: OpenSIPS users mailling list
> Date: Monday 30 November 2015 at 13:01
> To: OpenSIPS users mailling list
> Subject: Re: [OpenSIPS-Users] CDR search slow in CDRTool
> 
> Hi Tomas,
> 
> That query should not take 10 seconds. Here it completes in 0.02s according 
> to mysql. The query is used to determine the flow of the calls. After the 
> query is executed in CDRTool, more logic follows. It can easily be that the 
> delay is in there.
> 
> If web normalizing is enabled and the call is not normalized,  it will also 
> try to normalize and rate the calls while searching. This can be disabled if 
> you don’t need/want it. Perhaps you can disable this to check if this causes 
> the delay.
> 
> To disable it add to the opensips datasource in global.inc:  
> "skipNormalizeOnPageLoad" => 1
> 
> 
> Best regards,
> 
> Tijmen de Mes
> —
> AG Projects
> 
> 
>> On 30 nov. 2015, at 10:26, Tomas Andersen > <mailto:tomas.ander...@ipco.no>> wrote:
>> 
>> Hi again.
>> 
>> I have set up wireshark to check why the CDR rating engine uses so much time.
>> 
>> The following SQL queries are run from CDRTool to my OpenSIPS server:
>> select * from domain;
>> select * from trusted_peers;
>> Select rpid from subscriber where username = ‘+47’ and domain = 
>> ‘example.sip.com <http://example.sip.com/>’
>> 
>> (with username and domain scrambled here)
>> 
>> The rpid select statement is run for each caller in the search period. What 
>> is strange is that these selects are only run each 10 second, and if I am 
>> searching
>> Within a period of time and there has been 7 different callers, it will take 
>> 70 seconds. After this the GUI is “released” and updated with the maching 
>> CDR list.
>> 
>> My subscriber table in open sips is empty. Why does this take so long?
>> 
>> Regards,
>> Tomas Andersen
>> 
>> 
>> From: Tomas Andersen
>> Date: Friday 27 November 2015 at 09:10
>> 

Re: [OpenSIPS-Users] CDR search slow in CDRTool

2015-11-30 Thread Tomas Andersen
Sorry for “spamming” the list, but the sql query request/response itself to the 
subscriber list is fast.
So as you say there must be some more logic before the next caller is checked 
that takes time.
CDRTool “waits” 10 seconds between each query.

Regards,
Tomas


From: 
mailto:users-boun...@lists.opensips.org>> on 
behalf of Tomas Andersen
Reply-To: OpenSIPS users mailling list
Date: Monday 30 November 2015 at 13:31
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] CDR search slow in CDRTool

Hi.

Thank you for responding. I have now tried to add the parameter you specified 
in my global.inc file. I have also added “skipNormalize” => 1.
The search does still use forever, and according to my RadiusAcct table all 
CDRs are already normalized, as the value is set to 1. I don’t see why it still 
should use that much time..
as they already are normalized..?

By checking wireshark, the calls to OpenSIPS db still searches for rpid in the 
subscriber table and each call takes 10 minutes.
The latest search i did now resulted in 8 CDRs and the search took 8x10seconds 
= 1m 20s.

My concern is that CDRTool relies on a strict way to use OpenSIPS, as it need 
certain tables to be filled out?

We have made another approach to OpenSIPS and are using the grp table for 
listing our subscribers (not the subscriber table).
We are also using dr_gateways to list our external Gateways (e.g other SIP 
servers or external GWs).

We do not use the trusted_peers or subscriber tables which I see are queried 
from cdrtool.

My hope was to use CDRTool to rate calls differently if the call is placed 
internally (userloc-userloc) or from an internal user to an external user (and 
then lookup destinations with country code).

Do you see any limitations based on how we use OpenSIPS?

I really appreciate if you could assist me in the question.

Regards,
Tomas Andersen

From: 
mailto:users-boun...@lists.opensips.org>> on 
behalf of Tijmen de Mes
Reply-To: OpenSIPS users mailling list
Date: Monday 30 November 2015 at 13:01
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] CDR search slow in CDRTool

Hi Tomas,

That query should not take 10 seconds. Here it completes in 0.02s according to 
mysql. The query is used to determine the flow of the calls. After the query is 
executed in CDRTool, more logic follows. It can easily be that the delay is in 
there.

If web normalizing is enabled and the call is not normalized,  it will also try 
to normalize and rate the calls while searching. This can be disabled if you 
don’t need/want it. Perhaps you can disable this to check if this causes the 
delay.

To disable it add to the opensips datasource in global.inc:  
"skipNormalizeOnPageLoad" => 1


Best regards,

Tijmen de Mes
—
AG Projects


On 30 nov. 2015, at 10:26, Tomas Andersen 
mailto:tomas.ander...@ipco.no>> wrote:

Hi again.

I have set up wireshark to check why the CDR rating engine uses so much time.

The following SQL queries are run from CDRTool to my OpenSIPS server:
select * from domain;
select * from trusted_peers;
Select rpid from subscriber where username = ‘+47’ and domain = 
‘example.sip.com<http://example.sip.com>’

(with username and domain scrambled here)

The rpid select statement is run for each caller in the search period. What is 
strange is that these selects are only run each 10 second, and if I am searching
Within a period of time and there has been 7 different callers, it will take 70 
seconds. After this the GUI is “released” and updated with the maching CDR list.

My subscriber table in open sips is empty. Why does this take so long?

Regards,
Tomas Andersen


From: Tomas Andersen
Date: Friday 27 November 2015 at 09:10
To: "users@lists.opensips.org<mailto:users@lists.opensips.org>"
Subject: CDR search slow in CDRTool

Hi

I have set up CDRTool to read CDRs from my radius database for OpenSIP calls. I 
am successfully rating calls, but everytime I search for CDR records using the
CDRTool GUI it takes 1-3 minutes before the search result window is shown.

If there are no matching records the result window is shown immediately. Does 
anyone else have any experience with this? I suspect that there might be a 
database lock,
Database connection pool problems or just some configuration error somewhere.

In my browser I get the following in my developer console / network (note the 
huge duration for the HTTP POST):

200 POST callsearch.pthmlhtml105.41 kb150212 ms
200 GET date picker.csscss9.96 kb14 ms

Followed by several lines of
304 GETs


When checking with Wireshark I notice that after the HTTP POST to callsearch, I 
get several TCP Keep-Alive messages as the server is slow..
After 2m 38 seconds everything is suddenly released and some HTTP GETs make the 
page to update.

I see nothing in syslog (from cdrtool) but some mysql connection statements.. 
No lock/unlock or similar statements..

I appreciate if anyone could enli

Re: [OpenSIPS-Users] CDR search slow in CDRTool

2015-11-30 Thread Tomas Andersen
Hi.

Thank you for responding. I have now tried to add the parameter you specified 
in my global.inc file. I have also added “skipNormalize” => 1.
The search does still use forever, and according to my RadiusAcct table all 
CDRs are already normalized, as the value is set to 1. I don’t see why it still 
should use that much time..
as they already are normalized..?

By checking wireshark, the calls to OpenSIPS db still searches for rpid in the 
subscriber table and each call takes 10 minutes.
The latest search i did now resulted in 8 CDRs and the search took 8x10seconds 
= 1m 20s.

My concern is that CDRTool relies on a strict way to use OpenSIPS, as it need 
certain tables to be filled out?

We have made another approach to OpenSIPS and are using the grp table for 
listing our subscribers (not the subscriber table).
We are also using dr_gateways to list our external Gateways (e.g other SIP 
servers or external GWs).

We do not use the trusted_peers or subscriber tables which I see are queried 
from cdrtool.

My hope was to use CDRTool to rate calls differently if the call is placed 
internally (userloc-userloc) or from an internal user to an external user (and 
then lookup destinations with country code).

Do you see any limitations based on how we use OpenSIPS?

I really appreciate if you could assist me in the question.

Regards,
Tomas Andersen

From: 
mailto:users-boun...@lists.opensips.org>> on 
behalf of Tijmen de Mes
Reply-To: OpenSIPS users mailling list
Date: Monday 30 November 2015 at 13:01
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] CDR search slow in CDRTool

Hi Tomas,

That query should not take 10 seconds. Here it completes in 0.02s according to 
mysql. The query is used to determine the flow of the calls. After the query is 
executed in CDRTool, more logic follows. It can easily be that the delay is in 
there.

If web normalizing is enabled and the call is not normalized,  it will also try 
to normalize and rate the calls while searching. This can be disabled if you 
don’t need/want it. Perhaps you can disable this to check if this causes the 
delay.

To disable it add to the opensips datasource in global.inc:  
"skipNormalizeOnPageLoad" => 1


Best regards,

Tijmen de Mes
—
AG Projects


On 30 nov. 2015, at 10:26, Tomas Andersen 
mailto:tomas.ander...@ipco.no>> wrote:

Hi again.

I have set up wireshark to check why the CDR rating engine uses so much time.

The following SQL queries are run from CDRTool to my OpenSIPS server:
select * from domain;
select * from trusted_peers;
Select rpid from subscriber where username = ‘+47’ and domain = 
‘example.sip.com<http://example.sip.com>’

(with username and domain scrambled here)

The rpid select statement is run for each caller in the search period. What is 
strange is that these selects are only run each 10 second, and if I am searching
Within a period of time and there has been 7 different callers, it will take 70 
seconds. After this the GUI is “released” and updated with the maching CDR list.

My subscriber table in open sips is empty. Why does this take so long?

Regards,
Tomas Andersen


From: Tomas Andersen
Date: Friday 27 November 2015 at 09:10
To: "users@lists.opensips.org<mailto:users@lists.opensips.org>"
Subject: CDR search slow in CDRTool

Hi

I have set up CDRTool to read CDRs from my radius database for OpenSIP calls. I 
am successfully rating calls, but everytime I search for CDR records using the
CDRTool GUI it takes 1-3 minutes before the search result window is shown.

If there are no matching records the result window is shown immediately. Does 
anyone else have any experience with this? I suspect that there might be a 
database lock,
Database connection pool problems or just some configuration error somewhere.

In my browser I get the following in my developer console / network (note the 
huge duration for the HTTP POST):

200 POST callsearch.pthmlhtml105.41 kb150212 ms
200 GET date picker.csscss9.96 kb14 ms

Followed by several lines of
304 GETs


When checking with Wireshark I notice that after the HTTP POST to callsearch, I 
get several TCP Keep-Alive messages as the server is slow..
After 2m 38 seconds everything is suddenly released and some HTTP GETs make the 
page to update.

I see nothing in syslog (from cdrtool) but some mysql connection statements.. 
No lock/unlock or similar statements..

I appreciate if anyone could enlighten me on this subject.


Best Regards,
Tomas Andersen

___
Users mailing list
Users@lists.opensips.org<mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR search slow in CDRTool

2015-11-30 Thread Tijmen de Mes
Hi Tomas,

That query should not take 10 seconds. Here it completes in 0.02s according to 
mysql. The query is used to determine the flow of the calls. After the query is 
executed in CDRTool, more logic follows. It can easily be that the delay is in 
there.

If web normalizing is enabled and the call is not normalized,  it will also try 
to normalize and rate the calls while searching. This can be disabled if you 
don’t need/want it. Perhaps you can disable this to check if this causes the 
delay.

To disable it add to the opensips datasource in global.inc:  
"skipNormalizeOnPageLoad" => 1


Best regards,

Tijmen de Mes
—
AG Projects


> On 30 nov. 2015, at 10:26, Tomas Andersen  wrote:
> 
> Hi again.
> 
> I have set up wireshark to check why the CDR rating engine uses so much time.
> 
> The following SQL queries are run from CDRTool to my OpenSIPS server:
> select * from domain;
> select * from trusted_peers;
> Select rpid from subscriber where username = ‘+47’ and domain = 
> ‘example.sip.com’
> 
> (with username and domain scrambled here)
> 
> The rpid select statement is run for each caller in the search period. What 
> is strange is that these selects are only run each 10 second, and if I am 
> searching
> Within a period of time and there has been 7 different callers, it will take 
> 70 seconds. After this the GUI is “released” and updated with the maching CDR 
> list.
> 
> My subscriber table in open sips is empty. Why does this take so long?
> 
> Regards,
> Tomas Andersen
> 
> 
> From: Tomas Andersen
> Date: Friday 27 November 2015 at 09:10
> To: "users@lists.opensips.org "
> Subject: CDR search slow in CDRTool
> 
> Hi
> 
> I have set up CDRTool to read CDRs from my radius database for OpenSIP calls. 
> I am successfully rating calls, but everytime I search for CDR records using 
> the
> CDRTool GUI it takes 1-3 minutes before the search result window is shown.
> 
> If there are no matching records the result window is shown immediately. Does 
> anyone else have any experience with this? I suspect that there might be a 
> database lock,
> Database connection pool problems or just some configuration error somewhere.
> 
> In my browser I get the following in my developer console / network (note the 
> huge duration for the HTTP POST):
> 
> 200 POST callsearch.pthml
> html105.41 kb
> 150212 ms
> 200 GET date picker.css
> css9.96 kb
> 14 ms
> 
> Followed by several lines of
> 304 GETs
> 
> 
> When checking with Wireshark I notice that after the HTTP POST to callsearch, 
> I get several TCP Keep-Alive messages as the server is slow..
> After 2m 38 seconds everything is suddenly released and some HTTP GETs make 
> the page to update.
> 
> I see nothing in syslog (from cdrtool) but some mysql connection statements.. 
> No lock/unlock or similar statements..
> 
> I appreciate if anyone could enlighten me on this subject.
> 
> 
> Best Regards,
> Tomas Andersen
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR search slow in CDRTool

2015-11-30 Thread Tomas Andersen
Hi again.

I have set up wireshark to check why the CDR rating engine uses so much time.

The following SQL queries are run from CDRTool to my OpenSIPS server:
select * from domain;
select * from trusted_peers;
Select rpid from subscriber where username = ‘+47’ and domain = 
‘example.sip.com’

(with username and domain scrambled here)

The rpid select statement is run for each caller in the search period. What is 
strange is that these selects are only run each 10 second, and if I am searching
Within a period of time and there has been 7 different callers, it will take 70 
seconds. After this the GUI is “released” and updated with the maching CDR list.

My subscriber table in open sips is empty. Why does this take so long?

Regards,
Tomas Andersen


From: Tomas Andersen
Date: Friday 27 November 2015 at 09:10
To: "users@lists.opensips.org"
Subject: CDR search slow in CDRTool

Hi

I have set up CDRTool to read CDRs from my radius database for OpenSIP calls. I 
am successfully rating calls, but everytime I search for CDR records using the
CDRTool GUI it takes 1-3 minutes before the search result window is shown.

If there are no matching records the result window is shown immediately. Does 
anyone else have any experience with this? I suspect that there might be a 
database lock,
Database connection pool problems or just some configuration error somewhere.

In my browser I get the following in my developer console / network (note the 
huge duration for the HTTP POST):

200 POST callsearch.pthml html105.41 kb 150212 ms
200 GET date picker.css css9.96 kb 14 ms

Followed by several lines of
304 GETs


When checking with Wireshark I notice that after the HTTP POST to callsearch, I 
get several TCP Keep-Alive messages as the server is slow..
After 2m 38 seconds everything is suddenly released and some HTTP GETs make the 
page to update.

I see nothing in syslog (from cdrtool) but some mysql connection statements.. 
No lock/unlock or similar statements..

I appreciate if anyone could enlighten me on this subject.


Best Regards,
Tomas Andersen

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR search slow in CDRTool

2015-11-27 Thread Tomas Andersen
Hi

I have set up CDRTool to read CDRs from my radius database for OpenSIP calls. I 
am successfully rating calls, but everytime I search for CDR records using the
CDRTool GUI it takes 1-3 minutes before the search result window is shown.

If there are no matching records the result window is shown immediately. Does 
anyone else have any experience with this? I suspect that there might be a 
database lock,
Database connection pool problems or just some configuration error somewhere.

In my browser I get the following in my developer console / network (note the 
huge duration for the HTTP POST):

200 POST callsearch.pthml  html 105.41 kb 150212 ms
200 GET date picker.css  css 9.96 kb 14 ms

Followed by several lines of
304 GETs


When checking with Wireshark I notice that after the HTTP POST to callsearch, I 
get several TCP Keep-Alive messages as the server is slow..
After 2m 38 seconds everything is suddenly released and some HTTP GETs make the 
page to update.

I see nothing in syslog (from cdrtool) but some mysql connection statements.. 
No lock/unlock or similar statements..

I appreciate if anyone could enlighten me on this subject.


Best Regards,
Tomas Andersen

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR in flat file

2014-03-06 Thread Răzvan Crainea

Hi, Gary!

The configuration file looks ok. Can you check if the /var/log/acc 
directory exists? Do you see any errors in the logs?


Best regards,

Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 03/05/2014 11:40 PM, Gary Nyquist wrote:

Hi,

I am trying to configure the OpenSIPS v.1.10 to make it write the CDRs
to flat files.

But no luck yet.

The "opensips.cfg" looks like this:

...

loadmodule "dialog.so"

modparam("dialog", "dlg_match_mode", 1)

loadmodule "acc.so"

modparam("acc", "detect_direction", 1)

modparam("acc", "failed_transaction_flag", "ACC_FAILED")

modparam("acc", "db_url", "flatstore:/var/log/acc")

modparam("acc", "log_flag", "LOG_FLAG")

modparam("acc", "log_facility", "LOG_LOCAL0")

modparam("acc", "cdr_flag", "CDR_FLAG")

modparam("acc", "db_flag", "DB_FLAG")

loadmodule "db_flatstore.so"

modparam("db_flatstore", "flush", 0)

modparam("db_flatstore", "suffix", "$time(%H)")

...

route[relay]{

 if (is_method("INVITE")){

 rewritehostport("54.84.239.100:5080");

 create_dialog();

 setflag(LOG_FLAG);

 setflag(DB_FLAG);

 setflag(CDR_FLAG);

 if (!t_relay()) {

send_reply("500","Internal Error");

 }

 }

}

...

Am I missing something or doing something wrong?

Thanks in advance

Gary



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR in flat file

2014-03-05 Thread Gary Nyquist
Hi,
I am trying to configure the OpenSIPS v.1.10 to make it write the CDRs to flat 
files.
But no luck yet.
The "opensips.cfg" looks like this:
...
loadmodule "dialog.so"
modparam("dialog", "dlg_match_mode", 1)
loadmodule "acc.so"
modparam("acc", "detect_direction", 1)
modparam("acc", "failed_transaction_flag", "ACC_FAILED")
modparam("acc", "db_url", "flatstore:/var/log/acc")
modparam("acc", "log_flag", "LOG_FLAG")
modparam("acc", "log_facility", "LOG_LOCAL0")
modparam("acc", "cdr_flag", "CDR_FLAG")
modparam("acc", "db_flag", "DB_FLAG")
loadmodule "db_flatstore.so"
modparam("db_flatstore", "flush", 0)
modparam("db_flatstore", "suffix", "$time(%H)")
...
route[relay]{
 if (is_method("INVITE")){
 rewritehostport("54.84.239.100:5080");
 create_dialog();
 setflag(LOG_FLAG); 
 setflag(DB_FLAG); 
 setflag(CDR_FLAG); 
 if (!t_relay()) {
 send_reply("500","Internal Error");
 }
 }
}
...
Am I missing something or doing something wrong?
Thanks in advance
Gary
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] cdr in opensips 1.8

2012-08-28 Thread Engineer voip
Hello All,

I configured OpenSIPS 1.8 to have  cdr and after making some calls between
two softphones I geted the cdr

 but now I don't get it without any  modification, and in cdrs table i have
cdr_id = 0 !!

someone have an idea please?

thank you
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-25 Thread Engineer voip
Hi,

I had a problem with the script "opensips_cdrs.mysql" as cdr_id fields
is already exists in the table acc, so I commented the line that adds
cdr_id to the table acc in the script generate.mysql
and I configured the acc module in opensips.cfg as follows:

loadmodule "acc.so"
modparam("acc", "early_media", 0)
modparam("acc", "report_cancels", 0)
modparam("acc", "detect_direction", 0)
modparam("acc", "failed_transaction_flag", 24)
modparam("acc", "db_flag", 2)
modparam("acc", "db_missed_flag", 2)
modparam("acc", "db_table_missed_calls", "missed_calls")
modparam("acc", "cdr_flag",1)
modparam("acc", "db_table_acc", "acc")
modparam("acc", "db_url","mysql://opensips:opensipsrw@localhost/opensips")

Also i changed this ligne "mysql -h $HOSTNAME -u $USER -p$PASS -e
"call opensips_cdrs_1.6(); " $DATABASE"
 in generate_cdrs.mysql  to "mysql -h $HOSTNAME -u $USER -p$PASS -e
"call opensips_cdrs(); " $DATABASE"

Thank you All




2012/8/25, Ali Pey :
> What was the problem? How did you fix it?
>
> It's good to mention your problems and solutions for people that might
> experience the same problem in the future.
>
> Regards,
> Ali Pey
>
> On Fri, Aug 24, 2012 at 7:10 PM, Engineer voip  wrote:
>
>> Hello,
>> It's good, i can to get CDRs and Dialog information using OCP.
>> Thank you to all those who helped me.
>>
>> Best Regards
>>
>> 2012/8/24, Binan AL Halabi :
>> > Hi,
>> >
>> > restart DB
>> > restart opensips
>> > reload apache (service httpd reload)
>> >
>> > //Binan
>> >
>> > --- On Fri, 8/24/12, Ali Pey  wrote:
>> >
>> > From: Ali Pey 
>> > Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
>> > To: "Engineer voip" 
>> > Cc: "OpenSIPS users mailling list" 
>> > Date: Friday, August 24, 2012, 8:37 AM
>> >
>> > Did you get an error for the dlg_list command? Did you try to make some
>> > calls and try the dialog list command?
>> > Basically this means your fifo is working but you don't either have
>> dialog
>> > module loaded or your opensips-cp is not working. Look at your
>> opensipsctl
>> > config file in your config directory and see where it's pointing for
>> > the
>> > fifo file. Make sure it matches your opensips-cp configuration.
>> >
>> > Regards,Ali Pey
>> > On Fri, Aug 24, 2012 at 9:45 AM, Engineer voip 
>> wrote:
>> >
>> > Hello,
>> >
>> >
>> >
>> > ** The result of  opensipsctl fifo arg is:
>> >
>> >
>> >
>> > root@Poste-810:/usr/local/sbin# opensipsctl fifo arg
>> >
>> > /usr/local/sbin/opensips
>> >
>> > -P
>> >
>> > /var/run/opensips/opensips.pid
>> >
>> > -m
>> >
>> > 64
>> >
>> > -M
>> >
>> > 4
>> >
>> > -u
>> >
>> > opensips
>> >
>> > -g
>> >
>> > opensips
>> >
>> >
>> >
>> > ** But no resultat for opensipsctl fifo dlg_list
>> >
>> > 2012/8/24, Ali Pey :
>> >
>> >> Try these commands:
>> >
>> >>
>> >
>> >> opensipsctl fifo arg
>> >
>> >> opensipsctl fifo dlg_list
>> >
>> >>
>> >
>> >> and post the results here. This should give you a pretty good clue.
>> >
>> >>
>> >
>> >> Regards,
>> >
>> >> Ali Pey
>> >
>> >>
>> >
>> >> On Fri, Aug 24, 2012 at 8:47 AM, Engineer voip 
>> >> wrote:
>> >
>> >>
>> >
>> >>> Hello,
>> >
>> >>>
>> >
>> >>> ** how can i verify that MI connector points to the server?
>> >
>> >>>
>> >
>> >>> ** I have loadid the dialog module in my opensips.cfg like that:
>> >
>> >>>
>> >
>> >>> loadmodule "dialog.so"
>> >
>> >>> modparam("dialog", "dlg_match_mode", 1)
>> >
>> >>> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
>> >
>> >>>

Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Ali Pey
What was the problem? How did you fix it?

It's good to mention your problems and solutions for people that might
experience the same problem in the future.

Regards,
Ali Pey

On Fri, Aug 24, 2012 at 7:10 PM, Engineer voip  wrote:

> Hello,
> It's good, i can to get CDRs and Dialog information using OCP.
> Thank you to all those who helped me.
>
> Best Regards
>
> 2012/8/24, Binan AL Halabi :
> > Hi,
> >
> > restart DB
> > restart opensips
> > reload apache (service httpd reload)
> >
> > //Binan
> >
> > --- On Fri, 8/24/12, Ali Pey  wrote:
> >
> > From: Ali Pey 
> > Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
> > To: "Engineer voip" 
> > Cc: "OpenSIPS users mailling list" 
> > Date: Friday, August 24, 2012, 8:37 AM
> >
> > Did you get an error for the dlg_list command? Did you try to make some
> > calls and try the dialog list command?
> > Basically this means your fifo is working but you don't either have
> dialog
> > module loaded or your opensips-cp is not working. Look at your
> opensipsctl
> > config file in your config directory and see where it's pointing for the
> > fifo file. Make sure it matches your opensips-cp configuration.
> >
> > Regards,Ali Pey
> > On Fri, Aug 24, 2012 at 9:45 AM, Engineer voip 
> wrote:
> >
> > Hello,
> >
> >
> >
> > ** The result of  opensipsctl fifo arg is:
> >
> >
> >
> > root@Poste-810:/usr/local/sbin# opensipsctl fifo arg
> >
> > /usr/local/sbin/opensips
> >
> > -P
> >
> > /var/run/opensips/opensips.pid
> >
> > -m
> >
> > 64
> >
> > -M
> >
> > 4
> >
> > -u
> >
> > opensips
> >
> > -g
> >
> > opensips
> >
> >
> >
> > ** But no resultat for opensipsctl fifo dlg_list
> >
> > 2012/8/24, Ali Pey :
> >
> >> Try these commands:
> >
> >>
> >
> >> opensipsctl fifo arg
> >
> >> opensipsctl fifo dlg_list
> >
> >>
> >
> >> and post the results here. This should give you a pretty good clue.
> >
> >>
> >
> >> Regards,
> >
> >> Ali Pey
> >
> >>
> >
> >> On Fri, Aug 24, 2012 at 8:47 AM, Engineer voip 
> >> wrote:
> >
> >>
> >
> >>> Hello,
> >
> >>>
> >
> >>> ** how can i verify that MI connector points to the server?
> >
> >>>
> >
> >>> ** I have loadid the dialog module in my opensips.cfg like that:
> >
> >>>
> >
> >>> loadmodule "dialog.so"
> >
> >>> modparam("dialog", "dlg_match_mode", 1)
> >
> >>> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
> >
> >>> modparam("dialog", "db_mode", 1)
> >
> >>> modparam("dialog", "db_update_period", 30)
> >
> >>> modparam("dialog", "table_name", "dialog")
> >
> >>> modparam("dialog",
> >
> >>> "db_url","mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE
> >
> >>> ME
> >
> >>> modparam("dialog", "call_id_column", "callid")
> >
> >>> modparam("dialog", "from_uri_column", "from_uri")
> >
> >>> modparam("dialog", "from_tag_column", "from_tag")
> >
> >>> modparam("dialog", "to_uri_column", "to_uri")
> >
> >>> modparam("dialog", "to_tag_column", "to_tag")
> >
> >>> modparam("dialog", "from_cseq_column", "caller_cseq")
> >
> >>> modparam("dialog", "to_cseq_column", "callee_cseq")
> >
> >>> modparam("dialog", "state_column", "state")
> >
> >>> modparam("dialog", "start_time_column", "start_time")
> >
> >>>
> >
> >>> ** For information in my acc table the cdr_id value is empty and i
> >
> >>> don't know how i do to have it, any idea please??
> >
> >>>
> >
> >>>
> >
> >>> Regards
> >
> >>>
> >
> >&g

Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Engineer voip
Hello,
It's good, i can to get CDRs and Dialog information using OCP.
Thank you to all those who helped me.

Best Regards

2012/8/24, Binan AL Halabi :
> Hi,
>
> restart DB
> restart opensips
> reload apache (service httpd reload)
>
> //Binan
>
> --- On Fri, 8/24/12, Ali Pey  wrote:
>
> From: Ali Pey 
> Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
> To: "Engineer voip" 
> Cc: "OpenSIPS users mailling list" 
> Date: Friday, August 24, 2012, 8:37 AM
>
> Did you get an error for the dlg_list command? Did you try to make some
> calls and try the dialog list command?
> Basically this means your fifo is working but you don't either have dialog
> module loaded or your opensips-cp is not working. Look at your opensipsctl
> config file in your config directory and see where it's pointing for the
> fifo file. Make sure it matches your opensips-cp configuration.
>
> Regards,Ali Pey
> On Fri, Aug 24, 2012 at 9:45 AM, Engineer voip  wrote:
>
> Hello,
>
>
>
> ** The result of  opensipsctl fifo arg is:
>
>
>
> root@Poste-810:/usr/local/sbin# opensipsctl fifo arg
>
> /usr/local/sbin/opensips
>
> -P
>
> /var/run/opensips/opensips.pid
>
> -m
>
> 64
>
> -M
>
> 4
>
> -u
>
> opensips
>
> -g
>
> opensips
>
>
>
> ** But no resultat for opensipsctl fifo dlg_list
>
> 2012/8/24, Ali Pey :
>
>> Try these commands:
>
>>
>
>> opensipsctl fifo arg
>
>> opensipsctl fifo dlg_list
>
>>
>
>> and post the results here. This should give you a pretty good clue.
>
>>
>
>> Regards,
>
>> Ali Pey
>
>>
>
>> On Fri, Aug 24, 2012 at 8:47 AM, Engineer voip 
>> wrote:
>
>>
>
>>> Hello,
>
>>>
>
>>> ** how can i verify that MI connector points to the server?
>
>>>
>
>>> ** I have loadid the dialog module in my opensips.cfg like that:
>
>>>
>
>>> loadmodule "dialog.so"
>
>>> modparam("dialog", "dlg_match_mode", 1)
>
>>> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
>
>>> modparam("dialog", "db_mode", 1)
>
>>> modparam("dialog", "db_update_period", 30)
>
>>> modparam("dialog", "table_name", "dialog")
>
>>> modparam("dialog",
>
>>> "db_url","mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE
>
>>> ME
>
>>> modparam("dialog", "call_id_column", "callid")
>
>>> modparam("dialog", "from_uri_column", "from_uri")
>
>>> modparam("dialog", "from_tag_column", "from_tag")
>
>>> modparam("dialog", "to_uri_column", "to_uri")
>
>>> modparam("dialog", "to_tag_column", "to_tag")
>
>>> modparam("dialog", "from_cseq_column", "caller_cseq")
>
>>> modparam("dialog", "to_cseq_column", "callee_cseq")
>
>>> modparam("dialog", "state_column", "state")
>
>>> modparam("dialog", "start_time_column", "start_time")
>
>>>
>
>>> ** For information in my acc table the cdr_id value is empty and i
>
>>> don't know how i do to have it, any idea please??
>
>>>
>
>>>
>
>>> Regards
>
>>>
>
>>> 2012/8/24, Bogdan-Andrei Iancu :
>
>>> > Hi,
>
>>> >
>
>>> > Are you 100% sure that the MI connector you put in CP
>
>>> > ("/tmp/opensips_fifo") points to the server you actually want to
>
>>> > interrogate for dialogs ?
>
>>> >
>
>>> > As I see the MI communication works (as you get the "command dlg_list
>
>>> > is
>
>>> > not available" reply), but it seems you talk from CP with an opensips
>
>>> > which does not have dialog module loaded.
>
>>> >
>
>>> > I leads to 2 options: either you talk to wrong opensips instance,
>
>>> > either
>
>>> > your opensips (if only one) loads a different cfg file than you think
>
>>> > (maybe uses the default one instead the one you listed here).
>
>>> >
>
>>> > Regards,
>
>>> >
>
>>> > Bog

Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Binan AL Halabi
Hi,

restart DB
restart opensips
reload apache (service httpd reload)

//Binan

--- On Fri, 8/24/12, Ali Pey  wrote:

From: Ali Pey 
Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
To: "Engineer voip" 
Cc: "OpenSIPS users mailling list" 
Date: Friday, August 24, 2012, 8:37 AM

Did you get an error for the dlg_list command? Did you try to make some calls 
and try the dialog list command?
Basically this means your fifo is working but you don't either have dialog 
module loaded or your opensips-cp is not working. Look at your opensipsctl 
config file in your config directory and see where it's pointing for the fifo 
file. Make sure it matches your opensips-cp configuration.

Regards,Ali Pey
On Fri, Aug 24, 2012 at 9:45 AM, Engineer voip  wrote:

Hello,



** The result of  opensipsctl fifo arg is:



root@Poste-810:/usr/local/sbin# opensipsctl fifo arg

/usr/local/sbin/opensips

-P

/var/run/opensips/opensips.pid

-m

64

-M

4

-u

opensips

-g

opensips



** But no resultat for opensipsctl fifo dlg_list

2012/8/24, Ali Pey :

> Try these commands:

>

> opensipsctl fifo arg

> opensipsctl fifo dlg_list

>

> and post the results here. This should give you a pretty good clue.

>

> Regards,

> Ali Pey

>

> On Fri, Aug 24, 2012 at 8:47 AM, Engineer voip  wrote:

>

>> Hello,

>>

>> ** how can i verify that MI connector points to the server?

>>

>> ** I have loadid the dialog module in my opensips.cfg like that:

>>

>> loadmodule "dialog.so"

>> modparam("dialog", "dlg_match_mode", 1)

>> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout

>> modparam("dialog", "db_mode", 1)

>> modparam("dialog", "db_update_period", 30)

>> modparam("dialog", "table_name", "dialog")

>> modparam("dialog",

>> "db_url","mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE

>> ME

>> modparam("dialog", "call_id_column", "callid")

>> modparam("dialog", "from_uri_column", "from_uri")

>> modparam("dialog", "from_tag_column", "from_tag")

>> modparam("dialog", "to_uri_column", "to_uri")

>> modparam("dialog", "to_tag_column", "to_tag")

>> modparam("dialog", "from_cseq_column", "caller_cseq")

>> modparam("dialog", "to_cseq_column", "callee_cseq")

>> modparam("dialog", "state_column", "state")

>> modparam("dialog", "start_time_column", "start_time")

>>

>> ** For information in my acc table the cdr_id value is empty and i

>> don't know how i do to have it, any idea please??

>>

>>

>> Regards

>>

>> 2012/8/24, Bogdan-Andrei Iancu :

>> > Hi,

>> >

>> > Are you 100% sure that the MI connector you put in CP

>> > ("/tmp/opensips_fifo") points to the server you actually want to

>> > interrogate for dialogs ?

>> >

>> > As I see the MI communication works (as you get the "command dlg_list

>> > is

>> > not available" reply), but it seems you talk from CP with an opensips

>> > which does not have dialog module loaded.

>> >

>> > I leads to 2 options: either you talk to wrong opensips instance,

>> > either

>> > your opensips (if only one) loads a different cfg file than you think

>> > (maybe uses the default one instead the one you listed here).

>> >

>> > Regards,

>> >

>> > Bogdan-Andrei Iancu

>> > OpenSIPS Founder and Developer

>> > http://www.opensips-solutions.com

>> >

>> >

>> > On 08/24/2012 01:30 PM, Engineer voip wrote:

>> >> Hello,

>> >>

>> >> yes i have configured them like:

>> >>

>> >> db.inc.php configuration is:

>> >>

>> >>   $config->db_driver = "mysql";

>> >>

>> >>   //database host

>> >>   $config->db_host = "localhost";

>> >>

>> >>   //database port - leave empty for default

>> >>   $config->db_port = "";

>> >>

>> >>   //database connection user

>> >>   $config->db_user = "root";

>> >>

>> >>   //database connection password

>> >>   $c

Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Ali Pey
>
> >> >>   //database connection password
> >> >>   $config->db_pass = "1234";
> >> >>
> >> >>   //database name
> >> >>   $config->db_name = "opensips";
> >> >>
> >> >>   if (!empty($config->db_port) ) $config->db_host = $config->db_host
> .
> >> >> ":" . $config->db_port;
> >> >>
> >> >>
> >>
> --
> >> >> boxes.global.inc.php configuration:
> >> >>
> >> >> $box_id=0;
> >> >>
> >> >> // mi host:port pair || fifo_file
> >> >> //$boxes[$box_id]['mi']['conn']="127.0.0.1:8000";
> >> >> $boxes[$box_id]['mi']['conn']="/tmp/opensips_fifo";
> >> >>
> >> >> // monit host:port
> >> >> //$boxes[$box_id]['monit']['conn']="192.168.1.7:2812";
> >> >> //$boxes[$box_id]['monit']['conn']="127.0.0.1:2812";
> >> >> $boxes[$box_id]['monit']['user']="admin";
> >> >> $boxes[$box_id]['monit']['pass']="admin";
> >> >> $boxes[$box_id]['monit']['has_ssl']=0;
> >> >>
> >> >>
> >> >> // description (appears in mi , monit )
> >> >> $boxes[$box_id]['desc']="SIP server";
> >> >>
> >> >>
> >> >> $boxes[$box_id]['assoc_id']=1;
> >> >>
> >> >> // enable local smonitor charts on this box : 0=disabled 1=enabled
> >> >> // (cron)
> >> >> $boxes[$box_id]['smonitor']['charts']=1;
> >> >>
> >> >>
> >> >>
> >> >> Thanks
> >> >>
> >> >>
> >> >>
> >> >> 2012/8/24, Binan AL Halabi:
> >> >>> Hi,
> >> >>>
> >> >>> have you configured files  "db.inc.php" and
> >> >>> "boxes.global.inc.php" ?
> >> >>>
> >> >>> --- On Thu, 8/23/12, Engineer voip  wrote:
> >> >>>
> >> >>> From: Engineer voip
> >> >>> Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
> >> >>> To: "OpenSIPS users mailling list"
> >> >>> Date: Thursday, August 23, 2012, 3:00 PM
> >> >>>
> >> >>> Hi,
> >> >>> someone can help me please !!
> >> >>>
> >> >>> 2012/8/23, Engineer voip:
> >> >>>> Hello,
> >> >>>> I did all this procedures but don't work
> >> >>>>
> >> >>>> my dialog configuration is:
> >> >>>>
> >> >>>> ### dialog module 
> >> >>>> loadmodule "dialog.so"
> >> >>>> modparam("dialog", "dlg_match_mode", 1)
> >> >>>> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
> >> >>>> modparam("dialog", "db_mode", 1)
> >> >>>> modparam("dialog", "db_update_period", 30)
> >> >>>> modparam("dialog", "table_name", "dialog")
> >> >>>> modparam("dialog",
> >> >>>> "db_url","mysql://opensips:opensipsrw@localhost/opensips")
> >> >>>> modparam("dialog", "call_id_column", "callid")
> >> >>>> modparam("dialog", "from_uri_column", "from_uri")
> >> >>>> modparam("dialog", "from_tag_column", "from_tag")
> >> >>>> modparam("dialog", "to_uri_column", "to_uri")
> >> >>>> modparam("dialog", "to_tag_column", "to_tag")
> >> >>>> modparam("dialog", "from_cseq_column", "caller_cseq")
> >> >>>> modparam("dialog", "to_cseq_column", "callee_cseq")
> >> >>>> modparam("dialog", "state_column", "state")
> >> >>>> modparam("dialog", "start_time_column", "start_time")
> >> >>>>
> >> >>>>
> >> >>>> Thank you for your help.
> >> >>>>
> >> >>>> Regards
> >> >>>>
> >> >>>> 2012/8/23, Binan AL Halabi:
> >> >>>>> Hi ,
> >> >>>>> 1- for Dialog : you have to load&  configure the
> >> >>>>> module "dialog" in OpenSIPS script.
> >> >>>>>
> >> >>>>> 2- for CDR viewer :
> >> >>>>>- add table *cdrs.mysql* and stored procedure
> >> *opensips_cdrs.mysql*
> >> >>>>> to OPENSIPS database
> >> >>>>>- edit the cron_job/generate-cdrs_mysql.sh file and change the
> >> >>>>> mysql
> >> >>>>> connection data (hostname,username,password and database)
> >> >>>>>- call the script from the cron
> >> >>>>>
> >> >>>>> check the opensips-cp INSTALL file for this.
> >> >>>>>
> >> >>>>> //Binan
> >> >>>>>
> >> >>>>> --- On Thu, 8/23/12, Engineer voip  wrote:
> >> >>>>>
> >> >>>>> From: Engineer voip
> >> >>>>> Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
> >> >>>>> To: "OpenSIPS users mailling list"
> >> >>>>> Date: Thursday, August 23, 2012, 6:15 AM
> >> >>>>>
> >> >>>>> hello,
> >> >>>>>
> >> >>>>> when i click "dialog" i get the message "
> >> >>>>> ERROR:mi_fifo:mi_fifo_server: command dlg_list is not available "
> >> >>>>>
> >> >>>>> thank you for help
> >> >>>>>
> >> >>>>> 2012/8/23, Binan AL Halabi:
> >> >>>>>> Hi,
> >> >>>>>> what you get when you click "dialog" under "system" list on
> >> >>>>>> opensips-cp
> >> >>>>>> ?
> >> >>>>>>
> >> >>>>>> //Binan
> >> >>>>>>
> >> >>>>>> --- On Thu, 8/23/12, Engineer voip  wrote:
> >> >>>>>>
> >> >>>>>> From: Engineer voip
> >> >>>>>> Subject: [OpenSIPS-Users] cdr and Dialog on opensips-cp
> >> >>>>>> To: "OpenSIPS users mailling list"
> >> >>>>>> Date: Thursday, August 23, 2012, 3:06 AM
> >> >>>>>>
> >> >>>>>> Hello All,
> >> >>>>>>
> >> >>>>>> I'm using opensips-cp with opensips 1.8, and i can do the call
> >> >>>>>> between
> >> >>>>>> two
> >> >>>>>> users but i can't  get the CDRs and Dialog informations by using
> >> >>>>>> opensips-cp.
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> someone can help me, please?
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> thanks
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> -Inline Attachment Follows-
> >> >>>>>>
> >> >>>>>> ___
> >> >>>>>> Users mailing list
> >> >>>>>> Users@lists.opensips.org
> >> >>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >> >>>>>>
> >> >>>>> ___
> >> >>>>> Users mailing list
> >> >>>>> Users@lists.opensips.org
> >> >>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >> >>>>>
> >> >>> ___
> >> >>> Users mailing list
> >> >>> Users@lists.opensips.org
> >> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >> >>>
> >> >> ___
> >> >> Users mailing list
> >> >> Users@lists.opensips.org
> >> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >> >>
> >> >
> >>
> >> ___
> >> Users mailing list
> >> Users@lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >>
> >
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread yassine.ab
Hi,

trying to put the ip address instead of the path





--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/cdr-and-Dialog-on-opensips-cp-tp7581329p7581380.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Engineer voip
Hello,

** The result of  opensipsctl fifo arg is:

root@Poste-810:/usr/local/sbin# opensipsctl fifo arg
/usr/local/sbin/opensips
-P
/var/run/opensips/opensips.pid
-m
64
-M
4
-u
opensips
-g
opensips

** But no resultat for opensipsctl fifo dlg_list
2012/8/24, Ali Pey :
> Try these commands:
>
> opensipsctl fifo arg
> opensipsctl fifo dlg_list
>
> and post the results here. This should give you a pretty good clue.
>
> Regards,
> Ali Pey
>
> On Fri, Aug 24, 2012 at 8:47 AM, Engineer voip  wrote:
>
>> Hello,
>>
>> ** how can i verify that MI connector points to the server?
>>
>> ** I have loadid the dialog module in my opensips.cfg like that:
>>
>> loadmodule "dialog.so"
>> modparam("dialog", "dlg_match_mode", 1)
>> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
>> modparam("dialog", "db_mode", 1)
>> modparam("dialog", "db_update_period", 30)
>> modparam("dialog", "table_name", "dialog")
>> modparam("dialog",
>> "db_url","mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE
>> ME
>> modparam("dialog", "call_id_column", "callid")
>> modparam("dialog", "from_uri_column", "from_uri")
>> modparam("dialog", "from_tag_column", "from_tag")
>> modparam("dialog", "to_uri_column", "to_uri")
>> modparam("dialog", "to_tag_column", "to_tag")
>> modparam("dialog", "from_cseq_column", "caller_cseq")
>> modparam("dialog", "to_cseq_column", "callee_cseq")
>> modparam("dialog", "state_column", "state")
>> modparam("dialog", "start_time_column", "start_time")
>>
>> ** For information in my acc table the cdr_id value is empty and i
>> don't know how i do to have it, any idea please??
>>
>>
>> Regards
>>
>> 2012/8/24, Bogdan-Andrei Iancu :
>> > Hi,
>> >
>> > Are you 100% sure that the MI connector you put in CP
>> > ("/tmp/opensips_fifo") points to the server you actually want to
>> > interrogate for dialogs ?
>> >
>> > As I see the MI communication works (as you get the "command dlg_list
>> > is
>> > not available" reply), but it seems you talk from CP with an opensips
>> > which does not have dialog module loaded.
>> >
>> > I leads to 2 options: either you talk to wrong opensips instance,
>> > either
>> > your opensips (if only one) loads a different cfg file than you think
>> > (maybe uses the default one instead the one you listed here).
>> >
>> > Regards,
>> >
>> > Bogdan-Andrei Iancu
>> > OpenSIPS Founder and Developer
>> > http://www.opensips-solutions.com
>> >
>> >
>> > On 08/24/2012 01:30 PM, Engineer voip wrote:
>> >> Hello,
>> >>
>> >> yes i have configured them like:
>> >>
>> >> db.inc.php configuration is:
>> >>
>> >>   $config->db_driver = "mysql";
>> >>
>> >>   //database host
>> >>   $config->db_host = "localhost";
>> >>
>> >>   //database port - leave empty for default
>> >>   $config->db_port = "";
>> >>
>> >>   //database connection user
>> >>   $config->db_user = "root";
>> >>
>> >>   //database connection password
>> >>   $config->db_pass = "1234";
>> >>
>> >>   //database name
>> >>   $config->db_name = "opensips";
>> >>
>> >>   if (!empty($config->db_port) ) $config->db_host = $config->db_host .
>> >> ":" . $config->db_port;
>> >>
>> >>
>> --
>> >> boxes.global.inc.php configuration:
>> >>
>> >> $box_id=0;
>> >>
>> >> // mi host:port pair || fifo_file
>> >> //$boxes[$box_id]['mi']['conn']="127.0.0.1:8000";
>> >> $boxes[$box_id]['mi']['conn']="/tmp/opensips_fifo";
>> >>
>> >> // monit host:port

Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Ali Pey
Try these commands:

opensipsctl fifo arg
opensipsctl fifo dlg_list

and post the results here. This should give you a pretty good clue.

Regards,
Ali Pey

On Fri, Aug 24, 2012 at 8:47 AM, Engineer voip  wrote:

> Hello,
>
> ** how can i verify that MI connector points to the server?
>
> ** I have loadid the dialog module in my opensips.cfg like that:
>
> loadmodule "dialog.so"
> modparam("dialog", "dlg_match_mode", 1)
> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
> modparam("dialog", "db_mode", 1)
> modparam("dialog", "db_update_period", 30)
> modparam("dialog", "table_name", "dialog")
> modparam("dialog",
> "db_url","mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE
> ME
> modparam("dialog", "call_id_column", "callid")
> modparam("dialog", "from_uri_column", "from_uri")
> modparam("dialog", "from_tag_column", "from_tag")
> modparam("dialog", "to_uri_column", "to_uri")
> modparam("dialog", "to_tag_column", "to_tag")
> modparam("dialog", "from_cseq_column", "caller_cseq")
> modparam("dialog", "to_cseq_column", "callee_cseq")
> modparam("dialog", "state_column", "state")
> modparam("dialog", "start_time_column", "start_time")
>
> ** For information in my acc table the cdr_id value is empty and i
> don't know how i do to have it, any idea please??
>
>
> Regards
>
> 2012/8/24, Bogdan-Andrei Iancu :
> > Hi,
> >
> > Are you 100% sure that the MI connector you put in CP
> > ("/tmp/opensips_fifo") points to the server you actually want to
> > interrogate for dialogs ?
> >
> > As I see the MI communication works (as you get the "command dlg_list is
> > not available" reply), but it seems you talk from CP with an opensips
> > which does not have dialog module loaded.
> >
> > I leads to 2 options: either you talk to wrong opensips instance, either
> > your opensips (if only one) loads a different cfg file than you think
> > (maybe uses the default one instead the one you listed here).
> >
> > Regards,
> >
> > Bogdan-Andrei Iancu
> > OpenSIPS Founder and Developer
> > http://www.opensips-solutions.com
> >
> >
> > On 08/24/2012 01:30 PM, Engineer voip wrote:
> >> Hello,
> >>
> >> yes i have configured them like:
> >>
> >> db.inc.php configuration is:
> >>
> >>   $config->db_driver = "mysql";
> >>
> >>   //database host
> >>   $config->db_host = "localhost";
> >>
> >>   //database port - leave empty for default
> >>   $config->db_port = "";
> >>
> >>   //database connection user
> >>   $config->db_user = "root";
> >>
> >>   //database connection password
> >>   $config->db_pass = "1234";
> >>
> >>   //database name
> >>   $config->db_name = "opensips";
> >>
> >>   if (!empty($config->db_port) ) $config->db_host = $config->db_host .
> >> ":" . $config->db_port;
> >>
> >>
> --
> >> boxes.global.inc.php configuration:
> >>
> >> $box_id=0;
> >>
> >> // mi host:port pair || fifo_file
> >> //$boxes[$box_id]['mi']['conn']="127.0.0.1:8000";
> >> $boxes[$box_id]['mi']['conn']="/tmp/opensips_fifo";
> >>
> >> // monit host:port
> >> //$boxes[$box_id]['monit']['conn']="192.168.1.7:2812";
> >> //$boxes[$box_id]['monit']['conn']="127.0.0.1:2812";
> >> $boxes[$box_id]['monit']['user']="admin";
> >> $boxes[$box_id]['monit']['pass']="admin";
> >> $boxes[$box_id]['monit']['has_ssl']=0;
> >>
> >>
> >> // description (appears in mi , monit )
> >> $boxes[$box_id]['desc']="SIP server";
> >>
> >>
> >> $boxes[$box_id]['assoc_id']=1;
> >>
> &g

Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Engineer voip
Hello,

** how can i verify that MI connector points to the server?

** I have loadid the dialog module in my opensips.cfg like that:

loadmodule "dialog.so"
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
modparam("dialog", "db_mode", 1)
modparam("dialog", "db_update_period", 30)
modparam("dialog", "table_name", "dialog")
modparam("dialog",
"db_url","mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE
ME
modparam("dialog", "call_id_column", "callid")
modparam("dialog", "from_uri_column", "from_uri")
modparam("dialog", "from_tag_column", "from_tag")
modparam("dialog", "to_uri_column", "to_uri")
modparam("dialog", "to_tag_column", "to_tag")
modparam("dialog", "from_cseq_column", "caller_cseq")
modparam("dialog", "to_cseq_column", "callee_cseq")
modparam("dialog", "state_column", "state")
modparam("dialog", "start_time_column", "start_time")

** For information in my acc table the cdr_id value is empty and i
don't know how i do to have it, any idea please??


Regards

2012/8/24, Bogdan-Andrei Iancu :
> Hi,
>
> Are you 100% sure that the MI connector you put in CP
> ("/tmp/opensips_fifo") points to the server you actually want to
> interrogate for dialogs ?
>
> As I see the MI communication works (as you get the "command dlg_list is
> not available" reply), but it seems you talk from CP with an opensips
> which does not have dialog module loaded.
>
> I leads to 2 options: either you talk to wrong opensips instance, either
> your opensips (if only one) loads a different cfg file than you think
> (maybe uses the default one instead the one you listed here).
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
>
> On 08/24/2012 01:30 PM, Engineer voip wrote:
>> Hello,
>>
>> yes i have configured them like:
>>
>> db.inc.php configuration is:
>>
>>   $config->db_driver = "mysql";
>>
>>   //database host
>>   $config->db_host = "localhost";
>>
>>   //database port - leave empty for default
>>   $config->db_port = "";
>>
>>   //database connection user
>>   $config->db_user = "root";
>>
>>   //database connection password
>>   $config->db_pass = "1234";
>>
>>   //database name
>>   $config->db_name = "opensips";
>>
>>   if (!empty($config->db_port) ) $config->db_host = $config->db_host .
>> ":" . $config->db_port;
>>
>> --
>> boxes.global.inc.php configuration:
>>
>> $box_id=0;
>>
>> // mi host:port pair || fifo_file
>> //$boxes[$box_id]['mi']['conn']="127.0.0.1:8000";
>> $boxes[$box_id]['mi']['conn']="/tmp/opensips_fifo";
>>
>> // monit host:port
>> //$boxes[$box_id]['monit']['conn']="192.168.1.7:2812";
>> //$boxes[$box_id]['monit']['conn']="127.0.0.1:2812";
>> $boxes[$box_id]['monit']['user']="admin";
>> $boxes[$box_id]['monit']['pass']="admin";
>> $boxes[$box_id]['monit']['has_ssl']=0;
>>
>>
>> // description (appears in mi , monit )
>> $boxes[$box_id]['desc']="SIP server";
>>
>>
>> $boxes[$box_id]['assoc_id']=1;
>>
>> // enable local smonitor charts on this box : 0=disabled 1=enabled
>> // (cron)
>> $boxes[$box_id]['smonitor']['charts']=1;
>>
>>
>>
>> Thanks
>>
>>
>>
>> 2012/8/24, Binan AL Halabi:
>>> Hi,
>>>
>>> have you configured files  "db.inc.php" and
>>> "boxes.global.inc.php" ?
>>>
>>> --- On Thu, 8/23/12, Engineer voip  wrote:
>>>
>>> From: Engineer voip
>>> Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
>>> To: "OpenSIPS users mailling list"
>>> Date: Thursday, August 23, 2012, 3:00 PM
>>>
>>> Hi,
&g

Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Bogdan-Andrei Iancu

Hi,

Are you 100% sure that the MI connector you put in CP 
("/tmp/opensips_fifo") points to the server you actually want to 
interrogate for dialogs ?


As I see the MI communication works (as you get the "command dlg_list is 
not available" reply), but it seems you talk from CP with an opensips 
which does not have dialog module loaded.


I leads to 2 options: either you talk to wrong opensips instance, either 
your opensips (if only one) loads a different cfg file than you think 
(maybe uses the default one instead the one you listed here).


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


On 08/24/2012 01:30 PM, Engineer voip wrote:

Hello,

yes i have configured them like:

db.inc.php configuration is:

  $config->db_driver = "mysql";

  //database host
  $config->db_host = "localhost";

  //database port - leave empty for default
  $config->db_port = "";

  //database connection user
  $config->db_user = "root";

  //database connection password
  $config->db_pass = "1234";

  //database name
  $config->db_name = "opensips";

  if (!empty($config->db_port) ) $config->db_host = $config->db_host .
":" . $config->db_port;

--
boxes.global.inc.php configuration:

$box_id=0;

// mi host:port pair || fifo_file
//$boxes[$box_id]['mi']['conn']="127.0.0.1:8000";
$boxes[$box_id]['mi']['conn']="/tmp/opensips_fifo";

// monit host:port
//$boxes[$box_id]['monit']['conn']="192.168.1.7:2812";
//$boxes[$box_id]['monit']['conn']="127.0.0.1:2812";
$boxes[$box_id]['monit']['user']="admin";
$boxes[$box_id]['monit']['pass']="admin";
$boxes[$box_id]['monit']['has_ssl']=0;


// description (appears in mi , monit )
$boxes[$box_id]['desc']="SIP server";


$boxes[$box_id]['assoc_id']=1;

// enable local smonitor charts on this box : 0=disabled 1=enabled
// (cron)
$boxes[$box_id]['smonitor']['charts']=1;



Thanks



2012/8/24, Binan AL Halabi:

Hi,

have you configured files  "db.inc.php" and
"boxes.global.inc.php" ?

--- On Thu, 8/23/12, Engineer voip  wrote:

From: Engineer voip
Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
To: "OpenSIPS users mailling list"
Date: Thursday, August 23, 2012, 3:00 PM

Hi,
someone can help me please !!

2012/8/23, Engineer voip:

Hello,
I did all this procedures but don't work

my dialog configuration is:

### dialog module 
loadmodule "dialog.so"
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
modparam("dialog", "db_mode", 1)
modparam("dialog", "db_update_period", 30)
modparam("dialog", "table_name", "dialog")
modparam("dialog",
"db_url","mysql://opensips:opensipsrw@localhost/opensips")
modparam("dialog", "call_id_column", "callid")
modparam("dialog", "from_uri_column", "from_uri")
modparam("dialog", "from_tag_column", "from_tag")
modparam("dialog", "to_uri_column", "to_uri")
modparam("dialog", "to_tag_column", "to_tag")
modparam("dialog", "from_cseq_column", "caller_cseq")
modparam("dialog", "to_cseq_column", "callee_cseq")
modparam("dialog", "state_column", "state")
modparam("dialog", "start_time_column", "start_time")


Thank you for your help.

Regards

2012/8/23, Binan AL Halabi:

Hi ,
1- for Dialog : you have to load&  configure the
module "dialog" in OpenSIPS script.

2- for CDR viewer :
   - add table *cdrs.mysql* and stored procedure *opensips_cdrs.mysql*
to OPENSIPS database
   - edit the cron_job/generate-cdrs_mysql.sh file and change the mysql
connection data (hostname,username,password and database)
   - call the script from the cron

check the opensips-cp INSTALL file for this.

//Binan

--- On Thu, 8/23/12, Engineer voip  wrote:

From: Engineer voip
Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
To: "OpenSIPS users mailling list"
Date: Thursday, August 23, 2012, 6:15 AM

hello,

when i click "dialog" i get the message "
ERROR:mi_fifo:mi_fifo_server: command dlg_list is not available "

thank you for help

2012/8/23, Binan AL Halabi:

Hi,
what you get when y

Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Engineer voip
Hello,

yes i have configured them like:

db.inc.php configuration is:

 $config->db_driver = "mysql";

 //database host
 $config->db_host = "localhost";

 //database port - leave empty for default
 $config->db_port = "";

 //database connection user
 $config->db_user = "root";

 //database connection password
 $config->db_pass = "1234";

 //database name
 $config->db_name = "opensips";

 if (!empty($config->db_port) ) $config->db_host = $config->db_host .
":" . $config->db_port;

--
boxes.global.inc.php configuration:

$box_id=0;

// mi host:port pair || fifo_file
//$boxes[$box_id]['mi']['conn']="127.0.0.1:8000";
$boxes[$box_id]['mi']['conn']="/tmp/opensips_fifo";

// monit host:port
//$boxes[$box_id]['monit']['conn']="192.168.1.7:2812";
//$boxes[$box_id]['monit']['conn']="127.0.0.1:2812";
$boxes[$box_id]['monit']['user']="admin";
$boxes[$box_id]['monit']['pass']="admin";
$boxes[$box_id]['monit']['has_ssl']=0;


// description (appears in mi , monit )
$boxes[$box_id]['desc']="SIP server";


$boxes[$box_id]['assoc_id']=1;

// enable local smonitor charts on this box : 0=disabled 1=enabled
// (cron)
$boxes[$box_id]['smonitor']['charts']=1;



Thanks



2012/8/24, Binan AL Halabi :
> Hi,
>
> have you configured files  "db.inc.php" and
> "boxes.global.inc.php" ?
>
> --- On Thu, 8/23/12, Engineer voip  wrote:
>
> From: Engineer voip 
> Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
> To: "OpenSIPS users mailling list" 
> Date: Thursday, August 23, 2012, 3:00 PM
>
> Hi,
> someone can help me please !!
>
> 2012/8/23, Engineer voip :
>> Hello,
>> I did all this procedures but don't work
>>
>> my dialog configuration is:
>>
>> ### dialog module 
>> loadmodule "dialog.so"
>> modparam("dialog", "dlg_match_mode", 1)
>> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
>> modparam("dialog", "db_mode", 1)
>> modparam("dialog", "db_update_period", 30)
>> modparam("dialog", "table_name", "dialog")
>> modparam("dialog",
>> "db_url","mysql://opensips:opensipsrw@localhost/opensips")
>> modparam("dialog", "call_id_column", "callid")
>> modparam("dialog", "from_uri_column", "from_uri")
>> modparam("dialog", "from_tag_column", "from_tag")
>> modparam("dialog", "to_uri_column", "to_uri")
>> modparam("dialog", "to_tag_column", "to_tag")
>> modparam("dialog", "from_cseq_column", "caller_cseq")
>> modparam("dialog", "to_cseq_column", "callee_cseq")
>> modparam("dialog", "state_column", "state")
>> modparam("dialog", "start_time_column", "start_time")
>>
>>
>> Thank you for your help.
>>
>> Regards
>>
>> 2012/8/23, Binan AL Halabi :
>>> Hi ,
>>> 1- for Dialog : you have to load & configure the
>>> module "dialog" in OpenSIPS script.
>>>
>>> 2- for CDR viewer :
>>>  - add table *cdrs.mysql* and stored procedure *opensips_cdrs.mysql*
>>> to OPENSIPS database
>>>  - edit the cron_job/generate-cdrs_mysql.sh file and change the mysql
>>> connection data (hostname,username,password and database)
>>>  - call the script from the cron
>>>
>>> check the opensips-cp INSTALL file for this.
>>>
>>> //Binan
>>>
>>> --- On Thu, 8/23/12, Engineer voip  wrote:
>>>
>>> From: Engineer voip 
>>> Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
>>> To: "OpenSIPS users mailling list" 
>>> Date: Thursday, August 23, 2012, 6:15 AM
>>>
>>> hello,
>>>
>>> when i click "dialog" i get the message "
>>> ERROR:mi_fifo:mi_fifo_server: command dlg_list is not available "
>>>
>>> thank you for help
>>>
>>> 2012/8/23, Binan AL Halabi :
>>>> Hi,
>>>> what you get when you click "dialog" under "system" list on opensips-cp
>>>> ?
>>>>
>>>> //Binan
>>>>
>>>> --- On Thu, 8/23/12, Engineer voip  wrote:
>>>>
>>>> From: Engineer voip 
>>>> Subject: [OpenSIPS-Users] cdr and Dialog on opensips-cp
>>>> To: "OpenSIPS users mailling list" 
>>>> Date: Thursday, August 23, 2012, 3:06 AM
>>>>
>>>> Hello All,
>>>>
>>>> I'm using opensips-cp with opensips 1.8, and i can do the call between
>>>> two
>>>> users but i can't  get the CDRs and Dialog informations by using
>>>> opensips-cp.
>>>>
>>>>
>>>> someone can help me, please?
>>>>
>>>>
>>>> thanks
>>>>
>>>>
>>>> -Inline Attachment Follows-
>>>>
>>>> ___
>>>> Users mailing list
>>>> Users@lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-24 Thread Binan AL Halabi
Hi,

have you configured files  "db.inc.php" and
"boxes.global.inc.php" ?

--- On Thu, 8/23/12, Engineer voip  wrote:

From: Engineer voip 
Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
To: "OpenSIPS users mailling list" 
Date: Thursday, August 23, 2012, 3:00 PM

Hi,
someone can help me please !!

2012/8/23, Engineer voip :
> Hello,
> I did all this procedures but don't work
>
> my dialog configuration is:
>
> ### dialog module 
> loadmodule "dialog.so"
> modparam("dialog", "dlg_match_mode", 1)
> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
> modparam("dialog", "db_mode", 1)
> modparam("dialog", "db_update_period", 30)
> modparam("dialog", "table_name", "dialog")
> modparam("dialog",
> "db_url","mysql://opensips:opensipsrw@localhost/opensips")
> modparam("dialog", "call_id_column", "callid")
> modparam("dialog", "from_uri_column", "from_uri")
> modparam("dialog", "from_tag_column", "from_tag")
> modparam("dialog", "to_uri_column", "to_uri")
> modparam("dialog", "to_tag_column", "to_tag")
> modparam("dialog", "from_cseq_column", "caller_cseq")
> modparam("dialog", "to_cseq_column", "callee_cseq")
> modparam("dialog", "state_column", "state")
> modparam("dialog", "start_time_column", "start_time")
>
>
> Thank you for your help.
>
> Regards
>
> 2012/8/23, Binan AL Halabi :
>> Hi ,
>> 1- for Dialog : you have to load & configure the
>> module "dialog" in OpenSIPS script.
>>
>> 2- for CDR viewer :
>>  - add table *cdrs.mysql* and stored procedure *opensips_cdrs.mysql*
>> to OPENSIPS database
>>  - edit the cron_job/generate-cdrs_mysql.sh file and change the mysql
>> connection data (hostname,username,password and database)
>>  - call the script from the cron
>>
>> check the opensips-cp INSTALL file for this.
>>
>> //Binan
>>
>> --- On Thu, 8/23/12, Engineer voip  wrote:
>>
>> From: Engineer voip 
>> Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
>> To: "OpenSIPS users mailling list" 
>> Date: Thursday, August 23, 2012, 6:15 AM
>>
>> hello,
>>
>> when i click "dialog" i get the message "
>> ERROR:mi_fifo:mi_fifo_server: command dlg_list is not available "
>>
>> thank you for help
>>
>> 2012/8/23, Binan AL Halabi :
>>> Hi,
>>> what you get when you click "dialog" under "system" list on opensips-cp
>>> ?
>>>
>>> //Binan
>>>
>>> --- On Thu, 8/23/12, Engineer voip  wrote:
>>>
>>> From: Engineer voip 
>>> Subject: [OpenSIPS-Users] cdr and Dialog on opensips-cp
>>> To: "OpenSIPS users mailling list" 
>>> Date: Thursday, August 23, 2012, 3:06 AM
>>>
>>> Hello All,
>>>
>>> I'm using opensips-cp with opensips 1.8, and i can do the call between
>>> two
>>> users but i can't  get the CDRs and Dialog informations by using
>>> opensips-cp.
>>>
>>>
>>> someone can help me, please?
>>>
>>>
>>> thanks
>>>
>>>
>>> -Inline Attachment Follows-
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-23 Thread Engineer voip
Hi,
someone can help me please !!

2012/8/23, Engineer voip :
> Hello,
> I did all this procedures but don't work
>
> my dialog configuration is:
>
> ### dialog module 
> loadmodule "dialog.so"
> modparam("dialog", "dlg_match_mode", 1)
> modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
> modparam("dialog", "db_mode", 1)
> modparam("dialog", "db_update_period", 30)
> modparam("dialog", "table_name", "dialog")
> modparam("dialog",
> "db_url","mysql://opensips:opensipsrw@localhost/opensips")
> modparam("dialog", "call_id_column", "callid")
> modparam("dialog", "from_uri_column", "from_uri")
> modparam("dialog", "from_tag_column", "from_tag")
> modparam("dialog", "to_uri_column", "to_uri")
> modparam("dialog", "to_tag_column", "to_tag")
> modparam("dialog", "from_cseq_column", "caller_cseq")
> modparam("dialog", "to_cseq_column", "callee_cseq")
> modparam("dialog", "state_column", "state")
> modparam("dialog", "start_time_column", "start_time")
>
>
> Thank you for your help.
>
> Regards
>
> 2012/8/23, Binan AL Halabi :
>> Hi ,
>> 1- for Dialog : you have to load & configure the
>> module "dialog" in OpenSIPS script.
>>
>> 2- for CDR viewer :
>>  - add table *cdrs.mysql* and stored procedure *opensips_cdrs.mysql*
>> to OPENSIPS database
>>  - edit the cron_job/generate-cdrs_mysql.sh file and change the mysql
>> connection data (hostname,username,password and database)
>>  - call the script from the cron
>>
>> check the opensips-cp INSTALL file for this.
>>
>> //Binan
>>
>> --- On Thu, 8/23/12, Engineer voip  wrote:
>>
>> From: Engineer voip 
>> Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
>> To: "OpenSIPS users mailling list" 
>> Date: Thursday, August 23, 2012, 6:15 AM
>>
>> hello,
>>
>> when i click "dialog" i get the message "
>> ERROR:mi_fifo:mi_fifo_server: command dlg_list is not available "
>>
>> thank you for help
>>
>> 2012/8/23, Binan AL Halabi :
>>> Hi,
>>> what you get when you click "dialog" under "system" list on opensips-cp
>>> ?
>>>
>>> //Binan
>>>
>>> --- On Thu, 8/23/12, Engineer voip  wrote:
>>>
>>> From: Engineer voip 
>>> Subject: [OpenSIPS-Users] cdr and Dialog on opensips-cp
>>> To: "OpenSIPS users mailling list" 
>>> Date: Thursday, August 23, 2012, 3:06 AM
>>>
>>> Hello All,
>>>
>>> I'm using opensips-cp with opensips 1.8, and i can do the call between
>>> two
>>> users but i can't  get the CDRs and Dialog informations by using
>>> opensips-cp.
>>>
>>>
>>> someone can help me, please?
>>>
>>>
>>> thanks
>>>
>>>
>>> -Inline Attachment Follows-
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-23 Thread Engineer voip
Hello,
I did all this procedures but don't work

my dialog configuration is:

### dialog module 
loadmodule "dialog.so"
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog", "default_timeout", 21600)  # 6 hours timeout
modparam("dialog", "db_mode", 1)
modparam("dialog", "db_update_period", 30)
modparam("dialog", "table_name", "dialog")
modparam("dialog", "db_url","mysql://opensips:opensipsrw@localhost/opensips")
modparam("dialog", "call_id_column", "callid")
modparam("dialog", "from_uri_column", "from_uri")
modparam("dialog", "from_tag_column", "from_tag")
modparam("dialog", "to_uri_column", "to_uri")
modparam("dialog", "to_tag_column", "to_tag")
modparam("dialog", "from_cseq_column", "caller_cseq")
modparam("dialog", "to_cseq_column", "callee_cseq")
modparam("dialog", "state_column", "state")
modparam("dialog", "start_time_column", "start_time")


Thank you for your help.

Regards

2012/8/23, Binan AL Halabi :
> Hi ,
> 1- for Dialog : you have to load & configure the
> module "dialog" in OpenSIPS script.
>
> 2- for CDR viewer :
>  - add table *cdrs.mysql* and stored procedure *opensips_cdrs.mysql*
> to OPENSIPS database
>  - edit the cron_job/generate-cdrs_mysql.sh file and change the mysql
> connection data (hostname,username,password and database)
>  - call the script from the cron
>
> check the opensips-cp INSTALL file for this.
>
> //Binan
>
> --- On Thu, 8/23/12, Engineer voip  wrote:
>
> From: Engineer voip 
> Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
> To: "OpenSIPS users mailling list" 
> Date: Thursday, August 23, 2012, 6:15 AM
>
> hello,
>
> when i click "dialog" i get the message "
> ERROR:mi_fifo:mi_fifo_server: command dlg_list is not available "
>
> thank you for help
>
> 2012/8/23, Binan AL Halabi :
>> Hi,
>> what you get when you click "dialog" under "system" list on opensips-cp ?
>>
>> //Binan
>>
>> --- On Thu, 8/23/12, Engineer voip  wrote:
>>
>> From: Engineer voip 
>> Subject: [OpenSIPS-Users] cdr and Dialog on opensips-cp
>> To: "OpenSIPS users mailling list" 
>> Date: Thursday, August 23, 2012, 3:06 AM
>>
>> Hello All,
>>
>> I'm using opensips-cp with opensips 1.8, and i can do the call between
>> two
>> users but i can't  get the CDRs and Dialog informations by using
>> opensips-cp.
>>
>>
>> someone can help me, please?
>>
>>
>> thanks
>>
>>
>> -Inline Attachment Follows-
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-23 Thread Binan AL Halabi
Hi ,
1- for Dialog : you have to load & configure the 
module "dialog" in OpenSIPS script.

2- for CDR viewer :
 - add table *cdrs.mysql* and stored procedure *opensips_cdrs.mysql* 
to OPENSIPS database 
 - edit the cron_job/generate-cdrs_mysql.sh file and change the mysql 
connection data (hostname,username,password and database)
 - call the script from the cron

check the opensips-cp INSTALL file for this. 

//Binan

--- On Thu, 8/23/12, Engineer voip  wrote:

From: Engineer voip 
Subject: Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp
To: "OpenSIPS users mailling list" 
Date: Thursday, August 23, 2012, 6:15 AM

hello,

when i click "dialog" i get the message "
ERROR:mi_fifo:mi_fifo_server: command dlg_list is not available "

thank you for help

2012/8/23, Binan AL Halabi :
> Hi,
> what you get when you click "dialog" under "system" list on opensips-cp ?
>
> //Binan
>
> --- On Thu, 8/23/12, Engineer voip  wrote:
>
> From: Engineer voip 
> Subject: [OpenSIPS-Users] cdr and Dialog on opensips-cp
> To: "OpenSIPS users mailling list" 
> Date: Thursday, August 23, 2012, 3:06 AM
>
> Hello All,
>
> I'm using opensips-cp with opensips 1.8, and i can do the call between two
> users but i can't  get the CDRs and Dialog informations by using
> opensips-cp.
>
>
> someone can help me, please?
>
>
> thanks
>
>
> -Inline Attachment Follows-
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-23 Thread Engineer voip
hello,

when i click "dialog" i get the message "
ERROR:mi_fifo:mi_fifo_server: command dlg_list is not available "

thank you for help

2012/8/23, Binan AL Halabi :
> Hi,
> what you get when you click "dialog" under "system" list on opensips-cp ?
>
> //Binan
>
> --- On Thu, 8/23/12, Engineer voip  wrote:
>
> From: Engineer voip 
> Subject: [OpenSIPS-Users] cdr and Dialog on opensips-cp
> To: "OpenSIPS users mailling list" 
> Date: Thursday, August 23, 2012, 3:06 AM
>
> Hello All,
>
> I'm using opensips-cp with opensips 1.8, and i can do the call between two
> users but i can't  get the CDRs and Dialog informations by using
> opensips-cp.
>
>
> someone can help me, please?
>
>
> thanks
>
>
> -Inline Attachment Follows-
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-23 Thread Binan AL Halabi
Hi,
what you get when you click "dialog" under "system" list on opensips-cp ?

//Binan

--- On Thu, 8/23/12, Engineer voip  wrote:

From: Engineer voip 
Subject: [OpenSIPS-Users] cdr and Dialog on opensips-cp
To: "OpenSIPS users mailling list" 
Date: Thursday, August 23, 2012, 3:06 AM

Hello All,

I'm using opensips-cp with opensips 1.8, and i can do the call between two 
users but i can't  get the CDRs and Dialog informations by using opensips-cp.


someone can help me, please?


thanks


-Inline Attachment Follows-

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] cdr and Dialog on opensips-cp

2012-08-23 Thread Engineer voip
Hello All,

I'm using opensips-cp with opensips 1.8, and i can do the call between two
users but i can't  get the CDRs and Dialog informations by using
opensips-cp.


someone can help me, please?

thanks
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-19 Thread Jayesh Nambiar
Hi Razwan,
This is the pastebin of logs after shutdown:
http://pastebin.com/tvmrSqwB

This is the pastebin of logs after start which is huge:
http://pastebin.com/C6K4Jt5y

--- Jayesh


On Wed, Dec 7, 2011 at 5:46 PM, Razvan Crainea
wrote:

>  Hi, Jayesh!
>
> I need the logs after opensips restarts. The result might also be pretty
> large.
>
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/07/2011 02:14 PM, Jayesh Nambiar wrote:
>
> Hi Razwan,
> I have applied the patch and made it working. Do you still only need the
> logs after opensips shutdown or also the logs after opensips restarts.
>
> --- Jayesh
>
> On Wed, Dec 7, 2011 at 4:35 PM, Razvan Crainea  > wrote:
>
>>  Hi, Jayesh!
>>
>> It seems like the problem appears while parsing the string got from the
>> database, so after opensips is restarted. The patch attached should give us
>> more information about the error.
>>
>>
>> Regards,
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Developer
>>
>>
>>   On 12/07/2011 12:37 PM, Jayesh Nambiar wrote:
>>
>> This is the string what I see when I query the dialog table for vars:
>>
>> accX_flags#   |accX_db#(  2 1
>>  11 1002
>>  12013386166
>>  919833171405 0 203.153.53.158 203.153.53.136 0 17 0 2 IP India - Mobile
>> 919 9198 2 1 2 4 0.0150 0.0130 0 0. 0.0226 1. 6 1 6 1 1 2 2 2
>>  Aal Izz Well
>>  Aal Izz Well 1 3 1.2.3.4|accX_leg#|accX_core# INVITE/
>> 100eb870-9e3599cb-13c4-50029-3b71-60de50d0-3b71\#
>> 97.208.30.751120+1+31850054+b8c0a68/
>> 100f7670-9e3599cb-13c4-50029-3b71-3c625412-3b71 200 O á=ÃN
>> |accX_created#Ã=ÃN|
>>
>> --- Jayesh
>>
>> On Wed, Dec 7, 2011 at 4:00 PM, Razvan Crainea <
>> razvancrai...@opensips.org> wrote:
>>
>>>  Hi, Jayesh!
>>>
>>> And what is the string in the database? You can see it in the database
>>> after you kill opensips with the following command:
>>>
>>> select vars from dialog;
>>>
>>>
>>> Regards,
>>>
>>> --
>>> Răzvan Crainea
>>> OpenSIPS Developer
>>>
>>>
>>>   On 12/07/2011 12:24 PM, Jayesh Nambiar wrote:
>>>
>>> Hi Razvan,
>>> Applied the patch and re-tested it. Here the logs that you are
>>> interested in specifically:
>>>
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: Dumping var name:  value: <#026>
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: compare char 22 - 0 - 11
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: compare char 0 - 1 - 12
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: compare char 0 - 2 - 13
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: compare char 0 - 3 - 14
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: Serialized string  (16)
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 0) char: a hex: 61
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 1) char: c hex: 63
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 2) char: c hex: 63
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 3) char: X hex: 58
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 4) char: _ hex: 5F
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 5) char: f hex: 66
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 6) char: l hex: 6C
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 7) char: a hex: 61
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 8) char: g hex: 67
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 9) char: s hex: 73
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 10) char: # hex: 23
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 11) char: #026 hex: 16
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 12) char: #000 hex: 00
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 13) char: #000 hex: 00
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 14) char: #000 hex: 00
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: 15) char: | hex: 7C
>>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>>> DBG:dialog:write_pair: Dumping var name:  value: <(>
>>>
>>> Apart from this, I have pasted everything in syslog after opensips
>>> shutdown in the paste-bin here:
>>> http://pastebin.com/gx0ZxFLb
>>>
>>> Let me know if there is anything more to test.
>>>
>>> --- Jayesh
>>>
>>> On Wed, Dec 7, 2011 at 3:36 PM, Razvan Crainea <
>>> razvancrai...@opensips.org> wrote:
>>>
  Sorr, I forgot to attach it. Here it is.


 Regards,

 --
 Răzvan Crainea
 

Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-08 Thread Ryan Bullock
Awesome information. Dialogs seem to persist over a restart, however I
am not sure if they are accounting. I will do a switch back to the
defaults, better safe than sorry.

Thanks,

Ryan

2011/12/8 Razvan Crainea :
> Hi, Ryan!
>
> Unfortunately it won't work. The problem is that the mysql library detects
> both VARCHAR and VARBINARY as string types. Only BLOB and TEXT are mapped as
> binary objects. You can find more information here[1].
> As far as I know, only the CDR accounting can generate binary data in dialog
> variables, so if you don't use this feature you can leave it as it is for
> now. But if you find any problems related to dialog persistence over restart
> I strongly advise you to change your columns type to the default ones.
>
> [1] http://dev.mysql.com/doc/refman/5.0/en/c-api-data-structures.html
>
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/07/2011 08:40 PM, Ryan Bullock wrote:
>
> Could a VARBINARY be used here instead?
>
> We actually use a memory table for the dialog table to reduce load on
> our disk and it does not support BLOB or TEXT, so instead we changed
> it to a large VARCHAR. The mysql docs suggest you can treat a TEXT the
> same as a VARCHAR, but obviously there are differences.
>
>
> Regards,
>
> Ryan
>
>
> On Wed, Dec 7, 2011 at 9:51 AM, Jayesh Nambiar 
> wrote:
>
> Hi Razvan,
> This actually solved the problem. Thank you very much. It was defined as
> VARCHAR instead of TEXT.
> Thank you very much for all the efforts. Really appreciate it. Need to get
> hold of my DB guy for the stupid mistake !!
>
> --- Jayesh
>
>
> On Wed, Dec 7, 2011 at 8:13 PM, Razvan Crainea 
> wrote:
>
> Hi, Jayesh!
>
> Can you check in your mysql database if the vars column from the dialog
> table is declared as TEXT or BLOB and not CHAR? If not, please change your
> column into BLOB:
>
> ALTER TABLE dialog CHANGE vars vars BLOB;
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/07/2011 02:27 PM, Jayesh Nambiar wrote:
>
> Hi Razwan,
>
> This is the pastebin of logs after shutdown:
> http://pastebin.com/tvmrSqwB
>
> This is the pastebin of logs after start which is huge:
> http://pastebin.com/C6K4Jt5y
>
> --- Jayesh
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-08 Thread Razvan Crainea

Hi, Ryan!

Unfortunately it won't work. The problem is that the mysql library 
detects both VARCHAR and VARBINARY as string types. Only BLOB and TEXT 
are mapped as binary objects. You can find more information here[1].
As far as I know, only the CDR accounting can generate binary data in 
dialog variables, so if you don't use this feature you can leave it as 
it is for now. But if you find any problems related to dialog 
persistence over restart I strongly advise you to change your columns 
type to the default ones.


[1] http://dev.mysql.com/doc/refman/5.0/en/c-api-data-structures.html

Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 08:40 PM, Ryan Bullock wrote:

Could a VARBINARY be used here instead?

We actually use a memory table for the dialog table to reduce load on
our disk and it does not support BLOB or TEXT, so instead we changed
it to a large VARCHAR. The mysql docs suggest you can treat a TEXT the
same as a VARCHAR, but obviously there are differences.


Regards,

Ryan


On Wed, Dec 7, 2011 at 9:51 AM, Jayesh Nambiar  wrote:

Hi Razvan,
This actually solved the problem. Thank you very much. It was defined as
VARCHAR instead of TEXT.
Thank you very much for all the efforts. Really appreciate it. Need to get
hold of my DB guy for the stupid mistake !!

--- Jayesh


On Wed, Dec 7, 2011 at 8:13 PM, Razvan Crainea
wrote:

Hi, Jayesh!

Can you check in your mysql database if the vars column from the dialog
table is declared as TEXT or BLOB and not CHAR? If not, please change your
column into BLOB:

ALTER TABLE dialog CHANGE vars vars BLOB;

Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 02:27 PM, Jayesh Nambiar wrote:

Hi Razwan,

This is the pastebin of logs after shutdown:
http://pastebin.com/tvmrSqwB

This is the pastebin of logs after start which is huge:
http://pastebin.com/C6K4Jt5y

--- Jayesh



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Ryan Bullock
Could a VARBINARY be used here instead?

We actually use a memory table for the dialog table to reduce load on
our disk and it does not support BLOB or TEXT, so instead we changed
it to a large VARCHAR. The mysql docs suggest you can treat a TEXT the
same as a VARCHAR, but obviously there are differences.


Regards,

Ryan


On Wed, Dec 7, 2011 at 9:51 AM, Jayesh Nambiar  wrote:
> Hi Razvan,
> This actually solved the problem. Thank you very much. It was defined as
> VARCHAR instead of TEXT.
> Thank you very much for all the efforts. Really appreciate it. Need to get
> hold of my DB guy for the stupid mistake !!
>
> --- Jayesh
>
>
> On Wed, Dec 7, 2011 at 8:13 PM, Razvan Crainea 
> wrote:
>>
>> Hi, Jayesh!
>>
>> Can you check in your mysql database if the vars column from the dialog
>> table is declared as TEXT or BLOB and not CHAR? If not, please change your
>> column into BLOB:
>>
>> ALTER TABLE dialog CHANGE vars vars BLOB;
>>
>> Regards,
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Developer
>>
>>
>> On 12/07/2011 02:27 PM, Jayesh Nambiar wrote:
>>>
>>> Hi Razwan,
>>>
>>> This is the pastebin of logs after shutdown:
>>> http://pastebin.com/tvmrSqwB
>>>
>>> This is the pastebin of logs after start which is huge:
>>> http://pastebin.com/C6K4Jt5y
>>>
>>> --- Jayesh
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Jayesh Nambiar
Hi Razvan,
This actually solved the problem. Thank you very much. It was defined as
VARCHAR instead of TEXT.
Thank you very much for all the efforts. Really appreciate it. Need to get
hold of my DB guy for the stupid mistake !!

--- Jayesh

On Wed, Dec 7, 2011 at 8:13 PM, Razvan Crainea
wrote:

> Hi, Jayesh!
>
> Can you check in your mysql database if the vars column from the dialog
> table is declared as TEXT or BLOB and not CHAR? If not, please change your
> column into BLOB:
>
> ALTER TABLE dialog CHANGE vars vars BLOB;
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/07/2011 02:27 PM, Jayesh Nambiar wrote:
>
>> Hi Razwan,
>>
>> This is the pastebin of logs after shutdown:
>> http://pastebin.com/tvmrSqwB
>>
>> This is the pastebin of logs after start which is huge:
>> http://pastebin.com/C6K4Jt5y
>>
>> --- Jayesh
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Razvan Crainea

Hi, Jayesh!

Can you check in your mysql database if the vars column from the dialog 
table is declared as TEXT or BLOB and not CHAR? If not, please change 
your column into BLOB:


ALTER TABLE dialog CHANGE vars vars BLOB;

Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 02:27 PM, Jayesh Nambiar wrote:

Hi Razwan,
This is the pastebin of logs after shutdown:
http://pastebin.com/tvmrSqwB

This is the pastebin of logs after start which is huge:
http://pastebin.com/C6K4Jt5y

--- Jayesh


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Razvan Crainea

Hi, Jayesh!

I need the logs after opensips restarts. The result might also be pretty 
large.


Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 02:14 PM, Jayesh Nambiar wrote:

Hi Razwan,
I have applied the patch and made it working. Do you still only need 
the logs after opensips shutdown or also the logs after opensips restarts.


--- Jayesh


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Jayesh Nambiar
Hi Razwan,
I have applied the patch and made it working. Do you still only need the
logs after opensips shutdown or also the logs after opensips restarts.

--- Jayesh

On Wed, Dec 7, 2011 at 4:35 PM, Razvan Crainea
wrote:

>  Hi, Jayesh!
>
> It seems like the problem appears while parsing the string got from the
> database, so after opensips is restarted. The patch attached should give us
> more information about the error.
>
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/07/2011 12:37 PM, Jayesh Nambiar wrote:
>
> This is the string what I see when I query the dialog table for vars:
>
> accX_flags#   |accX_db#(  2 1
>  11 1002
>  12013386166
>  919833171405 0 203.153.53.158 203.153.53.136 0 17 0 2 IP India - Mobile
> 919 9198 2 1 2 4 0.0150 0.0130 0 0. 0.0226 1. 6 1 6 1 1 2 2 2
>  Aal Izz Well
>  Aal Izz Well 1 3 1.2.3.4|accX_leg#|accX_core# INVITE/
> 100eb870-9e3599cb-13c4-50029-3b71-60de50d0-3b71\#
> 97.208.30.751120+1+31850054+b8c0a68/
> 100f7670-9e3599cb-13c4-50029-3b71-3c625412-3b71 200 O á=ÃN
> |accX_created#Ã=ÃN|
>
> --- Jayesh
>
> On Wed, Dec 7, 2011 at 4:00 PM, Razvan Crainea  > wrote:
>
>>  Hi, Jayesh!
>>
>> And what is the string in the database? You can see it in the database
>> after you kill opensips with the following command:
>>
>> select vars from dialog;
>>
>>
>> Regards,
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Developer
>>
>>
>>   On 12/07/2011 12:24 PM, Jayesh Nambiar wrote:
>>
>> Hi Razvan,
>> Applied the patch and re-tested it. Here the logs that you are interested
>> in specifically:
>>
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: Dumping var name:  value: <#026>
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: compare char 22 - 0 - 11
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: compare char 0 - 1 - 12
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: compare char 0 - 2 - 13
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: compare char 0 - 3 - 14
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: Serialized string  (16)
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 0) char: a hex: 61
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 1) char: c hex: 63
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 2) char: c hex: 63
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 3) char: X hex: 58
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 4) char: _ hex: 5F
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 5) char: f hex: 66
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 6) char: l hex: 6C
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 7) char: a hex: 61
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 8) char: g hex: 67
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 9) char: s hex: 73
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 10) char: # hex: 23
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 11) char: #026 hex: 16
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 12) char: #000 hex: 00
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 13) char: #000 hex: 00
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 14) char: #000 hex: 00
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: 15) char: | hex: 7C
>> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
>> DBG:dialog:write_pair: Dumping var name:  value: <(>
>>
>> Apart from this, I have pasted everything in syslog after opensips
>> shutdown in the paste-bin here:
>> http://pastebin.com/gx0ZxFLb
>>
>> Let me know if there is anything more to test.
>>
>> --- Jayesh
>>
>> On Wed, Dec 7, 2011 at 3:36 PM, Razvan Crainea <
>> razvancrai...@opensips.org> wrote:
>>
>>>  Sorr, I forgot to attach it. Here it is.
>>>
>>>
>>> Regards,
>>>
>>> --
>>> Răzvan Crainea
>>> OpenSIPS Developer
>>>
>>>
>>>   On 12/07/2011 11:59 AM, Jayesh Nambiar wrote:
>>>
>>> Hi Razvan,
>>> I don't see the patch attached !!
>>>
>>> --- Jayesh
>>>
>>> On Wed, Dec 7, 2011 at 2:57 PM, Razvan Crainea <
>>> razvancrai...@opensips.org> wrote:
>>>
  Hi, Jayesh !

 The root of the problem is the accX_flags dialog variable isn't
 properly serialized. What I'm trying to find out is why this happens,
 that's why I will need some extra debug as I can't figure out the problem
 there. So please apply this last patch and try again. It should be applied
 after the previous patch I've sent yo

Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Razvan Crainea

Hi, Jayesh!

It seems like the problem appears while parsing the string got from the 
database, so after opensips is restarted. The patch attached should give 
us more information about the error.


Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 12:37 PM, Jayesh Nambiar wrote:

This is the string what I see when I query the dialog table for vars:

accX_flags#   |accX_db#(  2 1
 11 1002
 12013386166
 919833171405 0 203.153.53.158 203.153.53.136 0 17 0 2 IP India - 
Mobile 919 9198 2 1 2 4 0.0150 0.0130 0 0. 0.0226 1. 6 1 6 1 1 
2 2 2

 Aal Izz Well
 Aal Izz Well 1 3 1.2.3.4|accX_leg#|accX_core# INVITE/ 
100eb870-9e3599cb-13c4-50029-3b71-60de50d0-3b71\# 
97.208.30.751120+1+31850054+b8c0a68/ 
100f7670-9e3599cb-13c4-50029-3b71-3c625412-3b71 200 O á=ÃN
|accX_created#Ã=ÃN|


--- Jayesh

On Wed, Dec 7, 2011 at 4:00 PM, Razvan Crainea 
mailto:razvancrai...@opensips.org>> wrote:


Hi, Jayesh!

And what is the string in the database? You can see it in the
database after you kill opensips with the following command:

select vars from dialog;


Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 12:24 PM, Jayesh Nambiar wrote:

Hi Razvan,
Applied the patch and re-tested it. Here the logs that you are
interested in specifically:

Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: Dumping var name:  value: <#026>
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: compare char 22 - 0 - 11
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: compare char 0 - 1 - 12
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: compare char 0 - 2 - 13
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: compare char 0 - 3 - 14
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: Serialized string  (16)
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 0) char: a hex: 61
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 1) char: c hex: 63
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 2) char: c hex: 63
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 3) char: X hex: 58
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 4) char: _ hex: 5F
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 5) char: f hex: 66
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 6) char: l hex: 6C
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 7) char: a hex: 61
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 8) char: g hex: 67
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 9) char: s hex: 73
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 10) char: # hex: 23
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 11) char: #026 hex: 16
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 12) char: #000 hex: 00
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 13) char: #000 hex: 00
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 14) char: #000 hex: 00
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: 15) char: | hex: 7C
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]:
DBG:dialog:write_pair: Dumping var name:  value: <(>

Apart from this, I have pasted everything in syslog after
opensips shutdown in the paste-bin here:
http://pastebin.com/gx0ZxFLb

Let me know if there is anything more to test.

--- Jayesh

On Wed, Dec 7, 2011 at 3:36 PM, Razvan Crainea
mailto:razvancrai...@opensips.org>>
wrote:

Sorr, I forgot to attach it. Here it is.


Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 11:59 AM, Jayesh Nambiar wrote:

Hi Razvan,
I don't see the patch attached !!

--- Jayesh

On Wed, Dec 7, 2011 at 2:57 PM, Razvan Crainea
mailto:razvancrai...@opensips.org>> wrote:

Hi, Jayesh !

The root of the problem is the accX_flags dialog
variable isn't properly serialized. What I'm trying to
find out is why this happens, that's why I will need
some extra debug as I can't figure out the problem
there. So please apply this last patch and try again. It
should be applied after the previous patch I've sent
you, so you won't need another fresh checkout.
This time there will be a lot of dumped info in th

Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Jayesh Nambiar
This is the string what I see when I query the dialog table for vars:

accX_flags#   |accX_db#(  2 1
 11 1002
 12013386166
 919833171405 0 203.153.53.158 203.153.53.136 0 17 0 2 IP India - Mobile
919 9198 2 1 2 4 0.0150 0.0130 0 0. 0.0226 1. 6 1 6 1 1 2 2 2
 Aal Izz Well
 Aal Izz Well 1 3 1.2.3.4|accX_leg#|accX_core# INVITE/
100eb870-9e3599cb-13c4-50029-3b71-60de50d0-3b71\#
97.208.30.751120+1+31850054+b8c0a68/
100f7670-9e3599cb-13c4-50029-3b71-3c625412-3b71 200 O á=ÃN
|accX_created#Ã=ÃN|

--- Jayesh

On Wed, Dec 7, 2011 at 4:00 PM, Razvan Crainea
wrote:

>  Hi, Jayesh!
>
> And what is the string in the database? You can see it in the database
> after you kill opensips with the following command:
>
> select vars from dialog;
>
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/07/2011 12:24 PM, Jayesh Nambiar wrote:
>
> Hi Razvan,
> Applied the patch and re-tested it. Here the logs that you are interested
> in specifically:
>
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> Dumping var name:  value: <#026>
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> compare char 22 - 0 - 11
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> compare char 0 - 1 - 12
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> compare char 0 - 2 - 13
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> compare char 0 - 3 - 14
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> Serialized string  (16)
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 0) char: a hex: 61
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 1) char: c hex: 63
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 2) char: c hex: 63
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 3) char: X hex: 58
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 4) char: _ hex: 5F
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 5) char: f hex: 66
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 6) char: l hex: 6C
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 7) char: a hex: 61
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 8) char: g hex: 67
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 9) char: s hex: 73
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 10) char: # hex: 23
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 11) char: #026 hex: 16
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 12) char: #000 hex: 00
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 13) char: #000 hex: 00
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 14) char: #000 hex: 00
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> 15) char: | hex: 7C
> Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
> Dumping var name:  value: <(>
>
> Apart from this, I have pasted everything in syslog after opensips
> shutdown in the paste-bin here:
> http://pastebin.com/gx0ZxFLb
>
> Let me know if there is anything more to test.
>
> --- Jayesh
>
> On Wed, Dec 7, 2011 at 3:36 PM, Razvan Crainea  > wrote:
>
>>  Sorr, I forgot to attach it. Here it is.
>>
>>
>> Regards,
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Developer
>>
>>
>>   On 12/07/2011 11:59 AM, Jayesh Nambiar wrote:
>>
>> Hi Razvan,
>> I don't see the patch attached !!
>>
>> --- Jayesh
>>
>> On Wed, Dec 7, 2011 at 2:57 PM, Razvan Crainea <
>> razvancrai...@opensips.org> wrote:
>>
>>>  Hi, Jayesh !
>>>
>>> The root of the problem is the accX_flags dialog variable isn't properly
>>> serialized. What I'm trying to find out is why this happens, that's why I
>>> will need some extra debug as I can't figure out the problem there. So
>>> please apply this last patch and try again. It should be applied after the
>>> previous patch I've sent you, so you won't need another fresh checkout.
>>> This time there will be a lot of dumped info in the log, so I would
>>> really appreciate if you could send them over pastebin. The only part that
>>> I will be interested in is between these lines:
>>>
>>>
>>> DBG:dialog:write_pair: Dumping var name:  value: <#026>
>>>
>>>  and
>>>
>>>
>>> DBG:dialog:write_pair: Dumping var name:  value: <(>
>>>
>>>  Thank you very much for testing!
>>>  Regards,
>>>
>>> --
>>> Răzvan Crainea
>>> OpenSIPS Developer
>>>
>>>
>>>   On 12/06/2011 07:57 PM, Jayesh Nambiar wrote:
>>>
>>> Hi Razvan,
>>> I just did a fresh download from
>>> http://opensips.org/pub/opensips/latest/src/. I did apply the patch
>>> successfully and I 

Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Razvan Crainea

Hi, Jayesh!

And what is the string in the database? You can see it in the database 
after you kill opensips with the following command:


select vars from dialog;

Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 12:24 PM, Jayesh Nambiar wrote:

Hi Razvan,
Applied the patch and re-tested it. Here the logs that you are 
interested in specifically:


Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: Dumping var name:  value: <#026>
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: compare char 22 - 0 - 11
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: compare char 0 - 1 - 12
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: compare char 0 - 2 - 13
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: compare char 0 - 3 - 14
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: Serialized string  (16)
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 0) char: a hex: 61
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 1) char: c hex: 63
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 2) char: c hex: 63
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 3) char: X hex: 58
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 4) char: _ hex: 5F
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 5) char: f hex: 66
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 6) char: l hex: 6C
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 7) char: a hex: 61
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 8) char: g hex: 67
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 9) char: s hex: 73
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 10) char: # hex: 23
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 11) char: #026 hex: 16
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 12) char: #000 hex: 00
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 13) char: #000 hex: 00
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 14) char: #000 hex: 00
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: 15) char: | hex: 7C
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: 
DBG:dialog:write_pair: Dumping var name:  value: <(>


Apart from this, I have pasted everything in syslog after opensips 
shutdown in the paste-bin here:

http://pastebin.com/gx0ZxFLb

Let me know if there is anything more to test.

--- Jayesh

On Wed, Dec 7, 2011 at 3:36 PM, Razvan Crainea 
mailto:razvancrai...@opensips.org>> wrote:


Sorr, I forgot to attach it. Here it is.


Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 11:59 AM, Jayesh Nambiar wrote:

Hi Razvan,
I don't see the patch attached !!

--- Jayesh

On Wed, Dec 7, 2011 at 2:57 PM, Razvan Crainea
mailto:razvancrai...@opensips.org>>
wrote:

Hi, Jayesh !

The root of the problem is the accX_flags dialog variable
isn't properly serialized. What I'm trying to find out is why
this happens, that's why I will need some extra debug as I
can't figure out the problem there. So please apply this last
patch and try again. It should be applied after the previous
patch I've sent you, so you won't need another fresh checkout.
This time there will be a lot of dumped info in the log, so I
would really appreciate if you could send them over pastebin.
The only part that I will be interested in is between these
lines:


DBG:dialog:write_pair: Dumping var name:  value:
<#026>

and


DBG:dialog:write_pair: Dumping var name:  value: <(>

Thank you very much for testing!
Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/06/2011 07:57 PM, Jayesh Nambiar wrote:

Hi Razvan,
I just did a fresh download from
http://opensips.org/pub/opensips/latest/src/. I did apply
the patch successfully and I still have the problem of CDR
not being recorded after restart. Here is the syslog pasted
after opensips was being shut down:

Dec  6 20:20:13 dev /usr/local/sbin/opensips[
15700]: DBG:dialog:dialog_update_db: inserting new dialog
0x7f3d323bd5f8
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Dumping var name:  value:
<#026>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Serialized string  (16)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG

Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Jayesh Nambiar
Hi Razvan,
Applied the patch and re-tested it. Here the logs that you are interested
in specifically:

Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
Dumping var name:  value: <#026>
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
compare char 22 - 0 - 11
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
compare char 0 - 1 - 12
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
compare char 0 - 2 - 13
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
compare char 0 - 3 - 14
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
Serialized string  (16)
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
0) char: a hex: 61
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
1) char: c hex: 63
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
2) char: c hex: 63
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
3) char: X hex: 58
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
4) char: _ hex: 5F
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
5) char: f hex: 66
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
6) char: l hex: 6C
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
7) char: a hex: 61
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
8) char: g hex: 67
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
9) char: s hex: 73
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
10) char: # hex: 23
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
11) char: #026 hex: 16
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
12) char: #000 hex: 00
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
13) char: #000 hex: 00
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
14) char: #000 hex: 00
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
15) char: | hex: 7C
Dec  7 15:50:33 dev /usr/local/sbin/opensips[8011]: DBG:dialog:write_pair:
Dumping var name:  value: <(>

Apart from this, I have pasted everything in syslog after opensips shutdown
in the paste-bin here:
http://pastebin.com/gx0ZxFLb

Let me know if there is anything more to test.

--- Jayesh

On Wed, Dec 7, 2011 at 3:36 PM, Razvan Crainea
wrote:

>  Sorr, I forgot to attach it. Here it is.
>
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/07/2011 11:59 AM, Jayesh Nambiar wrote:
>
> Hi Razvan,
> I don't see the patch attached !!
>
> --- Jayesh
>
> On Wed, Dec 7, 2011 at 2:57 PM, Razvan Crainea  > wrote:
>
>>  Hi, Jayesh !
>>
>> The root of the problem is the accX_flags dialog variable isn't properly
>> serialized. What I'm trying to find out is why this happens, that's why I
>> will need some extra debug as I can't figure out the problem there. So
>> please apply this last patch and try again. It should be applied after the
>> previous patch I've sent you, so you won't need another fresh checkout.
>> This time there will be a lot of dumped info in the log, so I would
>> really appreciate if you could send them over pastebin. The only part that
>> I will be interested in is between these lines:
>>
>>
>> DBG:dialog:write_pair: Dumping var name:  value: <#026>
>>
>>  and
>>
>>
>> DBG:dialog:write_pair: Dumping var name:  value: <(>
>>
>>  Thank you very much for testing!
>>  Regards,
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Developer
>>
>>
>>   On 12/06/2011 07:57 PM, Jayesh Nambiar wrote:
>>
>> Hi Razvan,
>> I just did a fresh download from
>> http://opensips.org/pub/opensips/latest/src/. I did apply the patch
>> successfully and I still have the problem of CDR not being recorded after
>> restart. Here is the syslog pasted after opensips was being shut down:
>>
>> Dec  6 20:20:13 dev /usr/local/sbin/opensips[
>> 15700]: DBG:dialog:dialog_update_db: inserting new dialog 0x7f3d323bd5f8
>> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
>> DBG:dialog:write_pair: Dumping var name:  value: <#026>
>> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
>> DBG:dialog:write_pair: Serialized string  (16)
>> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
>> DBG:dialog:write_pair: Dumping var name:  value: <(>
>> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
>> DBG:dialog:write_pair: Serialized string  (263)
>> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
>> DBG:dialog:write_pair: Dumping var name:  value: <>
>> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
>> DBG:dialog:write_pair: Serialized string  (14)
>> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
>> DBG:dialog:write_pair: Dumping var name:  value: <#006>
>> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
>> DBG:

Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Razvan Crainea

Sorr, I forgot to attach it. Here it is.

Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/07/2011 11:59 AM, Jayesh Nambiar wrote:

Hi Razvan,
I don't see the patch attached !!

--- Jayesh

On Wed, Dec 7, 2011 at 2:57 PM, Razvan Crainea 
mailto:razvancrai...@opensips.org>> wrote:


Hi, Jayesh !

The root of the problem is the accX_flags dialog variable isn't
properly serialized. What I'm trying to find out is why this
happens, that's why I will need some extra debug as I can't figure
out the problem there. So please apply this last patch and try
again. It should be applied after the previous patch I've sent
you, so you won't need another fresh checkout.
This time there will be a lot of dumped info in the log, so I
would really appreciate if you could send them over pastebin. The
only part that I will be interested in is between these lines:


DBG:dialog:write_pair: Dumping var name:  value: <#026>

and


DBG:dialog:write_pair: Dumping var name:  value: <(>

Thank you very much for testing!
Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/06/2011 07:57 PM, Jayesh Nambiar wrote:

Hi Razvan,
I just did a fresh download from
http://opensips.org/pub/opensips/latest/src/. I did apply the
patch successfully and I still have the problem of CDR not being
recorded after restart. Here is the syslog pasted after opensips
was being shut down:

Dec  6 20:20:13 dev /usr/local/sbin/opensips[
15700]: DBG:dialog:dialog_update_db: inserting new dialog
0x7f3d323bd5f8
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Dumping var name:  value: <#026>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Serialized string  (16)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Dumping var name:  value: <(>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Serialized string  (263)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Dumping var name:  value: <>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Serialized string  (14)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Dumping var name:  value: <#006>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: escaping char 53
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Serialized string  (165)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Dumping var name:  value:
<<95>+ÃN>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Serialized string +ÃN> (22)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_dialog_vars: var string is (480)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Dumping var name:  value:
<1002>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Serialized string  (21)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Dumping var name:  value:
<1003>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Serialized string  (21)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Dumping var name:  value:
<1007>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_pair: Serialized string  (21)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_dialog_profiles: profile string is
(63)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:db_mysql:has_stmt_ctx: ctx found for dialog
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:db_mysql:db_mysql_do_prepared_query: conn=0x810858
(tail=8454488) MC=0x8101b8
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:db_mysql:db_mysql_do_prepared_query: set values for the
statement run

I hope this will help you figure out something more relevant.


--- Jayesh


On Tue, Dec 6, 2011 at 7:56 PM, Razvan Crainea
mailto:razvancrai...@opensips.org>>
wrote:

Hi, Jayesh!

Can you post your dlg_db_handler.c file on pastebin? I think
you are using an old version of the dialog module, and that's
why you have this problem.


Regards,

--
Răzvan Crainea
OpenSIPS Developer



--- modules/dialog/dlg_db_handler.c	2011-12-06 15:48:48.112479173 +0200
+++ modules/dialog/dlg_db_handler.c	2011-12-07 11:22:38.332347513 +0200
@@ -799,6 +799,7 @@
 	}
 	b[j++] = '#';
 	for( i=0 ; val && ilen ; i++) {
+		LM_DBG("compare char %d - %d - %d\n", val->s[i], i, j);
 		if (val->s[i]=='|' || val->s[i]=='#' || val->s[i]=='\\') {
 			b[j++] = '\\';
 			LM_DBG("escaping char %d\

Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Jayesh Nambiar
Hi Razvan,
I don't see the patch attached !!

--- Jayesh

On Wed, Dec 7, 2011 at 2:57 PM, Razvan Crainea
wrote:

>  Hi, Jayesh !
>
> The root of the problem is the accX_flags dialog variable isn't properly
> serialized. What I'm trying to find out is why this happens, that's why I
> will need some extra debug as I can't figure out the problem there. So
> please apply this last patch and try again. It should be applied after the
> previous patch I've sent you, so you won't need another fresh checkout.
> This time there will be a lot of dumped info in the log, so I would really
> appreciate if you could send them over pastebin. The only part that I will
> be interested in is between these lines:
>
>
> DBG:dialog:write_pair: Dumping var name:  value: <#026>
>
> and
>
>
> DBG:dialog:write_pair: Dumping var name:  value: <(>
>
> Thank you very much for testing!
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/06/2011 07:57 PM, Jayesh Nambiar wrote:
>
> Hi Razvan,
> I just did a fresh download from
> http://opensips.org/pub/opensips/latest/src/. I did apply the patch
> successfully and I still have the problem of CDR not being recorded after
> restart. Here is the syslog pasted after opensips was being shut down:
>
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[
> 15700]: DBG:dialog:dialog_update_db: inserting new dialog 0x7f3d323bd5f8
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Dumping var name:  value: <#026>
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Serialized string  (16)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Dumping var name:  value: <(>
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Serialized string  (263)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Dumping var name:  value: <>
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Serialized string  (14)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Dumping var name:  value: <#006>
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: escaping char 53
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Serialized string  (165)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Dumping var name:  value: <<95>+ÃN>
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Serialized string +ÃN> (22)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_dialog_vars: var string is (480)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Dumping var name:  value: <1002>
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Serialized string  (21)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Dumping var name:  value: <1003>
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Serialized string  (21)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Dumping var name:  value: <1007>
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_pair: Serialized string  (21)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:dialog:write_dialog_profiles: profile string is
> (63)
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:db_mysql:has_stmt_ctx: ctx found for dialog
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:db_mysql:db_mysql_do_prepared_query: conn=0x810858 (tail=8454488)
> MC=0x8101b8
> Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
> DBG:db_mysql:db_mysql_do_prepared_query: set values for the statement run
>
> I hope this will help you figure out something more relevant.
>
>
> --- Jayesh
>
>
> On Tue, Dec 6, 2011 at 7:56 PM, Razvan Crainea  > wrote:
>
>>  Hi, Jayesh!
>>
>> Can you post your dlg_db_handler.c file on pastebin? I think you are
>> using an old version of the dialog module, and that's why you have this
>> problem.
>>
>>
>> Regards,
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Developer
>>
>>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-07 Thread Razvan Crainea

Hi, Jayesh !

The root of the problem is the accX_flags dialog variable isn't properly 
serialized. What I'm trying to find out is why this happens, that's why 
I will need some extra debug as I can't figure out the problem there. So 
please apply this last patch and try again. It should be applied after 
the previous patch I've sent you, so you won't need another fresh checkout.
This time there will be a lot of dumped info in the log, so I would 
really appreciate if you could send them over pastebin. The only part 
that I will be interested in is between these lines:


DBG:dialog:write_pair: Dumping var name:  value: <#026>

and

DBG:dialog:write_pair: Dumping var name:  value: <(>

Thank you very much for testing!
Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/06/2011 07:57 PM, Jayesh Nambiar wrote:

Hi Razvan,
I just did a fresh download from 
http://opensips.org/pub/opensips/latest/src/. I did apply the patch 
successfully and I still have the problem of CDR not being recorded 
after restart. Here is the syslog pasted after opensips was being shut 
down:


Dec  6 20:20:13 dev /usr/local/sbin/opensips[
15700]: DBG:dialog:dialog_update_db: inserting new dialog 0x7f3d323bd5f8
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Dumping var name:  value: <#026>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Serialized string  (16)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Dumping var name:  value: <(>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Serialized string  (263)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Dumping var name:  value: <>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Serialized string  (14)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Dumping var name:  value: <#006>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: escaping char 53
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Serialized string  (165)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Dumping var name:  value: <<95>+ÃN>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Serialized string +ÃN> (22)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_dialog_vars: var string is (480)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Dumping var name:  value: <1002>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Serialized string  (21)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Dumping var name:  value: <1003>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Serialized string  (21)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Dumping var name:  value: <1007>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_pair: Serialized string  (21)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:dialog:write_dialog_profiles: profile string is 
(63)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:db_mysql:has_stmt_ctx: ctx found for dialog
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:db_mysql:db_mysql_do_prepared_query: conn=0x810858 (tail=8454488) 
MC=0x8101b8
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: 
DBG:db_mysql:db_mysql_do_prepared_query: set values for the statement run


I hope this will help you figure out something more relevant.


--- Jayesh


On Tue, Dec 6, 2011 at 7:56 PM, Razvan Crainea 
mailto:razvancrai...@opensips.org>> wrote:


Hi, Jayesh!

Can you post your dlg_db_handler.c file on pastebin? I think you
are using an old version of the dialog module, and that's why you
have this problem.


Regards,

--
Răzvan Crainea
OpenSIPS Developer

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] cdr accounting on opensips restart

2011-12-06 Thread Jayesh Nambiar
Hi Razvan,
I just did a fresh download from
http://opensips.org/pub/opensips/latest/src/. I did apply the patch
successfully and I still have the problem of CDR not being recorded after
restart. Here is the syslog pasted after opensips was being shut down:

Dec  6 20:20:13 dev /usr/local/sbin/opensips[
15700]: DBG:dialog:dialog_update_db: inserting new dialog 0x7f3d323bd5f8
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Dumping var name:  value: <#026>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Serialized string  (16)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Dumping var name:  value: <(>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Serialized string  (263)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Dumping var name:  value: <>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Serialized string  (14)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Dumping var name:  value: <#006>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
escaping char 53
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Serialized string  (165)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Dumping var name:  value: <<95>+ÃN>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Serialized string +ÃN> (22)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_dialog_vars: var string is (480)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Dumping var name:  value: <1002>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Serialized string  (21)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Dumping var name:  value: <1003>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Serialized string  (21)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Dumping var name:  value: <1007>
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]: DBG:dialog:write_pair:
Serialized string  (21)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:dialog:write_dialog_profiles: profile string is
(63)
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:db_mysql:has_stmt_ctx: ctx found for dialog
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:db_mysql:db_mysql_do_prepared_query: conn=0x810858 (tail=8454488)
MC=0x8101b8
Dec  6 20:20:13 dev /usr/local/sbin/opensips[15700]:
DBG:db_mysql:db_mysql_do_prepared_query: set values for the statement run

I hope this will help you figure out something more relevant.


--- Jayesh


On Tue, Dec 6, 2011 at 7:56 PM, Razvan Crainea
wrote:

>  Hi, Jayesh!
>
> Can you post your dlg_db_handler.c file on pastebin? I think you are using
> an old version of the dialog module, and that's why you have this problem.
>
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-06 Thread Jayesh Nambiar
Hi Razvan,
I am not able to patch. I get the following:
patching file dlg_db_handler.c
Hunk #1 FAILED at 789.
Hunk #2 FAILED at 796.
2 out of 2 hunks FAILED -- saving rejects to file dlg_db_handler.c.rej.

This is what I see in dlg_db_handler.c.rej:
--- dlg_db_handler.c(revision 8586)
+++ dlg_db_handler.c(working copy)
@@ -789,6 +789,9 @@
 {
int i,j;

+   LM_DBG("Dumping var name: <%.*s> value: <%.*s>\n",
+   name->len, name->s, val->len, val->s);
+
for( i=0,j=0 ; ilen ; i++) {
if (name->s[i]=='|' || name->s[i]=='#' || name->s[i]=='\\')
b[j++] = '\\';

I must admit that earlier also I was not able to patch properly but looking
at the patch file I just added the line:
LM_DBG("Dumping var name: <%.*s> value: <%.*s>\n",
   name->len, name->s, val->len, val->s);
after int i,j at line 790 in file dlg_db_handler.c and then recompiled.

Anything else I can do for the patch to work properly.

--- Jayesh

On Tue, Dec 6, 2011 at 7:19 PM, Razvan Crainea
wrote:

>  Hi, Jayesh!
>
> Something is really weird there. I've attached attached a new patch done
> against a fresh copy. Can you please try this one?
>
> Thanks and regards!
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/06/2011 01:52 PM, Jayesh Nambiar wrote:
>
> Hi Razvan,
> Here are the logs with Dumping var name:
>
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]:
> DBG:dialog:dialog_update_db: inserting new dialog 0x7fa29f2d0708
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
> Dumping var name:  value: <#026>
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
> Dumping var name:  value: <(>
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
> Dumping var name:  value: <>
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
> Dumping var name:  value: <#006>
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
> Dumping var name:  value: 
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]:
> DBG:dialog:write_dialog_vars: var string is (481)
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
> Dumping var name:  value: <1002>
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
> Dumping var name:  value: <1003>
> Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
> Dumping var name:  value: <1007>
>
> Let me know if this helps.
>
> Thanks,
>
> --- Jayesh
>
>
> On Tue, Dec 6, 2011 at 4:32 PM, Razvan Crainea  > wrote:
>
>>  Hi, Jayesh!
>>
>> Can you please apply the patch I've attached? And then mail me back the
>> log, but this time taken just after OpenSIPS shuts down with an active
>> dialog. The log should contain the following strings:
>>
>> "Dumping var name: "
>>
>> and
>>
>> "var string is <"
>>
>> They should appear before OpenSIPS stops with an active dialog, so
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Developer
>>
>>
>>   On 12/06/2011 12:13 PM, Jayesh Nambiar wrote:
>>
>> Hi Razvan,
>> The logs with debug level 9 are pasted here:
>>
>> After restarting I disconnected the call, the dialog matched perfectly
>> but no CDR record.
>>
>> --- Jayesh
>>
>>
>> On Tue, Dec 6, 2011 at 2:50 PM, Razvan Crainea <
>> razvancrai...@opensips.org> wrote:
>>
>>>  Hi, Jayesh!
>>>
>>> Yes, I will need extra debugging to see what's happening. Can you
>>> send[1] the log in full debugging, taken after OpenSIPS is restarted?
>>>
>>> [1] pastebin.com
>>>
>>>
>>> Regards,
>>>
>>> --
>>> Răzvan Crainea
>>> OpenSIPS Developer
>>>
>>>
>>>   On 12/06/2011 08:13 AM, Jayesh Nambiar wrote:
>>>
>>> Hi Razvan,
>>> The dialogs are definitely loaded on startup and it also matches with
>>> existing dialog. I use this to make sure the dialog is matched in my
>>> script. So even after a restart, I see the Dialog Matched in my syslog.
>>>
>>> if(has_totag()) {
>>>   if(match_dialog()) {
>>>  log(1, "Dialog Matched");
>>>  route(default_relay);
>>>  exit;
>>>   }
>>> }
>>>
>>> But it is just that the cdr insert does not take place after the restart
>>> !!
>>> My debug level was at 3. Do you want more detailed logs to check??
>>>
>>> Thanks,
>>>
>>> --- Jayesh
>>>
>>> On Mon, Dec 5, 2011 at 7:12 PM, Razvan Crainea <
>>> razvancrai...@opensips.org> wrote:
>>>
  Hi Jayesh,

 Can you please check if the dialogs are loaded back after a restart.
 Also, do you see any errors in your log?

 Regards,

 --
 Răzvan Crainea
 OpenSIPS Developer


 On 12/05/2011 02:31 PM, Bogdan-Andrei Iancu wrote:

 Hi Jayesh,

 Razvan is checking the code for you and running some tests.

 Regards,
 Bogdan

 On 12/03/2011 02:49 PM, Jayesh Nambiar wrote:

 Hi Bogdan,
 Just writing to ask if you got a chance to check if this is a bug or
 some error in my config !!


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-06 Thread Razvan Crainea

Hi, Jayesh!

Something is really weird there. I've attached attached a new patch done 
against a fresh copy. Can you please try this one?


Thanks and regards!

--
Răzvan Crainea
OpenSIPS Developer


On 12/06/2011 01:52 PM, Jayesh Nambiar wrote:

Hi Razvan,
Here are the logs with Dumping var name:

Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:dialog_update_db: inserting new dialog 0x7fa29f2d0708
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:write_pair: Dumping var name:  value: <#026>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:write_pair: Dumping var name:  value: <(>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:write_pair: Dumping var name:  value: <>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:write_pair: Dumping var name:  value: <#006>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:write_pair: Dumping var name:  value: 
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:write_dialog_vars: var string is (481)
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:write_pair: Dumping var name:  value: <1002>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:write_pair: Dumping var name:  value: <1003>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: 
DBG:dialog:write_pair: Dumping var name:  value: <1007>


Let me know if this helps.

Thanks,

--- Jayesh


On Tue, Dec 6, 2011 at 4:32 PM, Razvan Crainea 
mailto:razvancrai...@opensips.org>> wrote:


Hi, Jayesh!

Can you please apply the patch I've attached? And then mail me
back the log, but this time taken just after OpenSIPS shuts down
with an active dialog. The log should contain the following strings:

"Dumping var name: "

and

"var string is <"

They should appear before OpenSIPS stops with an active dialog, so

--
Răzvan Crainea
OpenSIPS Developer


On 12/06/2011 12:13 PM, Jayesh Nambiar wrote:

Hi Razvan,
The logs with debug level 9 are pasted here:

After restarting I disconnected the call, the dialog matched
perfectly but no CDR record.

--- Jayesh


On Tue, Dec 6, 2011 at 2:50 PM, Razvan Crainea
mailto:razvancrai...@opensips.org>>
wrote:

Hi, Jayesh!

Yes, I will need extra debugging to see what's happening. Can
you send[1] the log in full debugging, taken after OpenSIPS
is restarted?

[1] pastebin.com 


Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/06/2011 08:13 AM, Jayesh Nambiar wrote:

Hi Razvan,
The dialogs are definitely loaded on startup and it also
matches with existing dialog. I use this to make sure the
dialog is matched in my script. So even after a restart, I
see the Dialog Matched in my syslog.

if(has_totag()) {
  if(match_dialog()) {
 log(1, "Dialog Matched");
 route(default_relay);
 exit;
  }
}

But it is just that the cdr insert does not take place after
the restart !!
My debug level was at 3. Do you want more detailed logs to
check??

Thanks,

--- Jayesh

On Mon, Dec 5, 2011 at 7:12 PM, Razvan Crainea
mailto:razvancrai...@opensips.org>> wrote:

Hi Jayesh,

Can you please check if the dialogs are loaded back
after a restart. Also, do you see any errors in your log?

Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/05/2011 02:31 PM, Bogdan-Andrei Iancu wrote:

Hi Jayesh,

Razvan is checking the code for you and running some tests.

Regards,
Bogdan

On 12/03/2011 02:49 PM, Jayesh Nambiar wrote:

Hi Bogdan,
Just writing to ask if you got a chance to check if
this is a bug or some error in my config !!

Thanks,

--- Jayesh

On Fri, Dec 2, 2011 at 11:23 AM, Jayesh Nambiar
mailto:jayesh.v...@gmail.com>>
wrote:

Hi Bogdan,
The exact version used is 1.7.1 stable release
compiled from src. Output of opensips -V is:
version: opensips 1.7.1-notls (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP,
DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP,
PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE
262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE
65535
poll method support: poll, epoll_lt, epoll_et,
sigio_rt, select.
svnrevision: unknown
@(#) $Id: main.c 8537 2011-11-08 17:02:11Z
bogdan_i

Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-06 Thread Jayesh Nambiar
Hi Razvan,
Here are the logs with Dumping var name:

Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]:
DBG:dialog:dialog_update_db: inserting new dialog 0x7fa29f2d0708
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
Dumping var name:  value: <#026>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
Dumping var name:  value: <(>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
Dumping var name:  value: <>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
Dumping var name:  value: <#006>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
Dumping var name:  value: 
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]:
DBG:dialog:write_dialog_vars: var string is (481)
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
Dumping var name:  value: <1002>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
Dumping var name:  value: <1003>
Dec  6 17:24:13 dev /usr/local/sbin/opensips[1958]: DBG:dialog:write_pair:
Dumping var name:  value: <1007>

Let me know if this helps.

Thanks,

--- Jayesh


On Tue, Dec 6, 2011 at 4:32 PM, Razvan Crainea
wrote:

>  Hi, Jayesh!
>
> Can you please apply the patch I've attached? And then mail me back the
> log, but this time taken just after OpenSIPS shuts down with an active
> dialog. The log should contain the following strings:
>
> "Dumping var name: "
>
> and
>
> "var string is <"
>
> They should appear before OpenSIPS stops with an active dialog, so
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/06/2011 12:13 PM, Jayesh Nambiar wrote:
>
> Hi Razvan,
> The logs with debug level 9 are pasted here:
>
> After restarting I disconnected the call, the dialog matched perfectly but
> no CDR record.
>
> --- Jayesh
>
>
> On Tue, Dec 6, 2011 at 2:50 PM, Razvan Crainea  > wrote:
>
>>  Hi, Jayesh!
>>
>> Yes, I will need extra debugging to see what's happening. Can you send[1]
>> the log in full debugging, taken after OpenSIPS is restarted?
>>
>> [1] pastebin.com
>>
>>
>> Regards,
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Developer
>>
>>
>>   On 12/06/2011 08:13 AM, Jayesh Nambiar wrote:
>>
>> Hi Razvan,
>> The dialogs are definitely loaded on startup and it also matches with
>> existing dialog. I use this to make sure the dialog is matched in my
>> script. So even after a restart, I see the Dialog Matched in my syslog.
>>
>> if(has_totag()) {
>>   if(match_dialog()) {
>>  log(1, "Dialog Matched");
>>  route(default_relay);
>>  exit;
>>   }
>> }
>>
>> But it is just that the cdr insert does not take place after the restart
>> !!
>> My debug level was at 3. Do you want more detailed logs to check??
>>
>> Thanks,
>>
>> --- Jayesh
>>
>> On Mon, Dec 5, 2011 at 7:12 PM, Razvan Crainea <
>> razvancrai...@opensips.org> wrote:
>>
>>>  Hi Jayesh,
>>>
>>> Can you please check if the dialogs are loaded back after a restart.
>>> Also, do you see any errors in your log?
>>>
>>> Regards,
>>>
>>> --
>>> Răzvan Crainea
>>> OpenSIPS Developer
>>>
>>>
>>> On 12/05/2011 02:31 PM, Bogdan-Andrei Iancu wrote:
>>>
>>> Hi Jayesh,
>>>
>>> Razvan is checking the code for you and running some tests.
>>>
>>> Regards,
>>> Bogdan
>>>
>>> On 12/03/2011 02:49 PM, Jayesh Nambiar wrote:
>>>
>>> Hi Bogdan,
>>> Just writing to ask if you got a chance to check if this is a bug or
>>> some error in my config !!
>>>
>>> Thanks,
>>>
>>> --- Jayesh
>>>
>>> On Fri, Dec 2, 2011 at 11:23 AM, Jayesh Nambiar 
>>> wrote:
>>>
 Hi Bogdan,
 The exact version used is 1.7.1 stable release compiled from src.
 Output of opensips -V is:
 version: opensips 1.7.1-notls (x86_64/linux)
 flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST,
 SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
 ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
 MAX_URI_SIZE 1024, BUF_SIZE 65535
 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
 svnrevision: unknown
 @(#) $Id: main.c 8537 2011-11-08 17:02:11Z bogdan_iancu $
 main.c compiled on 16:59:52 Dec  1 2011 with gcc 4.4.5

 The CDR does not survive a restart. Anything else to be enabled or
 added in the script or to be looked at?
 Thanks,

 --- Jayesh


  On Thu, Dec 1, 2011 at 10:35 PM, Bogdan-Andrei Iancu <
 bog...@opensips.org> wrote:

>  Hi Jayesh,
>
> If dialog module has restart persistence ( db modes 1, 2 and 3) the
> CDRs should survive across a restart. If this is not the case for you, let
> me know the exact version of opensips you are running (do "opensips -V").
>
> Regards,
> Bogdan
>
>
> On 12/01/2011 12:28 PM, Jayesh Nambiar wrote:
>
>  Hello All,
> I am planning to use CDR accounting in my script starting from version
> 1.7 and it looks fine and working as expected. Although I had o

Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-06 Thread Razvan Crainea

Hi, Jayesh!

Yes, I will need extra debugging to see what's happening. Can you 
send[1] the log in full debugging, taken after OpenSIPS is restarted?


[1] pastebin.com

Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/06/2011 08:13 AM, Jayesh Nambiar wrote:

Hi Razvan,
The dialogs are definitely loaded on startup and it also matches with 
existing dialog. I use this to make sure the dialog is matched in my 
script. So even after a restart, I see the Dialog Matched in my syslog.


if(has_totag()) {
  if(match_dialog()) {
 log(1, "Dialog Matched");
 route(default_relay);
 exit;
  }
}

But it is just that the cdr insert does not take place after the 
restart !!

My debug level was at 3. Do you want more detailed logs to check??

Thanks,

--- Jayesh

On Mon, Dec 5, 2011 at 7:12 PM, Razvan Crainea 
mailto:razvancrai...@opensips.org>> wrote:


Hi Jayesh,

Can you please check if the dialogs are loaded back after a
restart. Also, do you see any errors in your log?

Regards,

--
Răzvan Crainea
OpenSIPS Developer


On 12/05/2011 02:31 PM, Bogdan-Andrei Iancu wrote:

Hi Jayesh,

Razvan is checking the code for you and running some tests.

Regards,
Bogdan

On 12/03/2011 02:49 PM, Jayesh Nambiar wrote:

Hi Bogdan,
Just writing to ask if you got a chance to check if this is a
bug or some error in my config !!

Thanks,

--- Jayesh

On Fri, Dec 2, 2011 at 11:23 AM, Jayesh Nambiar
mailto:jayesh.v...@gmail.com>> wrote:

Hi Bogdan,
The exact version used is 1.7.1 stable release compiled from
src. Output of opensips -V is:
version: opensips 1.7.1-notls (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE,
USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144,
MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
svnrevision: unknown
@(#) $Id: main.c 8537 2011-11-08 17:02:11Z bogdan_iancu $
main.c compiled on 16:59:52 Dec  1 2011 with gcc 4.4.5

The CDR does not survive a restart. Anything else to be
enabled or added in the script or to be looked at?
Thanks,

--- Jayesh


On Thu, Dec 1, 2011 at 10:35 PM, Bogdan-Andrei Iancu
mailto:bog...@opensips.org>> wrote:

Hi Jayesh,

If dialog module has restart persistence ( db modes 1, 2
and 3) the CDRs should survive across a restart. If this
is not the case for you, let me know the exact version
of opensips you are running (do "opensips -V").

Regards,
Bogdan


On 12/01/2011 12:28 PM, Jayesh Nambiar wrote:

Hello All,
I am planning to use CDR accounting in my script
starting from version 1.7 and it looks fine and working
as expected. Although I had one doubt, how do I make
sure the CDR accounting still happens if the opensips
is restarted and BYE comes after the restart. I have
tried db_mode 3 for dialog module so that it dumps all
the dialogs while shutdown and on start it fetches the
dialog from the DB. This method makes sure the dialog
is matched when BYE comes after the restart but the CDR
record is not entered.
Is there any flag or dialog variable that I should set
to insert that value in the table for all dialogs when
opensips shuts off so that opensips knows that the CDR
flag was set for this dialog when started again and it
has to insert the record?
Do let me know for any pointers or ideas to get this done.
Thanks in advance.

--- Jayesh


___
Users mailing list
Users@lists.opensips.org  
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"






-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-05 Thread Jayesh Nambiar
Hi Razvan,
The dialogs are definitely loaded on startup and it also matches with
existing dialog. I use this to make sure the dialog is matched in my
script. So even after a restart, I see the Dialog Matched in my syslog.

if(has_totag()) {
  if(match_dialog()) {
 log(1, "Dialog Matched");
 route(default_relay);
 exit;
  }
}

But it is just that the cdr insert does not take place after the restart !!
My debug level was at 3. Do you want more detailed logs to check??

Thanks,

--- Jayesh

On Mon, Dec 5, 2011 at 7:12 PM, Razvan Crainea
wrote:

>  Hi Jayesh,
>
> Can you please check if the dialogs are loaded back after a restart. Also,
> do you see any errors in your log?
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/05/2011 02:31 PM, Bogdan-Andrei Iancu wrote:
>
> Hi Jayesh,
>
> Razvan is checking the code for you and running some tests.
>
> Regards,
> Bogdan
>
> On 12/03/2011 02:49 PM, Jayesh Nambiar wrote:
>
> Hi Bogdan,
> Just writing to ask if you got a chance to check if this is a bug or some
> error in my config !!
>
> Thanks,
>
> --- Jayesh
>
> On Fri, Dec 2, 2011 at 11:23 AM, Jayesh Nambiar wrote:
>
>> Hi Bogdan,
>> The exact version used is 1.7.1 stable release compiled from src. Output
>> of opensips -V is:
>> version: opensips 1.7.1-notls (x86_64/linux)
>> flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
>> SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
>> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
>> MAX_URI_SIZE 1024, BUF_SIZE 65535
>> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
>> svnrevision: unknown
>> @(#) $Id: main.c 8537 2011-11-08 17:02:11Z bogdan_iancu $
>> main.c compiled on 16:59:52 Dec  1 2011 with gcc 4.4.5
>>
>> The CDR does not survive a restart. Anything else to be enabled or added
>> in the script or to be looked at?
>> Thanks,
>>
>> --- Jayesh
>>
>>
>>  On Thu, Dec 1, 2011 at 10:35 PM, Bogdan-Andrei Iancu <
>> bog...@opensips.org> wrote:
>>
>>>  Hi Jayesh,
>>>
>>> If dialog module has restart persistence ( db modes 1, 2 and 3) the CDRs
>>> should survive across a restart. If this is not the case for you, let me
>>> know the exact version of opensips you are running (do "opensips -V").
>>>
>>> Regards,
>>> Bogdan
>>>
>>>
>>> On 12/01/2011 12:28 PM, Jayesh Nambiar wrote:
>>>
>>>  Hello All,
>>> I am planning to use CDR accounting in my script starting from version
>>> 1.7 and it looks fine and working as expected. Although I had one doubt,
>>> how do I make sure the CDR accounting still happens if the opensips is
>>> restarted and BYE comes after the restart. I have tried db_mode 3 for
>>> dialog module so that it dumps all the dialogs while shutdown and on start
>>> it fetches the dialog from the DB. This method makes sure the dialog is
>>> matched when BYE comes after the restart but the CDR record is not entered.
>>> Is there any flag or dialog variable that I should set to insert that
>>> value in the table for all dialogs when opensips shuts off so that opensips
>>> knows that the CDR flag was set for this dialog when started again and it
>>> has to insert the record?
>>> Do let me know for any pointers or ideas to get this done.
>>> Thanks in advance.
>>>
>>> --- Jayesh
>>>
>>>
>>> ___
>>> Users mailing 
>>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>>
>>> --
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developer
>>> OpenSIPS solutions and "know-how"
>>>
>>>
>>
>
>
> --
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> OpenSIPS solutions and "know-how"
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-05 Thread Razvan Crainea

Hi Jayesh,

Can you please check if the dialogs are loaded back after a restart. 
Also, do you see any errors in your log?


Regards,

--
Ra(zvan Crainea
OpenSIPS Developer


On 12/05/2011 02:31 PM, Bogdan-Andrei Iancu wrote:

Hi Jayesh,

Razvan is checking the code for you and running some tests.

Regards,
Bogdan

On 12/03/2011 02:49 PM, Jayesh Nambiar wrote:

Hi Bogdan,
Just writing to ask if you got a chance to check if this is a bug or 
some error in my config !!


Thanks,

--- Jayesh

On Fri, Dec 2, 2011 at 11:23 AM, Jayesh Nambiar 
mailto:jayesh.v...@gmail.com>> wrote:


Hi Bogdan,
The exact version used is 1.7.1 stable release compiled from src.
Output of opensips -V is:
version: opensips 1.7.1-notls (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST,
SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN
16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
svnrevision: unknown
@(#) $Id: main.c 8537 2011-11-08 17:02:11Z bogdan_iancu $
main.c compiled on 16:59:52 Dec  1 2011 with gcc 4.4.5

The CDR does not survive a restart. Anything else to be enabled
or added in the script or to be looked at?
Thanks,

--- Jayesh


On Thu, Dec 1, 2011 at 10:35 PM, Bogdan-Andrei Iancu
mailto:bog...@opensips.org>> wrote:

Hi Jayesh,

If dialog module has restart persistence ( db modes 1, 2 and
3) the CDRs should survive across a restart. If this is not
the case for you, let me know the exact version of opensips
you are running (do "opensips -V").

Regards,
Bogdan


On 12/01/2011 12:28 PM, Jayesh Nambiar wrote:

Hello All,
I am planning to use CDR accounting in my script starting
from version 1.7 and it looks fine and working as expected.
Although I had one doubt, how do I make sure the CDR
accounting still happens if the opensips is restarted and
BYE comes after the restart. I have tried db_mode 3 for
dialog module so that it dumps all the dialogs while
shutdown and on start it fetches the dialog from the DB.
This method makes sure the dialog is matched when BYE comes
after the restart but the CDR record is not entered.
Is there any flag or dialog variable that I should set to
insert that value in the table for all dialogs when opensips
shuts off so that opensips knows that the CDR flag was set
for this dialog when started again and it has to insert the
record?
Do let me know for any pointers or ideas to get this done.
Thanks in advance.

--- Jayesh


___
Users mailing list
Users@lists.opensips.org  
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"






--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-05 Thread Bogdan-Andrei Iancu

Hi Jayesh,

Razvan is checking the code for you and running some tests.

Regards,
Bogdan

On 12/03/2011 02:49 PM, Jayesh Nambiar wrote:

Hi Bogdan,
Just writing to ask if you got a chance to check if this is a bug or 
some error in my config !!


Thanks,

--- Jayesh

On Fri, Dec 2, 2011 at 11:23 AM, Jayesh Nambiar > wrote:


Hi Bogdan,
The exact version used is 1.7.1 stable release compiled from src.
Output of opensips -V is:
version: opensips 1.7.1-notls (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST,
SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN
16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
svnrevision: unknown
@(#) $Id: main.c 8537 2011-11-08 17:02:11Z bogdan_iancu $
main.c compiled on 16:59:52 Dec  1 2011 with gcc 4.4.5

The CDR does not survive a restart. Anything else to be enabled or
added in the script or to be looked at?
Thanks,

--- Jayesh


On Thu, Dec 1, 2011 at 10:35 PM, Bogdan-Andrei Iancu
mailto:bog...@opensips.org>> wrote:

Hi Jayesh,

If dialog module has restart persistence ( db modes 1, 2 and
3) the CDRs should survive across a restart. If this is not
the case for you, let me know the exact version of opensips
you are running (do "opensips -V").

Regards,
Bogdan


On 12/01/2011 12:28 PM, Jayesh Nambiar wrote:

Hello All,
I am planning to use CDR accounting in my script starting
from version 1.7 and it looks fine and working as expected.
Although I had one doubt, how do I make sure the CDR
accounting still happens if the opensips is restarted and BYE
comes after the restart. I have tried db_mode 3 for dialog
module so that it dumps all the dialogs while shutdown and on
start it fetches the dialog from the DB. This method makes
sure the dialog is matched when BYE comes after the restart
but the CDR record is not entered.
Is there any flag or dialog variable that I should set to
insert that value in the table for all dialogs when opensips
shuts off so that opensips knows that the CDR flag was set
for this dialog when started again and it has to insert the
record?
Do let me know for any pointers or ideas to get this done.
Thanks in advance.

--- Jayesh


___
Users mailing list
Users@lists.opensips.org  
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"






--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-03 Thread Jayesh Nambiar
Hi Bogdan,
Just writing to ask if you got a chance to check if this is a bug or some
error in my config !!

Thanks,

--- Jayesh

On Fri, Dec 2, 2011 at 11:23 AM, Jayesh Nambiar wrote:

> Hi Bogdan,
> The exact version used is 1.7.1 stable release compiled from src. Output
> of opensips -V is:
> version: opensips 1.7.1-notls (x86_64/linux)
> flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
> SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
> MAX_URI_SIZE 1024, BUF_SIZE 65535
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> svnrevision: unknown
> @(#) $Id: main.c 8537 2011-11-08 17:02:11Z bogdan_iancu $
> main.c compiled on 16:59:52 Dec  1 2011 with gcc 4.4.5
>
> The CDR does not survive a restart. Anything else to be enabled or added
> in the script or to be looked at?
> Thanks,
>
> --- Jayesh
>
>
> On Thu, Dec 1, 2011 at 10:35 PM, Bogdan-Andrei Iancu 
> wrote:
>
>> **
>> Hi Jayesh,
>>
>> If dialog module has restart persistence ( db modes 1, 2 and 3) the CDRs
>> should survive across a restart. If this is not the case for you, let me
>> know the exact version of opensips you are running (do "opensips -V").
>>
>> Regards,
>> Bogdan
>>
>>
>> On 12/01/2011 12:28 PM, Jayesh Nambiar wrote:
>>
>> Hello All,
>> I am planning to use CDR accounting in my script starting from version
>> 1.7 and it looks fine and working as expected. Although I had one doubt,
>> how do I make sure the CDR accounting still happens if the opensips is
>> restarted and BYE comes after the restart. I have tried db_mode 3 for
>> dialog module so that it dumps all the dialogs while shutdown and on start
>> it fetches the dialog from the DB. This method makes sure the dialog is
>> matched when BYE comes after the restart but the CDR record is not entered.
>> Is there any flag or dialog variable that I should set to insert that
>> value in the table for all dialogs when opensips shuts off so that opensips
>> knows that the CDR flag was set for this dialog when started again and it
>> has to insert the record?
>> Do let me know for any pointers or ideas to get this done.
>> Thanks in advance.
>>
>> --- Jayesh
>>
>>
>> ___
>> Users mailing 
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>> --
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developer
>> OpenSIPS solutions and "know-how"
>>
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-01 Thread Jayesh Nambiar
Hi Bogdan,
The exact version used is 1.7.1 stable release compiled from src. Output of
opensips -V is:
version: opensips 1.7.1-notls (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
svnrevision: unknown
@(#) $Id: main.c 8537 2011-11-08 17:02:11Z bogdan_iancu $
main.c compiled on 16:59:52 Dec  1 2011 with gcc 4.4.5

The CDR does not survive a restart. Anything else to be enabled or added in
the script or to be looked at?
Thanks,

--- Jayesh

On Thu, Dec 1, 2011 at 10:35 PM, Bogdan-Andrei Iancu wrote:

> **
> Hi Jayesh,
>
> If dialog module has restart persistence ( db modes 1, 2 and 3) the CDRs
> should survive across a restart. If this is not the case for you, let me
> know the exact version of opensips you are running (do "opensips -V").
>
> Regards,
> Bogdan
>
>
> On 12/01/2011 12:28 PM, Jayesh Nambiar wrote:
>
> Hello All,
> I am planning to use CDR accounting in my script starting from version 1.7
> and it looks fine and working as expected. Although I had one doubt, how do
> I make sure the CDR accounting still happens if the opensips is restarted
> and BYE comes after the restart. I have tried db_mode 3 for dialog module
> so that it dumps all the dialogs while shutdown and on start it fetches the
> dialog from the DB. This method makes sure the dialog is matched when BYE
> comes after the restart but the CDR record is not entered.
> Is there any flag or dialog variable that I should set to insert that
> value in the table for all dialogs when opensips shuts off so that opensips
> knows that the CDR flag was set for this dialog when started again and it
> has to insert the record?
> Do let me know for any pointers or ideas to get this done.
> Thanks in advance.
>
> --- Jayesh
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> --
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> OpenSIPS solutions and "know-how"
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr accounting on opensips restart

2011-12-01 Thread Bogdan-Andrei Iancu

Hi Jayesh,

If dialog module has restart persistence ( db modes 1, 2 and 3) the CDRs 
should survive across a restart. If this is not the case for you, let me 
know the exact version of opensips you are running (do "opensips -V").


Regards,
Bogdan

On 12/01/2011 12:28 PM, Jayesh Nambiar wrote:

Hello All,
I am planning to use CDR accounting in my script starting from version 
1.7 and it looks fine and working as expected. Although I had one 
doubt, how do I make sure the CDR accounting still happens if the 
opensips is restarted and BYE comes after the restart. I have tried 
db_mode 3 for dialog module so that it dumps all the dialogs while 
shutdown and on start it fetches the dialog from the DB. This method 
makes sure the dialog is matched when BYE comes after the restart but 
the CDR record is not entered.
Is there any flag or dialog variable that I should set to insert that 
value in the table for all dialogs when opensips shuts off so that 
opensips knows that the CDR flag was set for this dialog when started 
again and it has to insert the record?

Do let me know for any pointers or ideas to get this done.
Thanks in advance.

--- Jayesh


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] cdr accounting on opensips restart

2011-12-01 Thread Jayesh Nambiar
Hello All,
I am planning to use CDR accounting in my script starting from version 1.7
and it looks fine and working as expected. Although I had one doubt, how do
I make sure the CDR accounting still happens if the opensips is restarted
and BYE comes after the restart. I have tried db_mode 3 for dialog module
so that it dumps all the dialogs while shutdown and on start it fetches the
dialog from the DB. This method makes sure the dialog is matched when BYE
comes after the restart but the CDR record is not entered.
Is there any flag or dialog variable that I should set to insert that value
in the table for all dialogs when opensips shuts off so that opensips knows
that the CDR flag was set for this dialog when started again and it has to
insert the record?
Do let me know for any pointers or ideas to get this done.
Thanks in advance.

--- Jayesh
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting not working from this provider

2011-05-31 Thread Bogdan-Andrei Iancu

Hi James,

The dialog module does not "see" the BYE, so the dialog is counted as 
still ongoing so no CDR is generated.


Now, about the BYE - by default dialog module exclusively uses a cookie 
(the "did" param in the RR/Route header) to do the matching.


As you can see in the trace, because you do RR for re-INVITE (you 
shouldn't, but normally useless), the cookie is lost - and the device 
sending the BYE is brain-dead enough to "refresh" its route set during 
the reINVITE - even if the RFC says clear that the route set is learned 
only when the dialog is established.


Bottom line, because of the combination of un-nesessary RR and broken 
UA, the cookie gets lost and it does not appear in BYE, so it does not 
match.


A fast fix you can try is to set the matching mode of dialog mode to 
FALLBACK from "did" based matching to SIP-wise matching, so the dialog 
matching will match the BYE against the dialog even if the cookie is 
missing.


Regards,
Bogdan

On 04/23/2011 07:54 AM, jam...@vicidial.com wrote:


I have a new provider that I am evaluating and the built-in CDR 
functionality of the acc module is not working for them. I have tested 
with a second provider and it works fine. I can only assume that 
something somewhere in the SIP dialog is causing it to loose track of 
it. Here is the SIP dialog:


interface: any
filter: (ip) and ( port 5060 )
#
U 2011/04/22 23:06:09.857893 208.38.149.190:5060 -> 208.38.149.182:5060
INVITE sip:18633939336@208.38.149.182;cpd=on SIP/2.0
Via: SIP/2.0/UDP 208.38.149.190:5060;branch=z9hG4bK745a7a33;rport
From: "James P." ;tag=as791c05d3
To: 
Contact: 
Call-ID: 38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Max-Forwards: 70
Remote-Party-ID: "James P." 
;privacy=off;screen=no

Date: Sat, 23 Apr 2011 03:12:17 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces
Content-Type: application/sdp
Content-Length: 264

v=0
o=root 23976 23976 IN IP4 208.38.149.190
s=session
c=IN IP4 208.38.149.190
t=0 0
m=audio 13872 RTP/AVP 18 0 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

#
U 2011/04/22 23:06:09.858211 208.38.149.182:5060 -> 208.38.149.190:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 208.38.149.190:5060;branch=z9hG4bK745a7a33;rport=5060
From: "James P." ;tag=as791c05d3
To: 
Call-ID: 38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102 INVITE
Content-Length: 0


#
U 2011/04/22 23:06:09.859762 208.38.149.182:5060 -> 69.30.55.34:5060
INVITE sip:18633939336@69.30.55.34;cpd=on SIP/2.0
Record-Route: 
Via: SIP/2.0/UDP 208.38.149.182;branch=z9hG4bK4956.b46847f.0
Via: SIP/2.0/UDP 
208.38.149.190:5060;received=208.38.149.190;branch=z9hG4bK745a7a33;rport=5060

From: "James P." ;tag=as791c05d3
To: 
Contact: 
Call-ID: 38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Max-Forwards: 69
Remote-Party-ID: "James P." 
;privacy=off;screen=no

Date: Sat, 23 Apr 2011 03:12:17 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces
Content-Type: application/sdp
Content-Length: 264

v=0
o=root 23976 23976 IN IP4 208.38.149.190
s=session
c=IN IP4 208.38.149.190
t=0 0
m=audio 13872 RTP/AVP 18 0 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

#
U 2011/04/22 23:06:09.931832 69.30.55.34:5060 -> 208.38.149.182:5060
SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 208.38.149.182;branch=z9hG4bK4956.b46847f.0
Via: SIP/2.0/UDP 
208.38.149.190:5060;received=208.38.149.190;branch=z9hG4bK745a7a33;rport=5060

From: "James P." ;tag=as791c05d3
To: 
Call-ID: 38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102 INVITE
Server: OpenSIPS (1.6.2-notls (i386/linux))
Content-Length: 0


#
U 2011/04/22 23:06:10.974003 69.30.55.34:5060 -> 208.38.149.182:5060
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 208.38.149.182;branch=z9hG4bK4956.b46847f.0
Via: SIP/2.0/UDP 
208.38.149.190:5060;received=208.38.149.190;branch=z9hG4bK745a7a33;rport=5060

Record-Route: 
Record-Route: 
From: "James P." ;tag=as791c05d3
To: ;tag=as7abc238a
Call-ID: 38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102 INVITE
User-Agent: SIP SWITCH
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: 
Content-Type: application/sdp
Content-Length: 238

v=0
o=root 8881 8881 IN IP4 74.120.95.55
s=session
c=IN IP4 74.120.95.55
t=0 0
m=audio 23416 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv

#
U 2011/04/22 23:06:10.974350 208.38.149.182:5060 -> 208.38.149.190:5060
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 
208.38.149.190:5060;received=208.38.149.190;branch=z9hG4bK745a7a33;rport=5060

Record-Route: 
Record-Route: 
From: "James P." ;tag=as791c05d3
To: ;tag=as7abc238a
Call-ID: 38b57ce

[OpenSIPS-Users] CDR Accounting not working from this provider

2011-04-22 Thread jamesp


I have a new provider that I am evaluating and the built-in CDR
functionality of the acc module is not working for them. I have tested
with a second provider and it works fine. I can only assume that
something somewhere in the SIP dialog is causing it to loose track of
it. Here is the SIP dialog: 

interface: any
filter: (ip) and ( port
5060 )
#
U 2011/04/22 23:06:09.857893 208.38.149.190:5060 ->
208.38.149.182:5060
INVITE sip:18633939336@208.38.149.182;cpd=on
SIP/2.0
Via: SIP/2.0/UDP
208.38.149.190:5060;branch=z9hG4bK745a7a33;rport
From: "James P."
;tag=as791c05d3
To: 
Contact: 
Call-ID:
38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102
INVITE
User-Agent: Asterisk PBX
Max-Forwards: 70
Remote-Party-ID: "James
P." ;privacy=off;screen=no
Date: Sat, 23 Apr 2011 03:12:17 GMT
Allow:
INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY,
INFO
Supported: replaces
Content-Type: application/sdp
Content-Length:
264

v=0
o=root 23976 23976 IN IP4 208.38.149.190
s=session
c=IN IP4
208.38.149.190
t=0 0
m=audio 13872 RTP/AVP 18 0 101
a=rtpmap:18
G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:101
telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

#
U
2011/04/22 23:06:09.858211 208.38.149.182:5060 ->
208.38.149.190:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP
208.38.149.190:5060;branch=z9hG4bK745a7a33;rport=5060
From: "James P."
;tag=as791c05d3
To: 
Call-ID:
38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102
INVITE
Content-Length: 0

#
U 2011/04/22 23:06:09.859762
208.38.149.182:5060 -> 69.30.55.34:5060
INVITE
sip:18633939336@69.30.55.34;cpd=on SIP/2.0
Record-Route: 
Via:
SIP/2.0/UDP 208.38.149.182;branch=z9hG4bK4956.b46847f.0
Via: SIP/2.0/UDP
208.38.149.190:5060;received=208.38.149.190;branch=z9hG4bK745a7a33;rport=5060
From:
"James P." ;tag=as791c05d3
To: 
Contact: 
Call-ID:
38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102
INVITE
User-Agent: Asterisk PBX
Max-Forwards: 69
Remote-Party-ID: "James
P." ;privacy=off;screen=no
Date: Sat, 23 Apr 2011 03:12:17 GMT
Allow:
INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY,
INFO
Supported: replaces
Content-Type: application/sdp
Content-Length:
264

v=0
o=root 23976 23976 IN IP4 208.38.149.190
s=session
c=IN IP4
208.38.149.190
t=0 0
m=audio 13872 RTP/AVP 18 0 101
a=rtpmap:18
G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:101
telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

#
U
2011/04/22 23:06:09.931832 69.30.55.34:5060 ->
208.38.149.182:5060
SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP
208.38.149.182;branch=z9hG4bK4956.b46847f.0
Via: SIP/2.0/UDP
208.38.149.190:5060;received=208.38.149.190;branch=z9hG4bK745a7a33;rport=5060
From:
"James P." ;tag=as791c05d3
To: 
Call-ID:
38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102 INVITE
Server:
OpenSIPS (1.6.2-notls (i386/linux))
Content-Length: 0

#
U 2011/04/22
23:06:10.974003 69.30.55.34:5060 -> 208.38.149.182:5060
SIP/2.0 183
Session Progress
Via: SIP/2.0/UDP
208.38.149.182;branch=z9hG4bK4956.b46847f.0
Via: SIP/2.0/UDP
208.38.149.190:5060;received=208.38.149.190;branch=z9hG4bK745a7a33;rport=5060
Record-Route:

Record-Route: 
From: "James P." ;tag=as791c05d3
To:
;tag=as7abc238a
Call-ID:
38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102
INVITE
User-Agent: SIP SWITCH
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE,
REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: 
Content-Type:
application/sdp
Content-Length: 238

v=0
o=root 8881 8881 IN IP4
74.120.95.55
s=session
c=IN IP4 74.120.95.55
t=0 0
m=audio 23416 RTP/AVP
0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101
0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv

#
U 2011/04/22
23:06:10.974350 208.38.149.182:5060 -> 208.38.149.190:5060
SIP/2.0 183
Session Progress
Via: SIP/2.0/UDP
208.38.149.190:5060;received=208.38.149.190;branch=z9hG4bK745a7a33;rport=5060
Record-Route:

Record-Route: 
From: "James P." ;tag=as791c05d3
To:
;tag=as7abc238a
Call-ID:
38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102
INVITE
User-Agent: SIP SWITCH
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE,
REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: 
Content-Type:
application/sdp
Content-Length: 238

v=0
o=root 8881 8881 IN IP4
74.120.95.55
s=session
c=IN IP4 74.120.95.55
t=0 0
m=audio 23416 RTP/AVP
0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101
0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv

#
U 2011/04/22
23:06:19.628116 69.30.55.34:5060 -> 208.38.149.182:5060
SIP/2.0 200
OK
Via: SIP/2.0/UDP 208.38.149.182;branch=z9hG4bK4956.b46847f.0
Via:
SIP/2.0/UDP
208.38.149.190:5060;received=208.38.149.190;branch=z9hG4bK745a7a33;rport=5060
Record-Route:

Record-Route: 
From: "James P." ;tag=as791c05d3
To:
;tag=as7abc238a
Call-ID:
38b57ce271946530476aea3909a8de2b@208.38.149.190
CSeq: 102
INVITE
User-Agent: SIP SWITCH
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE,
REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: 
Content-Type:
application/sdp
Content-Length: 238

v=0
o=root 8881 

[OpenSIPS-Users] CDR flag

2011-02-08 Thread Denis Putyato
Hello!

 

There is Opensips 1.6.4-2 and I use CDR flag for accounting purposes.

 

Today I found one record in acc table which have duration 10829  s.

I found sip_debug  of this call (I am using ngrep utility for caching sip). The 
debug I attached to the message.

 

In this debug: 

1.1.1.1-  Kamailio of some provider

2.2.2.2 – my Opensips

3.3.3.3 – Cisco gateway

 

As you can see there is no BYE in this session, but CDR record appears in acc 
table. 

I have such parameter of dialog module:

modparam("dialog", "hash_size", 4096)

modparam("dialog", "log_profile_hash_size", 12)

modparam("dialog", "default_timeout", 10800)

modparam("dialog", "timeout_avp", "$avp(i:995)")

modparam("dialog", "dlg_match_mode", 1)

modparam("dialog", "db_mode", 1)

modparam("dialog", "db_url", "mysql://xxx:xxx@localhost/xx")

modparam("dialog", "profiles_with_value", "client;tgrp")

modparam("dialog", "bye_on_timeout_flag", 7)

 

I wonder how CDR record may appears in acc table if there was no BYE for this 
session (even generated locally by Opensips) 

 

Thank you for any help.  

U 2011/02/08 12:37:15.912296 1.1.1.1:5062 -> 2.2.2.2:5060
INVITE sip:81074953330822@2.2.2.2:5060;transport=udp SIP/2.0.
Max-Forwards: 10.
Record-Route: 
.
Record-Route: 
.
From: 
"00076246";tag=100ed728-4ee4d25b-13d8-50029-559cb-48b38c09-559cb.
To: .
Remote-Party-ID: ;party=calling;screen=yes;privacy=off.
Privacy: user.
P-Asserted-Identity: .
Call-ID: 100f8618-4ee4d25b-13d8-50029-559cb-492146b3-559cb.
CSeq: 2 INVITE.
Via: SIP/2.0/UDP 1.1.1.1:5062;branch=z9hG4bKa833.e14b1e83.0.
Via: SIP/2.0/UDP 1.1.1.1:5067;branch=z9hG4bKa833.ed1a515.0.
Via: SIP/2.0/UDP 
91.210.228.78:5080;rport=5080;branch=z9hG4bK-559cb-14e6c2e1-194a79dc.
Supported: replaces,100rel.
Contact: .
Content-Type: application/sdp.
Content-Length: 453.
.
v=0.
o=00076246 1297158004 1297158004 IN IP4 91.210.228.78.
s=-.
c=IN IP4 91.210.228.78.
t=0 0.
m=audio 5004 RTP/AVP 0 8 18 4 98 2 101.
a=rtpmap:0 PCMU/8000.
a=ptime:20.
a=rtpmap:8 PCMA/8000.
a=ptime:20.
a=rtpmap:18 G729/8000.
a=fmtp:18 annexb=no.
a=ptime:20.
a=rtpmap:4 g723/8000.
a=fmtp:4 annexa=no.
a=ptime:30.
a=rtpmap:98 g726-16/8000.
a=ptime:20.
a=rtpmap:2 g726-32/

U 2011/02/08 12:37:15.913193 2.2.2.2:5060 -> 1.1.1.1:5062
SIP/2.0 100 Giving a try.
From: 
"00076246";tag=100ed728-4ee4d25b-13d8-50029-559cb-48b38c09-559cb.
To: .
Call-ID: 100f8618-4ee4d25b-13d8-50029-559cb-492146b3-559cb.
CSeq: 2 INVITE.
Via: SIP/2.0/UDP 1.1.1.1:5062;branch=z9hG4bKa833.e14b1e83.0.
Via: SIP/2.0/UDP 1.1.1.1:5067;branch=z9hG4bKa833.ed1a515.0.
Via: SIP/2.0/UDP 
91.210.228.78:5080;rport=5080;branch=z9hG4bK-559cb-14e6c2e1-194a79dc.
Content-Length: 0.
.


U 2011/02/08 12:37:15.913383 2.2.2.2:5060 -> 3.3.3.3:5060
INVITE sip:10584953330822@3.3.3.3:5060;transport=udp SIP/2.0.
Record-Route: 
.
Max-Forwards: 10.
Record-Route: 
.
Record-Route: 
.
From: 
"00076246";tag=100ed728-4ee4d25b-13d8-50029-559cb-48b38c09-559cb.
To: .
Privacy: user
P-Asserted-Identity: .
Call-ID: 100f8618-4ee4d25b-13d8-50029-559cb-492146b3-559cb.
CSeq: 2 INVITE.
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKa833.94c70144.0.
Via: SIP/2.0/UDP 1.1.1.1:5062;branch=z9hG4bKa833.e14b1e83.0.
Via: SIP/2.0/UDP 1.1.1.1:5067;branch=z9hG4bKa833.ed1a515.0.
Via: SIP/2.0/UDP 
91.210.228.78:5080;rport=5080;branch=z9hG4bK-559cb-14e6c2e1-194a79dc.
Supported: replaces,100rel.
Contact: .
Remote-Party-ID:;party=calling;screen=yes;privacy=full
Content-Type: application/sdp.
Content-Length: 453.
.
v=0.
o=00076246 1297158004 1297158004 IN IP4 91.210.228.78.
s=-.
c=IN IP4 91.210.228.78.
t=0 0.
m=audio 5004 RTP/AVP 0 8 18 4 98 2 101.
a=rtpmap:0 PCMU/8000.
a=ptime:20.
a=rtpmap:8 PCMA/8000.
a=pti

U 2011/02/08 12:37:15.932117 3.3.3.3:5060 -> 2.2.2.2:5060
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKa833.94c70144.0,SIP/2.0/UDP 
1.1.1.1:5062;branch=z9hG4bKa833.e14b1e83.0,SIP/2.0/UDP 
1.1.1.1:5067;branch=z9hG4bKa833.ed1a515.0,SIP/2.0/UDP 
91.210.228.78:5080;rport=5080;branch=z9hG4bK-559cb-14e6c2e1-194a79dc.
From: 
"00076246";tag=100ed728-4ee4d25b-13d8-50029-559cb-48b38c09-559cb.
To: .
Date: Sat, 29 Apr 2000 22:33:47 GMT.
Call-ID: 100f8618-4ee4d25b-13d8-50029-559cb-492146b3-559cb.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 2 INVITE.
Allow-Events: telephone-event.
Content-Length: 0.
.


U 2011/02/08 12:37:18.391650 3.3.3.3:5060 -> 2.2.2.2:5060
SIP/2.0 183 Session Progress.
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKa833.94c70144.0,SIP/2.0/UDP 
1.1.1.1:5062;branch=z9hG4bKa833.e14b1e83.0,SIP/2.0/UDP 
1.1.1.1:5067;branch=z9hG4bKa833.ed1a515.0,SIP/2.0/UDP 
91.210.228.78:5080;rport=5080;branch=z9hG4bK-559cb-14e6c2e1-194a79dc.
From: 
"00076246";tag=100ed728-4ee4d25b-13d8-50029-559cb-48b38c09-559cb.
To: ;tag=1F4B3678-159A.
Date: Sat, 29 Apr 2000 22:33:47 GMT.
Call-ID: 100f8618-4ee4d25b-13d8-50029-559cb-492146b3-559cb.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 2 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, 
NOTIFY, INFO, REGISTER.
Require: 100rel.
RSeq: 615.
Allow-Events: t

Re: [OpenSIPS-Users] CDR Accounting

2011-01-25 Thread Adrian Georgescu
Why do you need microseconds in accounting? All database queries, round trip 
time to the database on the LAN, radius requests,  all add up times impossible 
to measure. What is the point of accounting microseconds for a process that 
itself takes unknown amount of time but several order of magnitude higher than 
your accounting resolution?

Adrian

On Jan 24, 2011, at 9:47 PM, Dave Singer wrote:

> Thanks for that clarification!
> 
> So just to be sure I'm clear on this. $Ts rounds down ( truncates ) the 
> current second. So using $avp(s:start_time) = $Ts.$Tsm; would give something 
> like "12343253.543233" and always be accurate?
> Further (standard ACC [without dialog]) you could just put $Tsm in the 
> db_extras as an extra column and then use the tool you are using to created 
> cdrs from the acc table to take the column with the $Tsm value into account 
> when calculating duration, ringtime, etc.
> To get these numbers with the new CDR feature, you would have to store a 
> dialog variable like $dlg_val("start") = "$Ts.$Tsm" at start and 
> $dlg_val("answered") = "$Ts.$Tsm" at answer and at the end of the call add 
> them db_extras along with $Ts.$Tsm for the end of the call. You would then 
> want to go off of those numbers rather than what the acc module automatically 
> put in the db.
> The disadvantage would be having duplicate columns for start/answer/end times 
> but you would still have the benefit of not having to have an external 
> process building cdrs from acc table matching up BYEs to INVITES, etc.
> Calculating the durations in opensips would be tricky since it does not work 
> with non integers. But you could do that easily with a sql trigger on the 
> record insert.
> 
> Does this sound right?
> 
> Thanks
> Dave
> 
> On Thu, Jan 20, 2011 at 4:54 AM, Anca Vamanu  wrote:
> On 01/19/2011 09:31 PM, a.zagors...@oyster-telecom.ru wrote:
> It was my conversation, and I told about
> 1) $Tsm is MICROseconds (6 digits)
> 2) It is microseconds of a current second.
> 
> Yes, that's true. I fixed it in documentation also.
> 
> -- 
> Anca Vamanu
> www.voice-system.ro
> 
> 
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-25 Thread Anton Zagorskiy
Hi Dave.

> So just to be sure I'm clear on this. $Ts rounds down ( truncates ) the
current second. So using $avp(s:start_time) = $Ts.$Tsm; would give something
like "12343253.543233" and always be accurate?

You should understand that $Ts.$Tsm is two independent calls to the system
time function. So actually $Tsm isn't microseconds of $Ts.

P.S. Could you please use any brackets to mark original letter or send your
answer in the plain text fromat?



> Thanks for that clarification!

> So just to be sure I'm clear on this. $Ts rounds down ( truncates ) the
current second. So using $avp(s:start_time) = $Ts.$Tsm; would give something
like "12343253.543233" and always be accurate?
> Further (standard ACC [without dialog]) you could just put $Tsm in the
db_extras as an extra column and then use the tool you are using to created
cdrs from the acc table to take the column with the $Tsm value into account
when > calculating duration, ringtime, etc.
> To get these numbers with the new CDR feature, you would have to store a
dialog variable like $dlg_val("start") = "$Ts.$Tsm" at start
and $dlg_val("answered") = "$Ts.$Tsm" at answer and at the end of the call
add them db_extras > along with $Ts.$Tsm for the end of the call. You would
then want to go off of those numbers rather than what the acc module
automatically put in the db.
> The disadvantage would be having duplicate columns for start/answer/end
times but you would still have the benefit of not having to have an external
process building cdrs from acc table matching up BYEs to INVITES, etc.
> Calculating the durations in opensips would be tricky since it does not
work with non integers. But you could do that easily with a sql trigger on
the record insert.

> Does this sound right?

> Thanks
> Dave

> On Thu, Jan 20, 2011 at 4:54 AM, Anca Vamanu  wrote:
> On 01/19/2011 09:31 PM, a.zagors...@oyster-telecom.ru wrote:
> It was my conversation, and I told about
> 1) $Tsm is MICROseconds (6 digits)
> 2) It is microseconds of a current second.
> Yes, that's true. I fixed it in documentation also.

> -- 
> Anca Vamanu
> www.voice-system.ro



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-24 Thread Dave Singer
Thanks for that clarification!

So just to be sure I'm clear on this. $Ts rounds down ( truncates ) the
current second. So using $avp(s:start_time) = $Ts.$Tsm; would give something
like "12343253.543233" and always be accurate?
Further (standard ACC [without dialog]) you could just put $Tsm in the
db_extras as an extra column and then use the tool you are using to created
cdrs from the acc table to take the column with the $Tsm value into account
when calculating duration, ringtime, etc.
To get these numbers with the new CDR feature, you would have to store a
dialog variable like $dlg_val("start") = "$Ts.$Tsm" at start
and $dlg_val("answered") = "$Ts.$Tsm" at answer and at the end of the call
add them db_extras along with $Ts.$Tsm for the end of the call. You would
then want to go off of those numbers rather than what the acc module
automatically put in the db.
The disadvantage would be having duplicate columns for start/answer/end
times but you would still have the benefit of not having to have an external
process building cdrs from acc table matching up BYEs to INVITES, etc.
Calculating the durations in opensips would be tricky since it does not work
with non integers. But you could do that easily with a sql trigger on the
record insert.

Does this sound right?

Thanks
Dave

On Thu, Jan 20, 2011 at 4:54 AM, Anca Vamanu  wrote:

> On 01/19/2011 09:31 PM, a.zagors...@oyster-telecom.ru wrote:
>
>> It was my conversation, and I told about
>> 1) $Tsm is MICROseconds (6 digits)
>> 2) It is microseconds of a current second.
>>
>>  Yes, that's true. I fixed it in documentation also.
>
> --
> Anca Vamanu
> www.voice-system.ro
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-20 Thread Anca Vamanu

On 01/19/2011 09:31 PM, a.zagors...@oyster-telecom.ru wrote:

It was my conversation, and I told about
1) $Tsm is MICROseconds (6 digits)
2) It is microseconds of a current second.


Yes, that's true. I fixed it in documentation also.

--
Anca Vamanu
www.voice-system.ro


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-20 Thread Bogdan-Andrei Iancu

Hi Andrew,

if you are using the new CDR generation feature (acc with dialog 
module), you cannot do it, as the acc module calculates the duration at 
second level. So, by default you get only secondsThere is a 
pseudo-variable to get the microseconds and you could use 
extra_accounting to have it added to CDR, but when generating directly 
CDRs (based on dialog module), all extra_accounting vars are evaluated 
at 200 OK time (when the call starts), so you cannot take the value for 
the BYE time.


You can do it only if you use the standard ACC (without dialog) which 
generated 2 records (START and STOP) for each call and extra_accounting 
vars are evaluated for each record, so you get the microseconds for 
INVITE and BYE


Regards,
Bogdan

Andrew Philp wrote:

It is the new feature of 1.6.4 that I am trying to get working.  Thanks for
your comments

Hi, Andrew.

Maybe I'm wrong, but using only acc module it is impossible.

I'm using dialog module and manually store start and end time of a duration.






WBR, Anton Zagorskiy
VoIP Developer, Oyster Telecom
Phone.: +7 812 601-0666
Fax: +7 812 601-0593
a.zagors...@oyster-telecom.ru
www.oyster-telecom.ru


From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Andrew Philp
Sent: Wednesday, January 19, 2011 2:12 PM
To: OpenSIPS users mailling list
Subject: [OpenSIPS-Users] CDR Accounting

Hi All,

Managed to finally get this working, mainly my stupidity in the end.

Just one more question if anyone can tell me.  Is it possible to have a
better reflection on the duration?  At present my system is only showing
whole seconds and not milliseconds and this would be helpful.

Thanks again in advance.


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

  



--
Bogdan-Andrei Iancu
OpenSIPS Event - expo, conf, social, bootcamp
2 - 4 February 2011, ITExpo, Miami,  USA
OpenSIPS solutions and "know-how"


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting Example

2011-01-19 Thread Andrew Hash
thanks!





From: Anton Zagorskiy 
To: andrew.ph...@just-tek.com; OpenSIPS users mailling list 

Sent: Tue, January 18, 2011 3:29:29 AM
Subject: Re: [OpenSIPS-Users] CDR Accounting Example

Hi Andrew.

modparam("acc", "db_extra",
"src=$(dlg_val(from.uri){uri.user});dst=$(dlg_val(request.uri){uri.user});ch
annel=$dlg_val(channel);dstchannel=$dlg_val(dchannel)")
modparam("acc", "db_flag", 10)
modparam("acc", "db_url", "mysql://login:pass@host/db")
modparam("acc", "cdr_flag", 2)

...

Later in the script
setflag(2);
setflag(10);





$dlg_val(..) I'm setting up during the script.



WBR, Anton Zagorskiy
VoIP Developer, Oyster Telecom
Phone.: +7 812 601-0666
Fax: +7 812 601-0593
a.zagors...@oyster-telecom.ru
www.oyster-telecom.ru


From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Andrew Philp
Sent: Tuesday, January 18, 2011 2:00 PM
To: OpenSIPS users mailling list
Subject: [OpenSIPS-Users] CDR Accounting Example

Hi All,
Has anyone got a working example of the CDR accounting working with mysql. 
I have tried to get this sorted but I feel I am missing something.
Thanks in adavnce



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-19 Thread a.zagorskiy

It was my conversation, and I told about
1) $Tsm is MICROseconds (6 digits)
2) It is microseconds of a current second.

On Wed, 19 Jan 2011 09:29:28 -0800
 Dave Singer  wrote:
Be careful when using $Tsm. I read a thread the other 
day that was just
talking about it and that it returns milliseconds since 
midnight, not epoch.
So if that is true you will need to somehow handle calls 
that cross midnight
for duration at least and start/answer/end of call if 
including the

precision in those timestamps.
I'd be interested to see what you find.
What I've seen with sub second accounting is for 
rounding purposes where for
example billing in 6 second increments and it is always 
rounded up. So a

call 6.001 seconds would be charged for 12 seconds.

Dave

On Wed, Jan 19, 2011 at 6:35 AM, Brett Nemeroff 
 wrote:


On Wed, Jan 19, 2011 at 8:32 AM, Andrew Philp 
wrote:


We are looking to use this for billing directly and for 
most of our

customers are billed on a hundredth of a second.

Does this make sense?


Sure it does, but I've never heard of sub second 
billing. The ACC module is
probably not going to help you for this need presently. 
I believe $Tsm
returns milliseconds. You may be able to manually 
account for the calls with

that.
-Brett


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-19 Thread Dave Singer
Be careful when using $Tsm. I read a thread the other day that was just
talking about it and that it returns milliseconds since midnight, not epoch.
So if that is true you will need to somehow handle calls that cross midnight
for duration at least and start/answer/end of call if including the
precision in those timestamps.
I'd be interested to see what you find.
What I've seen with sub second accounting is for rounding purposes where for
example billing in 6 second increments and it is always rounded up. So a
call 6.001 seconds would be charged for 12 seconds.

Dave

On Wed, Jan 19, 2011 at 6:35 AM, Brett Nemeroff  wrote:

> On Wed, Jan 19, 2011 at 8:32 AM, Andrew Philp 
> wrote:
>
>> We are looking to use this for billing directly and for most of our
>> customers are billed on a hundredth of a second.
>>
>> Does this make sense?
>>
>>
> Sure it does, but I've never heard of sub second billing. The ACC module is
> probably not going to help you for this need presently. I believe $Tsm
> returns milliseconds. You may be able to manually account for the calls with
> that.
> -Brett
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-19 Thread Brett Nemeroff
On Wed, Jan 19, 2011 at 8:32 AM, Andrew Philp wrote:

> We are looking to use this for billing directly and for most of our
> customers are billed on a hundredth of a second.
>
> Does this make sense?
>
>
Sure it does, but I've never heard of sub second billing. The ACC module is
probably not going to help you for this need presently. I believe $Tsm
returns milliseconds. You may be able to manually account for the calls with
that.
-Brett
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-19 Thread Andrew Philp
We are looking to use this for billing directly and for most of our customers 
are billed on a hundredth of a second. 

Does this make sense?

Sent from my iPhone

On 19 Jan 2011, at 14:18, Brett Nemeroff  wrote:

> On Wed, Jan 19, 2011 at 5:11 AM, Andrew Philp  
> wrote:
> Just one more question if anyone can tell me.  Is it possible to have a 
> better reflection on the duration?  At present my system is only showing 
> whole seconds and not milliseconds and this would be helpful.
> 
> 
> 
> 
> I don't believe that is possible at this time. I'm not sure why milliseconds 
> would be useful. Perhaps if you can tell us what you are trying to do with 
> that, there may be another way to do what you are trying to do (for example, 
> measuring ringtime or PDD).
> 
> -Brett
>  
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-19 Thread Brett Nemeroff
On Wed, Jan 19, 2011 at 5:11 AM, Andrew Philp wrote:

> Just one more question if anyone can tell me.  Is it possible to have a
> better reflection on the duration?  At present my system is only showing
> whole seconds and not milliseconds and this would be helpful.
>
>
>
I don't believe that is possible at this time. I'm not sure why milliseconds
would be useful. Perhaps if you can tell us what you are trying to do with
that, there may be another way to do what you are trying to do (for example,
measuring ringtime or PDD).

-Brett
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-19 Thread Andrew Philp
It is the new feature of 1.6.4 that I am trying to get working.  Thanks for
your comments

Hi, Andrew.

Maybe I'm wrong, but using only acc module it is impossible.

I'm using dialog module and manually store start and end time of a duration.






WBR, Anton Zagorskiy
VoIP Developer, Oyster Telecom
Phone.: +7 812 601-0666
Fax: +7 812 601-0593
a.zagors...@oyster-telecom.ru
www.oyster-telecom.ru


From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Andrew Philp
Sent: Wednesday, January 19, 2011 2:12 PM
To: OpenSIPS users mailling list
Subject: [OpenSIPS-Users] CDR Accounting

Hi All,

Managed to finally get this working, mainly my stupidity in the end.

Just one more question if anyone can tell me.  Is it possible to have a
better reflection on the duration?  At present my system is only showing
whole seconds and not milliseconds and this would be helpful.

Thanks again in advance.


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting

2011-01-19 Thread Anton Zagorskiy
Hi, Andrew.

Maybe I'm wrong, but using only acc module it is impossible.

I'm using dialog module and manually store start and end time of a duration.






WBR, Anton Zagorskiy
VoIP Developer, Oyster Telecom
Phone.: +7 812 601-0666
Fax: +7 812 601-0593
a.zagors...@oyster-telecom.ru
www.oyster-telecom.ru


From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Andrew Philp
Sent: Wednesday, January 19, 2011 2:12 PM
To: OpenSIPS users mailling list
Subject: [OpenSIPS-Users] CDR Accounting

Hi All,

Managed to finally get this working, mainly my stupidity in the end.

Just one more question if anyone can tell me.  Is it possible to have a
better reflection on the duration?  At present my system is only showing
whole seconds and not milliseconds and this would be helpful.

Thanks again in advance.


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR Accounting

2011-01-19 Thread Andrew Philp
Hi All,

 

Managed to finally get this working, mainly my stupidity in the end.

 

Just one more question if anyone can tell me.  Is it possible to have a
better reflection on the duration?  At present my system is only showing
whole seconds and not milliseconds and this would be helpful.

 

Thanks again in advance.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Accounting Example

2011-01-18 Thread Anton Zagorskiy
Hi Andrew.

modparam("acc", "db_extra",
"src=$(dlg_val(from.uri){uri.user});dst=$(dlg_val(request.uri){uri.user});ch
annel=$dlg_val(channel);dstchannel=$dlg_val(dchannel)")
modparam("acc", "db_flag", 10)
modparam("acc", "db_url", "mysql://login:pass@host/db")
modparam("acc", "cdr_flag", 2)

...

Later in the script
setflag(2);
setflag(10);





$dlg_val(..) I'm setting up during the script.



WBR, Anton Zagorskiy
VoIP Developer, Oyster Telecom
Phone.: +7 812 601-0666
Fax: +7 812 601-0593
a.zagors...@oyster-telecom.ru
www.oyster-telecom.ru


From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Andrew Philp
Sent: Tuesday, January 18, 2011 2:00 PM
To: OpenSIPS users mailling list
Subject: [OpenSIPS-Users] CDR Accounting Example

Hi All,
Has anyone got a working example of the CDR accounting working with mysql. 
I have tried to get this sorted but I feel I am missing something.
Thanks in adavnce



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] CDR Accounting Example

2011-01-18 Thread Andrew Philp
Hi All,

Has anyone got a working example of the CDR accounting working with mysql.
I have tried to get this sorted but I feel I am missing something.

Thanks in adavnce

 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] cdr vs drouting

2009-09-04 Thread Brett Nemeroff
I *think* you mean the LCR module.
You want to use the drouting module. It's effectively the replacement for
LCR. It's faster and supports more routes. My dr_rules table has over 3
million rules in it.
-Brett


On Fri, Sep 4, 2009 at 9:34 AM, Szasz Szabolcs wrote:

> Hi,
>
> What are main benefits of the drouting vs cdr module? Which of them should
> I use if I have thousands of routes?
>
> Thanks
> Szasz Szabolcs
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] cdr vs drouting

2009-09-04 Thread Szasz Szabolcs
Hi,

What are main benefits of the drouting vs cdr module? Which of them should I
use if I have thousands of routes?

Thanks
Szasz Szabolcs
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Tools

2009-04-24 Thread Darren Sessions
Not that I don't like the standard setup, I just think that one less  
layer of things to have to work with, the better is all.


Mainly just making sure that I'm not shooting myself in the foot  
trying to get away from the radius piece and also that I'm not going  
doing a path that's going to be uber complex or difficult to setup.


Many thanks,

 - Darren


On Apr 24, 2009, at 8:26 AM, Adrian Georgescu wrote:

You ask questions that can lead to infinite directions. You are the  
only one who can decide what is best to do if you do not like the  
standard setup.


Adrian

On Apr 24, 2009, at 4:17 PM, Darren Sessions wrote:

Does that mean I can't delete the radacct tables? or can I just  
point CDRTools in a different direction via global.inc? and if so,  
what would I point it to? the acc table?



On Apr 24, 2009, at 1:42 AM, Adrian Georgescu wrote:

As long as you end up in MySQL with the same data as Radius server  
use to write you do not need per se Freeradius.


Adrian


On Apr 23, 2009, at 7:15 PM, Darren Sessions wrote:


Is using freeradius a requirement with CDRTools? or can I use DB
access for everything? If so, how do I go about that or can someone
point me in the right direction?

I've got CDRTools up and running btw with the Freeradius server, it
just seems a bit of an extra component when I've got the database
running anyways.

Just piped 15k calls through an opensips/cdrtools/mediaproxy  
install
over the last week and have had very little to deal with (average  
load
of 0 across all the servers as well). Many thanks to everyone  
involved

with these projects!

Cheers,

 - Darren

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users








___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] CDR Tools

2009-04-24 Thread Adrian Georgescu
You ask questions that can lead to infinite directions. You are the  
only one who can decide what is best to do if you do not like the  
standard setup.


Adrian

On Apr 24, 2009, at 4:17 PM, Darren Sessions wrote:

Does that mean I can't delete the radacct tables? or can I just  
point CDRTools in a different direction via global.inc? and if so,  
what would I point it to? the acc table?



On Apr 24, 2009, at 1:42 AM, Adrian Georgescu wrote:

As long as you end up in MySQL with the same data as Radius server  
use to write you do not need per se Freeradius.


Adrian


On Apr 23, 2009, at 7:15 PM, Darren Sessions wrote:


Is using freeradius a requirement with CDRTools? or can I use DB
access for everything? If so, how do I go about that or can someone
point me in the right direction?

I've got CDRTools up and running btw with the Freeradius server, it
just seems a bit of an extra component when I've got the database
running anyways.

Just piped 15k calls through an opensips/cdrtools/mediaproxy install
over the last week and have had very little to deal with (average  
load
of 0 across all the servers as well). Many thanks to everyone  
involved

with these projects!

Cheers,

 - Darren

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users






___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


  1   2   >