Inbound calls

[Janky]

Hello,

Having a bit of trouble routing inbound calls im sure its from incorrect configuration.

i have went through the documentation and setup in bound groups as well as DIDs etc. one thing that i notice is the DID configuration page in the admin gui shows an option for routing directly to one phone although i dont see this explained in the documentaiton at all. This is idealy all i need the inbound to do right now although ive attempted setting it up serveral ways with no luck.

main reason i think i may have someting configured wrong is when i attempt to make an inbound call to the server th asterisk CLI goes nuts scrolling the following.

-- Executing AGI("SIP/IP.IP.IP.19-b7b0d6b8", "agi-DID_route.agi") in new stack
[Jul 21 11:58:03] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi

is this the corect agi it should be launching for an incoming call??

any advice is much appreciated.

[mflorell]

Yes that is the proper AGI script to launch.

Can you post the Asterisk CLI output before and after that?

Can you post the agiout logfile output for this call?

[Janky]

well it scrolls repeatedly

[Jul 21 21:34:25] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[Jul 21 21:34:25] -- AGI Script agi-DID_route.agi completed, returning 0
[Jul 21 21:34:25] -- Executing AGI("SIP/64.xx.xx.9-b7b1b140", "agi-DID_route.agi") in new stack
[Jul 21 21:34:25] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[Jul 21 21:34:25] -- AGI Script agi-DID_route.agi completed, returning 0
[Jul 21 21:34:25] -- Executing AGI("SIP/64.xx.xx.9-b7b1b140", "agi-DID_route.agi") in new stack
[Jul 21 21:34:25] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[Jul 21 21:34:25] == Spawn extension (default, 7272552550, 1) exited non-zero on 'SIP/64.xx.xx.9-b7b1b140'
[Jul 21 21:34:25] -- Executing DeadAGI("SIP/64.xx.xx.9-b7b1b140", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[Jul 21 21:34:25] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0

prior to that is just usual things that are scrolling

[Jul 21 21:35:01] == Manager 'sendcron' logged on from 127.0.0.1
[Jul 21 21:35:01] == Parsing '/etc/asterisk/manager.conf': [Jul 21 21:35:01] Found
[Jul 21 21:35:01] == Manager 'sendcron' logged on from 127.0.0.1


the log file output is below but now looking at it as well i think i may see the issue lmk what you think

2010-07-21 21:37:18|agi-DID_route.agi|-- CALL LOG : ||INSERT INTO call_log SET uniqueid='1279762633.169', channel='SIP/64.xx.xx.9-b7b0d6b8', channel_group='DID_INBOUND', server_ip='69. xx.xx.13', type='SIP', extension='7272552550', number_dialed='7272552550', caller_code='7275554577', start_time='2010-07-21 21:37:18', start_epoch='1279762638';|
2010-07-21 21:37:18|agi-DID_route.agi|exiting the DID app, transferring call to @ default

well maybe almost i made some more changes in the admin and now i receive this when calling in although nothing is heard on the calling end and there is no call showing in the realtime screen or being passed to the agent logged into the inbound campaign.

[Jul 21 22:27:41] -- Executing AGI("SIP/64.xx.xx.9-b7b0d6b8", "agi-DID_route.agi") in new stack
[Jul 21 22:27:41] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[Jul 21 22:27:41] -- AGI Script agi-DID_route.agi completed, returning 0
[Jul 21 22:27:41] -- Executing Answer("SIP/64.xx.xx.9-b7b0d6b8", "") in new stack
[Jul 21 22:27:41] -- Executing AGI("SIP/64.xx.xx.9-b7b0d6b8", "agi-VDAD_ALL_inbound.agi") in new stack
[Jul 21 22:27:41] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_inbound.agi
[Jul 21 22:27:43] -- Started music on hold, class 'default', on channel 'SIP/64.xx.xx.9-b7b0d6b8'
[Jul 21 22:27:43] -- Stopped music on hold on SIP/64.xx.xx.9-b7b0d6b8
[Jul 21 22:27:48] -- Started music on hold, class 'default', on channel 'SIP/64.x.xx.9-b7b0d6b8'
[Jul 21 22:27:48] -- Stopped music on hold on SIP/64.xx.xx.9-b7b0d6b8

[Janky]

well actually it looks like the call is showing up in the real time screen and i am receiving the hold message.

[Janky]

Ok i solved this i can not accept inbound calls via the ingroup and logging into the inbound campaign.

due to the fact that this automatically throws the person on the phone with the agent its not really going to work for my situation. can i configure this to just ring a certain phone extension? or is this something ill have to set manually. i saw the options for route to phone in the DID options but i cannot seem to get this to work although im only assuming that im makeing the corect settings changes.

[Janky]

ok i got this to work as well but i did it by setting the DID to EXTEN then specifying the phone extension below.

so i think where i am confused is that i don't understand the difference between the EXTEN setting and the PHONE setting in the DID settings.

is phone for calling a outside phone number?