Inbound calls not transfer to conferences

All installation and configuration problems and questions

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

Inbound calls not transfer to conferences

Postby hvite » Mon Oct 05, 2009 2:53 pm

I have setup a new server VERSION: 2.0.5-173 BUILD: 90320-0424 and have setup inbound calls, but the inbound calls not transfer to conferences, Following is the CLI:

> requested format = ulaw,
> requested prefs = (ulaw|alaw|gsm),
> actual format = gsm,
> host prefs = (gsm|alaw|ulaw),
> priority = mine
-- Executing Answer("IAX2/peru-ti03-6067", "") in new stack
-- Executing AGI("IAX2/peru-ti03-6067", "agi-VDAD_ALL_inbound.agi|CID-----LB-----CLCLAROHOME-----7876253954-----"7875162761" <7875162761>-----park----------18000-----1") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_inbound.agi
Oct 5 10:34:05 WARNING[16090]: file.c:1185 ast_waitstream_full: Unexpected control subclass '20'
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
Oct 5 10:34:05 NOTICE[16096]: chan_local.c:526 local_alloc: No such extension/context 010*010*000*008*78600051@default creating local channel
Oct 5 10:34:05 NOTICE[16096]: channel.c:2514 __ast_request_and_dial: Unable to request channel Local/010*010*000*008*78600051@default
== Manager 'sendcron' logged off from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
-- Executing MeetMe("Local/58600051@default-6c96,2", "8600051|Fq") in new stack
> Channel Local/58600051@default-6c96,1 was answered.
-- Executing Answer("Local/58600051@default-6c96,1", "") in new stack
-- Executing Monitor("Local/58600051@default-6c96,1", "gsm|CLRHOME_7875162761_20091005-113405_2567") in new stack
-- Executing Wait("Local/58600051@default-6c96,1", "3600") in new stack
== Manager 'sendcron' logged off from 127.0.0.1
-- AGI Script agi-VDAD_ALL_inbound.agi completed, returning 0
Oct 5 10:34:06 WARNING[16090]: pbx.c:2377 __ast_pbx_run: Channel 'IAX2/peru-ti03-6067' sent into invalid extension '010*010*000*008*8600051' in context 'default', d handler
-- Executing DeadAGI("IAX2/peru-ti03-6067", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
-- Hungup 'IAX2/peru-ti03-6067'


Please help
hvite
 
Posts: 5
Joined: Mon Oct 05, 2009 1:30 pm

Postby williamconley » Mon Oct 05, 2009 9:44 pm

Thank you for posting your Vicidial Version and Build! That's excellent for a newbie (most people miss that entirely).

We will also need to know your install method and OS (if it isn't inherent in your install method) and if there is any other software installed on your system besides Vicidial (Trixbox, SugarCRM, etc)

I will hazard a question or two in the meantime:

Have you changed your IP address?
Code: Select all
010*010*000*008*78600051
Is 10.10.0.8 your system's IP?

How exactly do you have your DID set up? (IE: where does the DID Point? and does it exist, this thing that the DID is pointed to?)

I also note that:
Code: Select all
Executing MeetMe("Local/58600051@default-6c96,2", "8600051|Fq")
Appears AFTER your attempted DID inbound call. This could cause a problem if the system attempted to dial in to the meetme room before it existed.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # 888-883-8488 # +44(203) 769-2294
williamconley
 
Posts: 20441
Joined: Wed Oct 31, 2007 4:17 pm
Location: Bartow, FL (In the boondocks)

Postby hvite » Tue Oct 06, 2009 12:13 am

Hi williamconley

My SO is CentOS release 5.3 and only is vicidial, and I follow instructions from scratch_installation.

The Ip address the my server is 10.10.0.8

Inbout call is transferred from another asterisk server to the dialing plan 33336.

Part of my extensions.conf:
Code: Select all
;########################## VICIDIAL #######################################################

;##### This 'h' exten is VERY important for VICIDIAL usage,
;##### you will have problems if it is not in your dialplan!
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})

; MANDITORY VDAD extens:
; In this setup, the serverIP is the prefix followed by agent conf_exten
; These lines are REQUIRED for VICIDIAL to work properly
; local server extens:
; BE SURE TO CHANGE THIS LINE FOR YOUR IP ADDRESS!
        exten => _010*010*010*008*.,1,Goto(default,${EXTEN:16},1)
        exten => _8600XXX*.,1,AGI(agi-VDADfixCXFER.agi)
        exten => _78600XXX*.,1,AGI(agi-VDADfixCXFER.agi)

; Local blind monitoring
        ;exten => _08600XXX,1,Dial(${TRUNKblind}/6${EXTEN:1},55,To)
; OPTIONAL server 2 extens, needed for load balancing:
        ;exten => _010*010*010*016*.,1,Dial(${TRUNKIAX2}/${EXTEN:16},55,o)

exten => _33336,1,Answer                  ; Answer the line
exten => _33336,2,AGI(agi-VDAD_ALL_inbound.agi,CID-----LB-----CLCLAROHOME-----7876253954-----${CALLERID}-----park----------18000-----1)
exten => _33336,3,Hangup

; VICIDIAL conferences
exten => _86000[5-9]X,1,Meetme,${EXTEN}|F
exten => _86001XX,1,Meetme,${EXTEN}|F
exten => _8600200,1,Meetme,${EXTEN}|F
; quiet entry and leaving conferences for VICIDIAL
exten => _78600XXX,1,Meetme,${EXTEN:1}|Fq
; quiet monitor extensions for meetme rooms (for room managers)
;exten => _68600XXX,1,Meetme,${EXTEN:1}|Fmq
; quiet entry and leaving conferences for VICIDIAL
exten => _58600XXX,1,Meetme,${EXTEN:1}|Fmq

hvite
 
Posts: 5
Joined: Mon Oct 05, 2009 1:30 pm

Postby williamconley » Tue Oct 06, 2009 5:12 pm

CentOS is in the Redhat family and is not supported as a rule. Noone has anything against it, but it doesn't seem to be compatible with this software. The only exception to that is that if you BEGIN with VicidialNOW, the system will be CentOS and will be functional, and from there you may begin to make revisions.

VicidialNOW is not published by The Vicidial Group (which is not me, by the way, I'm just a loudmouthed visitor), but it does have it's own forum topic on the VICIDIAL forum, and has helped a lot of people who MUST have CentOS.

You will not likely enjoy trying to re-create the work done by the creator of vicidialnow any other way. Just want to be sure you understand that a scratch install on CentOS is not likely to work (I don't mean "not work well", I mean "Not Work").

That being said, you can check your /var/log/astguiclient log files and find out what the vicidial logic decided to do with that call, and perhaps from that find out why and resolve it.

However, if you search the forums you will not find many (any?) instances of a scratch install on CentOS working out. Use Vicibox or scratch install on Ubuntu. If you MUST have CentOS, install VicidialNOW and (after it runs successfully) make changes to that OS to suit your needs.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # 888-883-8488 # +44(203) 769-2294
williamconley
 
Posts: 20441
Joined: Wed Oct 31, 2007 4:17 pm
Location: Bartow, FL (In the boondocks)


Return to Support

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 432 guests