When is a call answered? 1

[BIS]

Hi All,

Does anybody know when the switch considers a call as being answered? Suppose a call comes in, goes through some elaborate vector processing, then finally gets a "disconnect after announcement none" treatment. If I set up a simple test, I always seem to get a ring before the disconnect happens. Does the G3R always send a ring as sort of like an answer? Then proceeds with vector proccessing.. Am I making myself clear?

 

[mcopini]

The caller will always hear at least half a ring before being connnected to anything. This is the time the call takes to be set up by the Definity or by your local provider's switch.
Usually, vectors are setup with a wait-time x seconds hearing ringback/silence as a first step. This will, depending on the amount of seconds you put in for the x cause the caller to hear a ring.
Concerning your question: 'when is a call answered': this depends on what call-reports you are using and on a lot of other things. In order for me (or others) to answer your question, you should be a bit more specific. Put it up here and I will have a look.

Kind Regards,
Maarten Copini

http://www.effecta.nl

-Please let me know if this was of any help-

 

[EPalle]

No, normally you will not hear a ringtone.
But that depends on the content of the vector.

Can you put it on here so that we can have a look?

Thx,
Palle

 

[BIS]

Hmm. Ok, take this scenario. VDN goes to vector, vector looks something like this (simplified).
01-wait-time 0 sec hearing silence
02-disconnect after announcement none
03-stop

In this case, I still hear a ring signal, even though I would think that the call would get disconnected immediately. I guess this has something to do with the provider then.

 

[BIS]

To be more precise guys, there is actually a converse-on step (for conversant) in between. The conversant simply records details in a database table, then returns the call and passes digits to the vector.Something like this:
01-wait-time 0 sec hearing silence
02-converse-on skill XXX pass VDN and XXX
03-wait-time 0 sec hearing silence
04-collect X digits after announcement none
05-wait-time 0 sec hearing silence
06-goto step 31 if digits=X
.
31-disconnect after announcement none
32-stop

I hope this is clearer....
In this scenario I always get 1 ring tone before the disconnect happens.

 

[EPalle]

Ha, a conversant..
Sad to say, that I don't have one (so can't help you out on that).
The vector is OK, you should not get a ring, so I guess that the conversant is giving the problem or your provider.

Try to remove the conversant link out of the vector and try again, if you still have a ring, the conversant is not the problem.

EPalle

 

[mcopini]

Using 0 seconds wait-time after a converse-on step is nòt recommended. Depending on how much time the script in the conversant takes, you should enter more seconds in this step. Zero seconds wait-time will not allow the conversant to do his thing...maybe this is why the Definity puts in a ring anyway...

Kind Regards,
Maarten Copini

http://www.effecta.nl

-Please let me know if this was of any help-

 

[BIS]

mcopini,
the 0 sec is basically just to allow the processor to 'wake up'. I seem to get unreliable results without this step. But you could be right, the ring I hear might be caused by the call being treated by the conversant. The whole script takes around 3 seconds if this is of any use.

 

[def1]

If you have a CMS attached to the Definity you will probably see the call in the 'RING' state on one of the AAS Agents with Skill XXX (Reports >Realtime >Skill Status). When the call is passed to the Conversant using the Converse step it normally takes around 3s to be answered, during which time you hear ringtone.

I've never seen a call going to the conversant (or other IVRs) using a converse step where you don't hear ringtone before the IVR processing begins.

 

[BIS]

def1 - thanks. that's pretty clear. I guess I will just have to live with it. I do have CMS and you are quite right.

 

[Definity]

BIS,
You are getting the ring because the agents set for the conversant skill are in AAS & when the vector does the routing of the call onto the conversant port the ring is extended to the conversant from Definity so that the port on conversant can go Off-Hook & that's the ring you get.

I don't think can get out of the ring of conversant port & have to live with the half ring which conversant takes to go off hook.

Let me know if I could make it clear.

 

[mpls]

If you are using ISDN-PRI trunks, the switch sends the answer message to the CO immediately when vector processing starts.