vicidial.org

We created a campaign called "TEST_B"

Agents can get these calls w/no problem.

When i try to transfer to closer I can see it attempts one of two places (depending on local or internal).
local closer:
default, 90009*CL_TEST_B_L**4558**....
The closer is put back on hold with an annoying beep, waiting for a closer.

Looking at other posts, it appears that I need to create an ingroup called CL_TEST_B_L.

I'm not doubting that this would work, but Is there a way to choose the closer group I want in the campaign. It doesn't seem to make sense to me that every time I add a campaign i have to add a closer group. Am I missing something??


The internal closer extension 990009 doesn't seem to work. I get, that is an invalid extension

Code: Select all

  == Spawn extension (default, 990009*CL_TEST_B_L**4560**CallID*299*, 0) exited non-zero on 'SIP/22198-b7926248'
    -- Sent into invalid extension '990009*CL_TEST_B_L**4560**CallID*299*' in context 'default' on SIP/22198-b7926248
    -- Executing Playback("SIP/22198-b7926248", "invalid") in new stack

So I hate to ask 2 questions in a single post, but:
1. Do I have to manually add an ingroup for every campaign or can I specify the one i want somehow?
2. What is wrong with the 990009 extension?


Note: I found I can change the annoying message followed by the beeps by alter line 268 of the agi-VDADcloser_inboudCIDlookup.agi script!

Yes you do have to create that as an in-group. That is the default.

There is currently no way to select a different default in-group. This is a planned feature for the next release.

Thank you for the response, that saved me a lot of time looking for a feature that isn't there yet. I'll just make a note in the html so that people know that they have to create the ingroup manually.

Any idea about the other extension '9900099'? I just get a verbal message saying invalid extension.

It is actually '990009' not '9900099' This was something that was left out of the sample docs and sample dialplan in the 2.0.3 release. This too has been fixed in SVN.

Lucky Typo
I am actualy using 990009.

Which i don't see in extensions.conf

Originally I had thought that this would match
exten => _90009

After looking up how the asterisk pattern matching works, it appears that the "_" is simply just saying that I am doing pattern matching.

Should I also create 990009? Just make it the same as the other?

Yes, go ahead and add it and make it like the 90009 record

If I'm not mistaken, 990009 is for the local closer (closers on another server). Do we need to change this entry:

exten => _990009.,1,Answer ; Answer the line
exten => _990009.,2,AGI(agi-VDADcloser.agi,${EXTEN}-----START)
exten => _990009.,3,Hangup

to:

exten => _990009.,1,Answer ; Answer the line
exten => _990009.,2,AGI(,agi-VDAD_LB_closer.agi${EXTEN}-----START)
exten => _990009.,3,Hangup

to make transfer to local closers (closers on a different server on a multi-server setup) work?

How does the local transfer work (internal transfer is closer on the same server)?

You could actually use the LB version for both, there really isn't a reason to use the non-LB version.