inbound problem

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

inbound problem

Postby kpanik » Sun Feb 04, 2007 5:07 pm

Hi all,

SOrry ... I'm confused :roll: ... I would want to know if on the vicidial operator interface, the calls in entrance for the campaign in inbound can be seen like for outbound call ?
kpanik
 
Posts: 90
Joined: Wed Jun 14, 2006 4:21 am
Location: Italia

Postby mflorell » Sun Feb 04, 2007 9:45 pm

I'm not exactly sure what you are asking.

Inbound calls can be taken in VICIDIAL, you can also do blended inbound and outbound campaigns.
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby kpanik » Sun Feb 04, 2007 10:02 pm

there is my CLI.....

my server don't accept inbound call on my campaign !! :(

why ??





== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
-- Accepting call from '3356821175' to '112342701' on channel 0/31, span 1
-- Executing Ringing("Zap/31-1", "")
-- Executing Wait("Zap/31-1", "2")
-- Executing Answer("Zap/31-1", "")
-- Executing AGI("Zap/31-1", "agi-VDADcloser_inboundCID.agi,CLOSER-----0112342701-----CLOSER-----park----------999-----1")
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDADcloser_inboundCID.agi,CLOSER-----0112342701-----CLOSER-----park----------999-----1
AGI Tx >> agi_request: agi-VDADcloser_inboundCID.agi,CLOSER-----0112342701-----CLOSER-----park----------999-----1
AGI Tx >> agi_channel: Zap/31-1
AGI Tx >> agi_language: en
AGI Tx >> agi_type: Zap
AGI Tx >> agi_uniqueid: 1170644223.1
AGI Tx >> agi_callerid: 3356821175
AGI Tx >> agi_calleridname: unknown
AGI Tx >> agi_callingpres: 3
AGI Tx >> agi_callingani2: 0
AGI Tx >> agi_callington: 33
AGI Tx >> agi_callingtns: 0
AGI Tx >> agi_dnid: 112342701
AGI Tx >> agi_rdnis: unknown
AGI Tx >> agi_context: default
AGI Tx >> agi_extension: 112342701
AGI Tx >> agi_priority: 4
AGI Tx >> agi_enhanced: 0.0
AGI Tx >> agi_accountcode:
AGI Tx >>
-- AGI Script agi-VDADcloser_inboundCID.agi,CLOSER-----0112342701-----CLOSER-----park----------999-----1 completed, returning 0
-- Executing Hangup("Zap/31-1", "")
== Spawn extension (default, 112342701, 5) exited non-zero on 'Zap/31-1'
-- Executing DeadAGI("Zap/31-1", "agi://127.0.0.1:4577/call_log")
AGI Tx >> agi_network_script: call_log
AGI Tx >> agi_request: agi://127.0.0.1:4577/call_log
AGI Tx >> agi_channel: Zap/31-1
AGI Tx >> agi_language: en
AGI Tx >> agi_type: Zap
AGI Tx >> agi_uniqueid: 1170644223.1
AGI Tx >> agi_callerid: 3356821175
AGI Tx >> agi_calleridname: unknown
AGI Tx >> agi_callingpres: 3
AGI Tx >> agi_callingani2: 0
AGI Tx >> agi_callington: 33
AGI Tx >> agi_callingtns: 0
AGI Tx >> agi_dnid: 112342701
AGI Tx >> agi_rdnis: unknown
AGI Tx >> agi_context: default
AGI Tx >> agi_extension: h
AGI Tx >> agi_priority: 1
AGI Tx >> agi_enhanced: 0.0
AGI Tx >> agi_accountcode:
AGI Tx >>
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing DeadAGI("Zap/31-1", "agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG-----16---------------")
AGI Tx >> agi_network_script: VD_hangup--HVcauses--PRI-----NODEBUG-----16---------------
AGI Tx >> agi_request: agi://127.0.0.1:4577/VD_hangup--HVcause ... ----------
AGI Tx >> agi_channel: Zap/31-1
AGI Tx >> agi_language: en
AGI Tx >> agi_type: Zap
AGI Tx >> agi_uniqueid: 1170644223.1
AGI Tx >> agi_callerid: 3356821175
AGI Tx >> agi_calleridname: unknown
AGI Tx >> agi_callingpres: 3
AGI Tx >> agi_callingani2: 0
AGI Tx >> agi_callington: 33
AGI Tx >> agi_callingtns: 0
AGI Tx >> agi_dnid: 112342701
AGI Tx >> agi_rdnis: unknown
AGI Tx >> agi_context: default
AGI Tx >> agi_extension: h
AGI Tx >> agi_priority: 2
AGI Tx >> agi_enhanced: 0.0
AGI Tx >> agi_accountcode:
AGI Tx >>
-- AGI Script agi://127.0.0.1:4577/VD_hangup--HVcause ... ---------- completed, returning 0
-- Hungup 'Zap/31-1'
kpanik
 
Posts: 90
Joined: Wed Jun 14, 2006 4:21 am
Location: Italia

Postby gerski » Mon Feb 05, 2007 10:53 am

does your campaign has "Closer" include on campaign ID? (if updated to 2.0.3b you can use BLEND/INBND/*_C/*_B/*_I)

make sure you check the inbound group in campaign setting..

Purchase the Manager's Manual there are instruction there for inbound campaign.
gerski
 
Posts: 432
Joined: Fri Jul 14, 2006 6:21 am

Postby kpanik » Mon Feb 05, 2007 4:30 pm

ok... sorry my various problem is resolved !!!!!
:shock:

the problem has in my configuration in realtime !!

ON realtime configuration the comma

(agi-VDADcloser_inboundCID.agi,CLOSER-----0112342701-----CLOSER-----park----------999-----1)

they are from changing with the pipe .....

(agi-VDADcloser_inboundCID.agi|CLOSER-----0112342701-----CLOSER-----park----------999-----1)

:lol:
kpanik
 
Posts: 90
Joined: Wed Jun 14, 2006 4:21 am
Location: Italia


Return to Support

Who is online

Users browsing this forum: No registered users and 97 guests