provided by Star2Billing S.L.

Hello,

I think I am having issues with incoming DDI and forwarding it to sip client.

Technically it works OK - I am able to answer this call on my SIP phone and have a conversation.
However when I look at CDRs I can see 2 entries for this incoming call (example at the bottom) - one call type is DID_VOIP and the second one is DID-ALEG.

This call is not billed (which is what I want) but why do I have 2 entries? Is it expected in a2billing or perhaps I misconfiguration something?

Is anyone experiencing similar issue?

Current setup:

1. in FreePBX DDI is pointed to this context:

[a2billing-did-to-sip]
exten => _X.,1,DeadAgi(a2billing.php,2,did)
exten => _X.,2,Hangup

agi-conf2 >> it is for sip clients only, this module does not answer the call automatically: answer_call=NO, only when the SIP client answers it.


2. in a2billing
DDI is configured in the "INBOUND DDI > Add :: Search" section, it belongs to "first_did_group" DDI group.

3. in a2billing
In "INBOUND DDI > Destination" section the DDI is assigned to my a2billing account number and pointed to my SIP phone - "SIP/voip_acc_nr"




1. 2013-07-28 18:21:33 447929879632 441224378525 0 0.000 GBP 0.000 GBP 00:01 6987463811 ANSWER DID-ALEG 0.000 GBP 0.000 GBP n/a n/a

2. 2013-07-28 18:21:33 447929879632 SIP/441224378525 0 0.000 GBP 0.000 GBP 00:01 6987463811 ANSWER DID_VOIP 0.000 GBP 0.000 GBP n/a n/a