Hello i am a new participator but an old visitor of these forums and would love some help.
I am currently developing an CB,Position and EWT play application in Composer.
i have encountered a problem where after the treatment(application) ends, i route the call back to the originating RP, and then back to the VQ it was queuing in, but the entered call is treated as a new interaction(and is also gets a new ConnID) and therefor spams the VQ with additional call for each re-entry.
I must be doing something wrong but havenât managed to figure out what exactly.
btw i also tried routing the call to GVP using a few function in IRD as well as a treatment withing the target block.
and i tried to transfer the call from GVP by using the transfer call and Route request blocks.
Your agents are on same sip server as GVP?
If not, be sure to be using ISCC correctly.
If yes, check your sip server logs to see why a new connid is created
And secondly regarding your question. yes i believe my Agents are on the same server as GVP, my developing environment has only one active sip server atm.
will check sip server logs to see what might be creating a new ConnID and will update asap.
Hi, Under URS logs i can see a RequestSingleStepTransfer coming from GVP. Ivâe attached a part of the URS log here,
I hope it helps(Obviously ivâe change the sensitive info:
Iâm using the transfer block in composer with these settings:
Connect Timeout: 16
Connect When: Immediate
Destination: sip:705201@ -------> this is also the originating RP where the target VQ is.
Max Call Duration:0
Transfer Type:blind
@hsujdik The problem i am having is a call is routed from a strategy to an IVR application to offer callback collect digits etc..
and once the application is done it routs the call back to the originating RP where the strategy above is loaded.
and URS or some other component treats the routed call from GVP as a new one.
Thus creating a new AttributeConnID and obviously multiple calls on the one VQ, when there is only one live call.
I do not understand why you use transfer within IVR if this can be achieved easily via URS centric mode. However, try to post entire T-Server log to find out the root-cause of the release.
Is it URS who send call back to original RP? If yes, how it knows when to do it?
Referred in URS log SingleTransfer is part of default routing (executed by URS function Default).
Probably check strategy/solution in this regards - after default routing strategy cannot be continued anyway.
Both of our environment production and development are GVP centric. And we use a before and After IVR strategies for all our CC. The reason is we have migrated many CCs from our old Genesys 7.2 environment to the new 8.1 one, so we kept the overall scheme.
And I wasnât at the organization when the desicion was made.
Regardless ill post the log when I get back to the office.