provided by Star2Billing S.L.

Dear A2B user,

Scenario

When I call normal or standard calling card platform, call connects. After entering PIN number, I dial destination number. if by my mistake, I dialed the wrong number, so to disconnect, I press **.

then A2billing asks for new destination number.



But in CID Callback calls, in the same scenario, when I press ** the call hangsup totally. (I suppose it should ask for a new destination number..like in standard calling card application)

To make callback to work in the same way as std.calling card application, should I have to do some change in dialparm?

Can someone please help me


Thanks in advance

Regards
Senthil

I think this can be done via dialplan using the DIALSTATUS

I created a new dialplan for CID-callback. I am not good in Dialplan so can some dialplan expert check and let me know if this will wor?

ANY OTHER IDEAS or COMMENTS ARE MOST WELCOME


[custom-a2billing-cid-callback]
exten => _X.,1,NoOp(a2billing-cid-callback number: ${EXTEN})
exten => _X.,n,Ringing()
exten => _X.,n,Wait(1)
exten => _X.,n,DeadAGI(a2billing.php|2|cid-callback)
; Call plan based on Dialstatus
exten => s,n,NoOp( Dial Status: ${DIALSTATUS})
exten => s,n,Goto(s-${DIALSTATUS},1)

; DIALSTATUS - NO ANSWER
exten => s-NOANSWER,1,Playback(no-answer) ; new sound file no-answer configured
exten => s-NOANSWER,n,DeadAGI(a2billing.php|2|cid-callback)
exten => s-NOANSWER,n,Wait(2)
exten => s-NOANSWER,n, Hangup

; DIALSTATUS - CANCEL
exten => s-CANCEL,1,DeadAGI(a2billing.php|2|cid-callback)
exten => s-CANCEL,n,Wait(2)
exten => s-CANCEL,n,Hangup

; DIALSTATUS - CHANUNAVAIL
exten => s-CHANUNAVAIL,1,DeadAGI(a2billing.php|2|cid-callback)
exten => s-CHANUNAVAIL,n,wait(2)
exten => s-CHANUNAVAIL,n,Hangup

; DIALSTATUS - CONGESTION
exten => s-CONGESTION,1,Congestion

; DIALSTATUS - BUSY
exten => s-BUSY,1,Busy

;DIALSTATUS - OTHER
exten => _X.,n,Wait(2)
exten => _X.,n,Hangup