How to use URS AFTER AGENT DISCONNECTS CALL!

[LeszekM]

Victor,
going on Fra's and mine idea:
You don't need to know the state of the technical DN at all. All you need is (besides love ;-) ) is just a way to originate many calls from it. In other words: you have to develop a SIP device that is able to place many calls to the routing point.

You don't have to have exactly 1 technical DN - you could have a pool of technical DNs if you're affraid it doesn't work in a large call center.  Then agent app would choose randomly which DN from the pool to use. It is not important which technical DN calls to the routing point.

Regards,
Leszek

[René]

Hi Vic,

I can't help myself but you are not doing well trying to hack URS to implement required operations. Why?

1/ URS simply doesn't support such feature and trying to implement it means that you're pushing the product to work in way it wasn't designed for. So it could lead to some unpredictable issues later in the production. Is it really worth it?

2/ URS wasn't developed as a tool used for writing data to database. It's routing engine...

3/ If the customer has CRM system then business data related to customer's call should be stored in this system. Why using CTI system or part of it (URS) for a task that isn't related to CTI?

4/ I don't have sufficient information about your business case but what about offering SIP Server ACD functionality + CRM in first step and add URS later.

R.