RONA in an External Routing Point Alcatel 4400

[edobellamy]

Does anybody knows the correct setting for a CCD used as an external routing point to be able to retreive the call when not answered?

Currently the call is been routed to a remodte PBX and routed to an agent; but abandoned if not anwered.
Local RONA works fine.

[cavagnaro]

CCD can't be used as an external RP...
What you can do is configure the Pilot as a ACD Queue (check Tserver guide) and then use it on your strategy

[edobellamy]

Hi Cavagnaro;

Sorry is a RSI routing point.
I reckon the problem has to do with the ISCC configuration;

Currently is

extrouter]
cast-type=route
cof-ci-defer-create=0
cof-ci-defer-delete=0
cof-ci-req-tout=500 msec
cof-ci-wait-all=false
cof-feature=false
cof-rci-tout=10 sec
default-dn=
direct-digits-key=CDT_Track_Num
dn-for-unexpected-calls=
event-propagation=list
match-call-once=true
network-request-timeout=20 sec
reconnect-tout=15 sec
register-attempts=5
register-tout=60 sec
report-connid-changes=false
request-tout=20 sec
resource-allocation-mode=circular
resource-load-maximum=0
route-dn=
tcs-queue=
tcs-use=never
timeout=60 sec
use-data-from=original
use-implicit-access-numbers=false

the ISCC client is closing the call without overflow


Target type is Target ISCC
Route type Route

[cavagnaro]

ISCC? I don't get it, can you explain what you are trying to achieve? Will OXE transfer or receive the call?

[edobellamy]

Switch 1 sends an call to an external rp in Switch 2 for an agent in switch 2;
if unable to connect the call it should overflow to a local Swith 1 rona routing point:

This happens but then the call is not correctly handled by URS, it seems the connid of the call is been modified on RONA;

So the call remains in a rebounding between two RONA routing points

[edobellamy]

For further clarification this is the scenario

- Call arrives in PBX 1 in RP1 with no agents available 
- Strategy sees an agent in PBX 2 and routes through ISCC to External RP in PBX 2 from PBX 1 RP1
- Call is diverted and rings in agent PBX 2 ISCC tranfer succeded message is emited
- Call info is deleted in ISCC
- Call is not answered and is diverted from PBX 1 RP1 to the Rona RP2 but in doing so; it creates a new ConnID and routing data is lost
- Call stays in vicious cycle in RONA

So the problem is how to stop ISCC to Send a Tranfer Succeded before Establish or how to reconnect the data when diverted.

[fnunezsa]

From the depicted call flow it seems like you have ISCC correctly configure from PBX1 to PBX2 but not the other way around. Double check that configuration, maybe there is no ERP in PBX1 so attached data is lost.

[edobellamy]

Hi there is; I reckon it has to do with the COF-In DNs; Call Overflow functionality; but as always; documentation is very sparse; My Idea is to define the Rona where the call is overflowing two as a new call as a COF-In Access resource, if a understand correctly ISCC would try to match the call to the connected PBXs, and through the Network Id match it, has anybody done something like that?

[edobellamy]

Alas; given that the call is recalled and rerouted through a SCP; all attributes are changed;
there is nothing for the ISCC COF funtionallity to match the call, too bad that is not possible to configure a combination of attributes to match the call 
So need to change the routing strategies; for which I have no ownership.