Inbound CID Callback Prompt Not Working

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Inbound CID Callback Prompt Not Working

Postby Sufyan Khan » Mon Jan 23, 2023 8:50 pm

Version: 2.14b0.5
SVN Version: 3611
DB Schema Version: 1662
DB Schema Update Date: 2022-07-12 00:11:33
BUILD: 220623-0824
Standalone Cloud Server

Hello guys,
I hope you are doing well. I have been trying to setup callback function in ingroup from last 3 days but lock, no matter what option I select my call is being hanged up if I select Estimated Hold Time Option as CALLERID_CALLBACK. Tried to search in manual either couldn't find anything in it. Press_CALLBACK_QUEUE is working fine and whenever I go live in call is being dailed but CALLERID_CALLBACK option not working. I am sharing my screenshot below please guide me if anything needs to be done. Please let me know if you need more information from side.

Screenshot#1: Image
Screenshot#2: Image

Logs:
[Jan 23 20:06:04] -- <SIP/101-00012703> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:04] -- <SIP/101-00012703> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:04] -- <SIP/101-00012703>AGI Script agi-VDAD_ALL_inbound.agi completed, returning 0
[Jan 23 20:06:04] -- Executing [8300@default:1] Hangup("SIP/101-00012703", "") in new stack
[Jan 23 20:06:04] == Spawn extension (default, 8300, 1) exited non-zero on 'SIP/101-00012703'
[Jan 23 20:06:04] WARNING[5791][C-0001ce4c]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
[Jan 23 20:06:04] -- Executing [h@default:1] AGI("SIP/101-00012703", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------)") in new stack
[Jan 23 20:06:04] -- <SIP/101-00012703>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------) completed, returning 0
[Jan 23 20:06:06] == Manager 'sendcron' logged on from 127.0.0.1
[Jan 23 20:06:06] == Manager 'sendcron' logged off from 127.0.0.1
[Jan 23 20:06:32] == Using SIP RTP CoS mark 5
[Jan 23 20:06:32] > 0x7f8f1806e000 -- Strict RTP learning after remote address set to: 192.168.5.109:8000
[Jan 23 20:06:32] -- Executing [3214311650@defaultlog:1] AGI("SIP/101-00012704", "agi-NVA_recording.agi,BOTH------Y---Y---Y") in new stack
[Jan 23 20:06:32] -- Launched AGI Script /usr/share/asterisk/agi-bin/agi-NVA_recording.agi
[Jan 23 20:06:32] -- AGI Script Executing Application: (Monitor) Options: (wav,/var/spool/asterisk/monitor/MIX/20230123200632_101_3214311650)
[Jan 23 20:06:32] -- <SIP/101-00012704>AGI Script agi-NVA_recording.agi completed, returning 0
[Jan 23 20:06:32] -- Executing [3214311650@defaultlog:2] Goto("SIP/101-00012704", "default,3214311650,1") in new stack
[Jan 23 20:06:32] -- Goto (default,3214311650,1)
[Jan 23 20:06:32] -- Executing [3214311650@default:1] AGI("SIP/101-00012704", "agi-DID_route.agi") in new stack
[Jan 23 20:06:32] -- Launched AGI Script /usr/share/asterisk/agi-bin/agi-DID_route.agi
[Jan 23 20:06:32] -- <SIP/101-00012704>AGI Script agi-DID_route.agi completed, returning 0
[Jan 23 20:06:32] -- Executing [99909*4***DID@default:1] Answer("SIP/101-00012704", "") in new stack
[Jan 23 20:06:33] > 0x7f8f1806e000 -- Strict RTP qualifying stream type: audio
[Jan 23 20:06:33] > 0x7f8f1806e000 -- Strict RTP switching source address to 202.166.XXX.XXX:16971
[Jan 23 20:06:33] -- Executing [99909*4***DID@default:2] AGI("SIP/101-00012704", "agi-VDAD_ALL_inbound.agi") in new stack
[Jan 23 20:06:33] -- Launched AGI Script /usr/share/asterisk/agi-bin/agi-VDAD_ALL_inbound.agi
[Jan 23 20:06:33] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:33] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:35] -- Started music on hold, class 'CustomMOHaudio', on channel 'SIP/101-00012704'
[Jan 23 20:06:37] > 0x7f8f1806e000 -- Strict RTP learning complete - Locking on source address 202.166.XXX.XXX:16971
[Jan 23 20:06:38] -- Stopped music on hold on SIP/101-00012704
[Jan 23 20:06:38] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:38] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:38] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:38] -- <SIP/101-00012704> Playing 'OnHoldPromptInbound.slin' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:49] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:49] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:50] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:50] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:50] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:50] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:06:50] -- <SIP/101-00012704> Playing 'CB_IVR_3_Welcome_RecName.slin' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:07:00] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:07:00] -- <SIP/101-00012704> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Jan 23 20:07:00] -- <SIP/101-00012704>AGI Script agi-VDAD_ALL_inbound.agi completed, returning 0
[Jan 23 20:07:00] -- Executing [8300@default:1] Hangup("SIP/101-00012704", "") in new stack
[Jan 23 20:07:00] == Spawn extension (default, 8300, 1) exited non-zero on 'SIP/101-00012704'
[Jan 23 20:07:00] WARNING[5897][C-0001ce4d]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
[Jan 23 20:07:00] -- Executing [h@default:1] AGI("SIP/101-00012704", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------)") in new stack
[Jan 23 20:07:00] -- <SIP/101-00012704>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------) completed, returning 0
Sufyan Khan
 
Posts: 14
Joined: Wed Oct 16, 2019 3:36 pm

Re: Inbound CID Callback Prompt Not Working

Postby Sufyan Khan » Tue Jan 24, 2023 8:46 am

@carpenox, @William... anybody could you please help me on this
Sufyan Khan
 
Posts: 14
Joined: Wed Oct 16, 2019 3:36 pm

Re: Inbound CID Callback Prompt Not Working

Postby mflorell » Tue Jan 24, 2023 11:30 am

Your screenshots are not visible in this thread.
mflorell
Site Admin
 
Posts: 18108
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: Inbound CID Callback Prompt Not Working

Postby Sufyan Khan » Tue Jan 24, 2023 11:46 am

mflorell wrote:Your screenshots are not visible in this thread.

@mflorell thank you for your response, I have attached them again.

Image

Image
Sufyan Khan
 
Posts: 14
Joined: Wed Oct 16, 2019 3:36 pm

Re: Inbound CID Callback Prompt Not Working

Postby mflorell » Tue Jan 24, 2023 12:25 pm

2 of your CID Callback "Filename" entries are blank, you have to fill them all in for it to work.
mflorell
Site Admin
 
Posts: 18108
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: Inbound CID Callback Prompt Not Working

Postby Sufyan Khan » Tue Jan 24, 2023 12:34 pm

mflorell wrote:2 of your CID Callback "Filename" entries are blank, you have to fill them all in for it to work.


yes I did even all of the three options in "WAIT TIME OPTION" and in "Hold Time Option" issue is whenever I select CALLERID_CALLBACK or PRESS_CID_CALLBACK my calls get hangup when I press 1 or call is routed to WAIT TIME OPTION or HOLD TIME OPTION after specified seconds.
Sufyan Khan
 
Posts: 14
Joined: Wed Oct 16, 2019 3:36 pm

Re: Inbound CID Callback Prompt Not Working

Postby mflorell » Tue Jan 24, 2023 4:53 pm

Set your server setting to "AGI Output" to 'BOTH', then test again and post the screenlog output from the call.
mflorell
Site Admin
 
Posts: 18108
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: Inbound CID Callback Prompt Not Working

Postby Sufyan Khan » Wed Jan 25, 2023 4:09 pm

mflorell wrote:Set your server setting to "AGI Output" to 'BOTH', then test again and post the screenlog output from the call.

Hello @mflorell,

After lot of struggling now I can schedule the callback, I have selected List ID 501 instead of default List. Now leads is being created and showing in 501 List but how they are going to be dailed?
Also what if we want our clients to select the time of their own choice for callback? Can we do this or do we have to ask developer for it also we would like to take input of Name as well with callback number, Please guide. Thank you
Sufyan Khan
 
Posts: 14
Joined: Wed Oct 16, 2019 3:36 pm

Re: Inbound CID Callback Prompt Not Working

Postby Sufyan Khan » Wed Jan 25, 2023 8:26 pm

Calling issue is also resolved. List 501 leads status was set to HOLDTO and after adding Dialing Status as "HOLDTO" in campaign Dial Next Number is working fine.

I will really appreciate if you just could guide me about Callback Schedule. We want our client to chose callback time of his/her own choice along with Name. Is it possible in current system or we have to ask some developer for it.
Sufyan Khan
 
Posts: 14
Joined: Wed Oct 16, 2019 3:36 pm

Re: Inbound CID Callback Prompt Not Working

Postby mflorell » Thu Jan 26, 2023 5:40 am

There is currently no feature that allows a customer to set their own callback date and time over the phone. I'm sure something like that could be added, but it would require quite a lot of input from the customer, unless some sort of default sets of options were used.
mflorell
Site Admin
 
Posts: 18108
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: Inbound CID Callback Prompt Not Working

Postby Sufyan Khan » Thu Jan 26, 2023 2:31 pm

yes how does it sound if we give option to clients to select callback in one hour, two hour, today or tomorrow etc options so he can enter dtmf according... could you please tell which files then we have to touch?
Sufyan Khan
 
Posts: 14
Joined: Wed Oct 16, 2019 3:36 pm

Re: Inbound CID Callback Prompt Not Working

Postby mflorell » Thu Jan 26, 2023 11:07 pm

The "agi-VDAD_ALL_inbound.agi" script is the one that would need to be altered to add that functionality.
mflorell
Site Admin
 
Posts: 18108
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: Inbound CID Callback Prompt Not Working

Postby Sufyan Khan » Fri Jan 27, 2023 12:18 pm

thanks a lot, will look into it. :)
Sufyan Khan
 
Posts: 14
Joined: Wed Oct 16, 2019 3:36 pm


Return to Support

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 72 guests