[Freeswitch-users] nibblebill sometimes does not hang leg-b, maybe a bug??

[Luis Daniel Lucio Quiroz]

Hello

Using LCR+nibblebill works, but sometimes leg-b does not hang up.

I see this when this unwanted behaviour happens

[SELECT balance AS nibble_balance FROM v_billings WHERE type_value='mydomian']
2014-12-29 01:35:25.558121 [DEBUG] mod_nibblebill.c:428 Retrieved
current balance for account mydomain (balance = -4.545400)
2014-12-29 01:35:25.558121 [DEBUG] switch_core_state_machine.c:528
(sofia/external/1800XXXXXXX) State ROUTING going to sleep
2014-12-29 01:35:25.578118 [DEBUG] switch_ivr_originate.c:3684
Originate Cancelled by originator termination Cause: 487
[ORIGINATOR_CANCEL]
2014-12-29 01:35:25.578118 [NOTICE] switch_ivr_originate.c:2708 Cannot
create outgoing channel of type [lcr] cause: [ORIGINATOR_CANCEL]
2014-12-29 01:35:25.578118 [DEBUG] switch_ivr_originate.c:3695
Originate Resulted in Error Cause: 487 [ORIGINATOR_CANCEL]


LCR is loaded and working.  Could it be that events are asyncronous
and sometimes niblebill gets the first hit?

Odd thing is that this is random, and using same variables.  I mean,
same caller, to same callee, same carrier, same LCR rate.

I pass this variables:
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [lcr_carrier]=[Flowroute]
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [lcr_rate]=[0.00000]
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [lcr_user_rate]=[0.01900]
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [nibble_account]=[mydomain]
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [nibble_rate]=[0.01900]
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [lcr_first_increment]=[6]
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [lcr_second_increment]=[6]
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [lcr_user_first_increment]=[6]
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [lcr_user_second_increment]=[6]
2014-12-29 01:35:17.658127 [DEBUG] switch_event.c:1688 Parsing
variable [nobal_amt]=[-0.010000]


As I said, i use same variables and the behaviour is erratic.   All my
tests are the same, I dont change any variable.

Is this a nibble bug?  Let me know what kind of info you need to file
a bug in jira.

LD