Manager Manual Tutorial F Issue

[Kinghtflyer]

Asterisk 1.4.44-vici
Vicibox 4.0 ISO
Build 120831-1523

No Sangoma or Dahdi Hardware on the system
Only 1 Sip Trunk carrier

Purchased and followed the Manager Manual with due diligence
Proceeded well until Page 29 Tutorial F.

Can Login agent and connect to the outbound campaign and the autodialed calls okay
Can make outbound manual calls okay
An inbound call makes it to the Vicibox but never to the Campaign.
Here is the Asterisk CLI output whenever I try and call in to DID 7026371447

[Sep 28 09:32:43] -- Executing [7026371447@inbound:1] Answer("SIP/vitel-inbound-00000010", "") in new stack
[Sep 28 09:32:43] == Auto fallthrough, channel 'SIP/vitel-inbound-00000010' status is 'UNKNOWN'

Thanks to the community for any help.

[Staydog]

Without looking at the back-end process, have you enabled inbound on the campaign and allowed the in-group? Assuming you have routed your DID to IN-GROUP; On the campaign you will put Y in Allow Inbound and Blended field and hit submit. When it reloads scroll to the bottom and above the submit button you will see fields for In-groups and Transfers; all your groups will be listed here and you just check the boxes on the ones you want to allow in the campaign. Make sure you have agents in the group and logged in, and it should route properly.

[Kinghtflyer]

I checked all that you recommended and the check marks showing the ingroups are selected.

I logged into the TEST-IN campaign with inbound allowed as a user with membership to the In-Group AGENTS-Vicidial
then placed a call to the DID.

Here is the CLI-Output from that call.

[Sep 28 18:14:32] -- Executing [7026371447@inbound:1] Answer("SIP/vitel-inbound-00000019", "") in new stack
[Sep 28 18:14:32] == Auto fallthrough, channel 'SIP/vitel-inbound-00000019' status is 'UNKNOWN'
[Sep 28 18:14:36] -- Executing [7026371447@inbound:1] Answer("SIP/vitel-inbound-0000001a", "") in new stack
[Sep 28 18:14:36] == Auto fallthrough, channel 'SIP/vitel-inbound-0000001a' status is 'UNKNOWN'

I would be willing to give you the root password and ip if that would help us locate the problem.
I have meticulously gone over the manual numerous times and am sure I have took the documented steps.
I am not confident of the setup from the SIP Provider. But since the call is hitting the server I guess that is okay.

Thanks again.
Randy

[williamconley]

[Sep 28 09:32:43] -- Executing [7026371447@inbound:1] Answer("SIP/vitel-inbound-00000010", "") in new stack

@inbound means the context the call is executing in is "inbound". But inbound calls are expected to be sent to "trunkinbound" not "inbound". The "account entry" for the carrier in admin->carriers should include "context=trunkinbound". No matter whether the trunk is expected to be used for inbound or outbound as this setting is not used for outbound anyway. Once it has been sent to "trunkinbound" instead of "inbound", it will land in the [trunkinbound] context in "extensions.conf" which turns control over to the inbound DID agi script provided by Vicidial ... and the call is then controlled by Vicidial instead of Asterisk Dial Plan.