vicidial.org

VicidialNOW
Centos 5.4
Vicidial VERSION: 2.0.5-174
BUILD: 90522-0506

Hello everyone,

I have been running the predictive dialer for 3 weeks now and I say that it has been stable. Outbound works great. But, lately, there is a need for me to setup an inbound campaign. I have followed the steps on the manual. I have created a DID, pointed it to the correct DID number. I have also configured the SIP carrier settings and made sure that there is a context=trunkinbound in it. I can also confirm that the SIP is registered properly.

Calls are coming in now, but I am getting an error related to the context:

=====

-- Executing AGI("SIP/8001-b7923f08", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing Dial("SIP/8001-b7923f08", "SIP/mysipprovider/1XXXXXXXXXX||tTo") in new stack
-- Called mysipprovider/1XXXXXXXXXX
-- Got SIP response 482 "Loop Detected" back from xx.xxx.xx.xxx
-- Now forwarding SIP/8001-b7923f08 to 'Local/1XXXXXXXXXX@default' (thanks to SIP/mysipprovider-08bd0d28)
Jun 9 08:12:10 NOTICE[25416]: chan_local.c:526 local_alloc: No such extension/context 1XXXXXXXXXX@default creating local channel
Jun 9 08:12:10 NOTICE[25416]: app_dial.c:481 wait_for_answer: Unable to create local channel for call forward to 'Local/1XXXXXXXXXX@default' (cause = 0)
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing Hangup("SIP/8001-b7923f08", "") in new stack
== Spawn extension (default, 912697634923, 3) exited non-zero on 'SIP/8001-b7923f08'
-- Executing DeadAGI("SIP/8001-b7923f08", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----CHANUNAVAIL----------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0

=====

Note that it is still using "default" as the context. Its as if its not recognizing the trunkinbound setting on the carrier setup.

I hope someone can shed me some light regarding this.

Thank you in advance.

when you post, please post your entire configuration including (but not limited to) your installation method, vicidial version and build, asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

the "context" entry in your sip provider's entry in Admin->Carriers tells asterisk which context to send calls from this inbound trunk. When the carrier is identified, the call comes to the SIP context of the provider. Asterisk checks this context for a "context=????" entry. Then, in your dial plan (extensions.conf) it finds the named context and looks for the extension your provider "called" (the did).

If the context=default in your provider's sip context, instead of context=trunkinbound ... then it goes to the wrong place. all sip contexts for trunks should have context=trunkinbound (it has no effect on outbound, but it is necessary for inbounds!)