Page 1 of 1

Inbound campaign setup problems

PostPosted: Wed May 28, 2014 4:40 pm
by syxteen
I setup an Inbound Campaign and DID according the manager's manual.
But when calls are made to the inbound number, on the other end it says "party dialed did not answer" and there are no calls being received in ViciDial.

Re: Inbound campaign setup problems

PostPosted: Wed May 28, 2014 6:39 pm
by syxteen
Code: Select all
  -- Executing [13053962284@trunkinbound:1] AGI("SIP/66.33.146.52-00000005", "agi-DID_route.agi") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
    -- <SIP/66.33.146.52-00000005>AGI Script agi-DID_route.agi completed, returning 0
    -- Executing [9998811112@default:1] Wait("SIP/66.33.146.52-00000005", "2") in new stack
    -- Executing [9998811112@default:2] Answer("SIP/66.33.146.52-00000005", "") in new stack
    -- Executing [9998811112@default:3] Playback("SIP/66.33.146.52-00000005", "ss-noservice") in new stack
    -- <SIP/66.33.146.52-00000005> Playing 'ss-noservice.gsm' (language 'en')
  == Spawn extension (default, 9998811112, 3) exited non-zero on 'SIP/66.33.146.52-00000005'
    -- Executing [h@default:1] AGI("SIP/66.33.146.52-00000005", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
    -- <SIP/66.33.146.52-00000005>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------- completed, returning 0


This asterisk cli output

Re: Inbound campaign setup problems

PostPosted: Thu May 29, 2014 6:19 am
by geoff3dmg
The CLI output would suggest that the call is going to the 'default' DID. This is normally because the DID you setup isn't matching what your carrier is sending you. Double check that. It needs to be a DID called '13053962284' according to the CLI output (as a rule I usually do a test call, then set up the DID based on the CLI rather than trust the carrier to send me what I expect).