vicidial.org

Hi,
Goautodial CE 2.0
VERSION: 2.2.1-237
BUILD: 100510-2015

I have already setup trunks from which i can dial outbound, however, i would like to setup a SIP for Inbound calls now. If someone can help me configure INBOUND carrier. Is it different than outbound trunk? What part would be different in setting up Inbound form Outbound? Also, once the inbound is setup, how can i receive calls using CAMPAIGNS?
Thank You for your help.

register your carrirer as per below

1. register => username:password@domainip/username


sipsettings
[siptrunk]
disallow=all
allow=ur codec "ulaw or g729"
username=username
fromuser=username
secret=password
host=domainip
context=trunkinbound =>this is the context used for incomming calls

2. go ingroups= add new ingroups for eg ukinbound

3. go to click Ingroups=create DID
add new did
enter ur did no

in DID route select Ingroups for ukinbound

3 go to ur campaign
allowcloser =Y
inbound blended=y
submit

4.again open the campaign ==detail screen

scroll down atlast u can see allowed ingroups selct ukinbound
submit

5.now go to user =select a user = agent select ingroups =y

blendeddefault check =y

now log in as agent you will be promoted with select ingroups
click the ingorup from left side it will be shift to left side and press submit

now make a incomming calls


and in same page INgroupid= selct ur ingroups for eg

Thanks dude, i will try it and let you know.

If you already have a WORKING outbound trunk which is registered to your carrier, the ONLY change you have to make to get calls into vicidial is to change "context=trunkinbound" in the "Account Entry" (if it was already there, change it, if it was not, add it).

If you did not need to use register => (no registration) to get the outbound trunk to work, you may or may not need it for inbound, depending on your carrier. (Some carriers allow or require setting this in their system directly, without registration.)

striker wrote:register your carrirer as per below

1. register => username:password@domainip/username


sipsettings
[siptrunk]
disallow=all
allow=ur codec "ulaw or g729"
username=username
fromuser=username
secret=password
host=domainip
context=trunkinbound =>this is the context used for incomming calls

2. go ingroups= add new ingroups for eg ukinbound

3. go to click Ingroups=create DID
add new did
enter ur did no

in DID route select Ingroups for ukinbound

3 go to ur campaign
allowcloser =Y
inbound blended=y
submit

4.again open the campaign ==detail screen

scroll down atlast u can see allowed ingroups selct ukinbound
submit

5.now go to user =select a user = agent select ingroups =y

blendeddefault check =y

now log in as agent you will be promoted with select ingroups
click the ingorup from left side it will be shift to left side and press submit

now make a incomming calls


and in same page INgroupid= selct ur ingroups for eg

Hey Striker,
I have done exactly what you have mentioned. Here is my CLI when i receive calls on my Goautdial

[May 27 17:48:23] -- Executing [144637074@trunkinbound:1] AGI("SIP/CT-00000013", "agi-DID_route.agi") in new stack
[May 27 17:48:23] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[May 27 17:48:23] -- AGI Script agi-DID_route.agi completed, returning 0
[May 27 17:48:23] == Auto fallthrough, channel 'SIP/CT-00000013' status is 'UNKNOWN'
[May 27 17:48:23] -- Executing [h@trunkinbound:1] DeadAGI("SIP/CT-00000013", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[May 27 17:48:23] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0


It seems like i am receiving call, however the agent who is logged in to receive inbound calls is not getting anything. Somehow the call that is coming in is not getting routed to the agent. I have followed all the instructions that you have mentiones, also i have read the Vicidial Manager's manual, and it is the same. Any ideas what can be wrong?

Post results of this on the Linux CLI:
tail /var/log/astguiclient/didin.2011-05-27

you can also look in the vicidial_did_log table for the same information.

mflorell wrote:Post results of this on the Linux CLI:
tail /var/log/astguiclient/didin.2011-05-27

you can also look in the vicidial_did_log table for the same information.

HEre is what i got

2011-05-27 17:43:16|1306500196.26|SIP/CT-00000010|144637074|Anonymous|Anonymous|||
NO default DID DEFINED! EXITING... 2011-05-27 17:43:16|1306500196.26|SIP/CT-00000010|144637074|Anonymous|Anonymous|
2011-05-27 17:46:30|1306500390.29|SIP/CT-00000011|144637074|Anonymous|Anonymous|||
NO default DID DEFINED! EXITING... 2011-05-27 17:46:30|1306500390.29|SIP/CT-00000011|144637074|Anonymous|Anonymous|
2011-05-27 17:48:23|1306500503.31|SIP/CT-00000013|144637074|Anonymous|Anonymous|||
NO default DID DEFINED! EXITING... 2011-05-27 17:48:23|1306500503.31|SIP/CT-00000013|144637074|Anonymous|Anonymous|
2011-05-27 18:09:39|1306501778.38|SIP/CT-00000016|144637074|Anonymous|Anonymous|||
NO default DID DEFINED! EXITING... 2011-05-27 18:09:39|1306501778.38|SIP/CT-00000016|144637074|Anonymous|Anonymous|
2011-05-27 18:09:56|1306501796.39|SIP/CT-00000017|144637074|Anonymous|Anonymous|||
NO default DID DEFINED! EXITING... 2011-05-27 18:09:56|1306501796.39|SIP/CT-00000017|144637074|Anonymous|Anonymous|

WHat does it mean? Can you please let me know what am i doing wrong?
Thanks

It means you need to create a DID entry with 'default' as the DID extension.

You should also create one for 144637074 for this specific number that you tried.

mflorell wrote:It means you need to create a DID entry with 'default' as the DID extension.

You should also create one for 144637074 for this specific number that you tried.

That worked out great. Thank You very much.

Just one moer question. What if i have more than one DID, how can i name them all default? How can i make it work with multiple DIDs. 144637074 this is the username for inbound SIP account i have, the DID number is 8609464041 i had this number at the DID Extension before i changed it to default.

You need to talk to your carrier then, they are not sending the DID, they are sending your account ID.

mflorell wrote:You need to talk to your carrier then, they are not sending the DID, they are sending your account ID.

Thanks for all your help mforell. I am able to get the calls by putting in the account number as DID extension. I can manage with account numbers as well.

Hello,

I did all what you have written above, yet nothing works fine,
cli debug is the following

Code: Select all

May 27 14:40:57] NOTICE[32703]: chan_sip.c:15147 handle_request_invite: Call from '' to extension '05751784450' rejected because extension not found.

Plz tell me what to do
Thanks.

As based from the discussion above, you need to create a DID entry for: 05751784450. Point it to an in-group or IVR then have it included in your campagin.

I have all done by manager manual, but I get this

Code: Select all

[Jul  5 08:47:08]     -- Executing [1444882e24@trunkinbound:1] AGI("SIP/1444882e24-000001ee", "agi-DID_route.agi") in new stack
[Jul  5 08:47:08]     -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[Jul  5 08:47:08]     -- AGI Script agi-DID_route.agi completed, returning 0
[Jul  5 08:47:08]     -- Executing [9998811112@default:1] Wait("SIP/1444882e24-000001ee", "2") in new stack
[Jul  5 08:47:10]     -- Executing [9998811112@default:2] Answer("SIP/1444882e24-000001ee", "") in new stack
[Jul  5 08:47:10]     -- Executing [9998811112@default:3] Playback("SIP/1444882e24-000001ee", "ss-noservice") in new stack
[Jul  5 08:47:10]     -- <SIP/1444882e24-000001ee> Playing 'ss-noservice' (language 'en')
[Jul  5 08:47:16]     -- Executing [9998811112@default:4] Playback("SIP/1444882e24-000001ee", "vm-goodbye") in new stack
[Jul  5 08:47:16]     -- <SIP/1444882e24-000001ee> Playing 'vm-goodbye' (language 'en')
[Jul  5 08:47:16]     -- Executing [9998811112@default:5] Hangup("SIP/1444882e24-000001ee", "") in new stack
[Jul  5 08:47:16]   == Spawn extension (default, 9998811112, 5) exited non-zero on 'SIP/1444882e24-000001ee'
[Jul  5 08:47:16]     -- Executing [h@default:1] DeadAGI("SIP/1444882e24-000001ee", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack


and this is my /var/log/astguiclient/didin.2011-07-05

Code: Select all

2012-07-05 08:45:13|1341470713.501|SIP/1444882e24-000001eb|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 08:45:55|1341470755.502|SIP/1444882e24-000001ec|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 08:46:16|1341470776.503|SIP/1444882e24-000001ed|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 08:47:08|1341470828.504|SIP/1444882e24-000001ee|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 08:49:48|1341470988.506|SIP/1444882e24-000001ef|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 08:58:40|1341471520.507|SIP/1444882e24-000001f0|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 09:13:52|1341472432.547|SIP/sipgateinbound-00000211|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 09:23:05|1341472985.556|SIP/sipgateinbound-0000021a|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 09:29:37|1341473377.572|SIP/sipgateinbound-00000227|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 09:34:30|1341473670.584|SIP/sipgateinbound-00000230|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 09:38:20|1341473900.593|SIP/sipgateinbound-00000239|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 09:39:01|1341473941.597|SIP/sipgateinbound-0000023a|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 09:42:33|1341474153.603|SIP/sipgateinbound-0000023d|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 11:55:51|1341482151.715|SIP/sipgateinbound-000002a8|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 12:04:37|1341482677.725|SIP/sipgateinbound-000002af|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 12:22:44|1341483764.739|SIP/sipgate.de-000002b4|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 12:29:54|1341484194.745|SIP/sipgate.de-000002b7|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 12:37:48|1341484668.753|SIP/sipgate.de-000002bc|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 13:26:49|1341487609.776|SIP/sipgate.de-000002c9|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 13:39:42|1341488382.796|SIP/sipgate.de-000002ce|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 13:44:35|1341488675.800|SIP/sipgate.de-000002cf|1444882e24|0038762723254|089416149286|1|EXTEN|
2012-07-05 14:24:36|1341491076.810|SIP/sipgate.de-000002d8|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:24:58|1341491098.815|SIP/sipgate.de-000002dd|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:28:37|1341491317.829|SIP/sipgate.de-000002e8|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:35:44|1341491744.837|SIP/sipgate.de-000002ed|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:38:59|1341491939.843|SIP/sipgate.de-000002f0|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:40:35|1341492035.846|SIP/sipgate.de-000002f3|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:43:24|1341492204.852|SIP/sipgate.de-000002f6|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:49:59|1341492599.862|SIP/sipgate.de-000002fd|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:50:17|1341492617.863|SIP/sipgate.de-000002fe|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:54:45|1341492885.869|SIP/sipgate.de-00000301|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 14:58:56|1341493136.875|SIP/sipgate.de-00000304|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 15:05:25|1341493525.888|SIP/sipgate.de-0000030f|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 15:05:43|1341493543.889|SIP/sipgate.de-00000310|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 15:23:44|1341494624.934|SIP/sipgatede-0000033b|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 15:34:23|1341495263.977|SIP/sipgatede-00000351|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 15:34:48|1341495288.978|SIP/sipgatede-00000352|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 15:38:23|1341495503.988|SIP/sipgatede-00000359|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 15:50:18|1341496218.1008|SIP/sipgatede-00000368|1444882e24|089416149286|089416149286|1|EXTEN|
2012-07-05 16:28:59|1341498539.1038|SIP/sipgatede-00000385|1444882e24|089416149286|089416149286|7|EXTEN|
2012-07-05 16:30:21|1341498621.1039|SIP/sipgatede-00000386|1444882e24|089416149286|089416149286|7|EXTEN|


I solved my problem at this moment by wrote above @mflorell

Hi
I have similar problem . Like this :

kashutu wrote:

mflorell wrote:You need to talk to your carrier then, they are not sending the DID, they are sending your account ID.

Thanks for all your help mforell. I am able to get the calls by putting in the account number as DID extension. I can manage with account numbers as well.

Whenver i am sending calls to in group , i dont where should i redirect my CallCentric DID . For Example , if i do this :

8019@Myipaddress and point my DID to EXTEN 8019 i can receive call in 8019. BUT
if i do
Ingroupname@Myipaddress i get message similar to above .

My version are server config is same as @ kashutu

shisdew,

I don't think you would point you callcentric to ingroupname@youripaddress. You point it to number@ipaddress then on the DID configurations in vicidial point it to your in_group or the call menu or an extension or whatever. Should be a drop down.

cc