Remote extenision as Solidus Agents.

[safron]

Hi Guys,

Mx ver:3.2 sp5 / Sec.6.0 sp2.

I was really seeking confirmation that this is possible or not.
I have Solidus agents in a remote location set up as mobile extension ie: type=MOB. on a different switch.
They work fine as far as taking making calls. Problem is they are uanble to use the hold/transfer facility from DM(F5) but its ok from the handset.
I was wondering if this is functionality or not.
In ALEX Sec docs there is a matrix that says RXN's shoiuld be able to use hold/transfer.
I have played around with ASPAC'S:123/124 &56 to no avail.
Does anybody have this function?

Thanks...Saf.

 

[doktor]

It should normally work. Have you tried with type=MOB where the device is a mobile phone or direct land line (PSTN) with just one phone?

///doktor

http://www.kandu.dk/spg153996.aspx

 

[doktor]

I have mostly seen issues, when the Solidus agents do not keep to the rules by dialling out through the MD110 or MX-ONE's R1 number.
If they do the direct dialling from their device to the PSTN without using the R1 number you will get wrong reports and trouble forced agent not ready.

///doktor

http://www.kandu.dk/spg153996.aspx

 

[doktor]

I was puzzled reading " on a different switch". Does this mean that the mobile extensions are initiated as extension numbers on a different telephone system.

If this is the case, I guess that you will have to use the Solidus Desktop Manager(Solidus Softphone) to transfer to the public DDI number of the "other" agent, not just transfer to the local extension number in telephone system.
Please explain furter.

///doktor

http://www.kandu.dk/spg153996.aspx

 

[whosrdaddy]

doktor,

they are just extensions on a different switch defined as remote extension in the MD110/MX-ONE.

safron,

like doktor already mentioned is that the agents need to form the R1 number so that the MD110 knows that the line is busy.
Check if the remote switch has hotline functionality, if so program the R1 number as hotline...


/Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[safron]

Guys,
thanks for the responses.
Yes they use a different switch with DM installed on their PC's.
So when Sec deflects a call to the associated Rxn it dials the indial number of their pbx.
The agent then tries to use DM to answer hold and transfer the call. (message says 'use the handse - which i've since learned).

Am i right to say applink cant control this calls so unable to use DM so they need to use any soft client or does this need to be Solidus Softphone?

With o/g calls no need to set up speed dial to R1 as they use DM to dial out which works fine.

thanks.

Saf.

 

[safron]

Guys...

Also regarding the problem where the mobile Sec agent transfers a call within its internal pabx, I.M shows the agents as busy until the transferred call is complete.

I presume applink has no way to monitor this transfer so is unable to clear the call until that call is closed?

thanks
Saf.

 

[doktor]

I guess if the agent on "other" PBX wants to transfer to his/her colleague, he/she will have to put the call on hold in DM and transfer it to the DDI number in the Aastra MX-ONE that corresponds to the colleagues real DDI number (Aastra MX-ONE DDI number) - and not the local extension number of the "other" PBX.

///doktor

http://www.kandu.dk/spg153996.aspx

 

[doktor]

Or better. Replace (only) the agents phones on the "other" PBX with Aastra IP phones connected to the MX-ONE where the Solidus is installed. (as "flying" IP phones, i.e. no MX at the site).

///doktor

http://www.kandu.dk/spg153996.aspx

 

[whosrdaddy]

^^^ +1

RXN is too much hassle...

safron you really need to go via R1 number for outgoing calls or else solidus won't know that the agent is busy! (and you get forced not ready when solidus tries to deflect a call to that busy agent)

/Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[safron]

So bottom line is using remote extension as Solidus agents really only works for basic making and taking calls. You would loose a lot of agent funcionality
I guess IP soft clients would be the way forward (if they are on the same WAN)?

thanks.

 

[safron]

Guys,

Sorry to go on about this. I have now enabled CLI on the PABX where remote extn resides (type =mob) This CLI matches NUTRI and REEXI.
I noticed that that when Solidus targets the remote extn and the extn tries to make an enquiry of transfer the call by dialing back to R1 number, the agent get Busy when dialing R1!

Didnt expect this, obviously the RXN is busy but not R1?

Apart from all this, enquiry and transfer on DM should by rights work for remote extns but doesnt

Saf.

Think i need to upgrade both Mx and Sec.

 

[whosrdaddy]

Hi Safron,

if you have Alex, please read the operational instructions concerning Remote extension.

in short: to do an inquiry, the mex user just has to press '*' (check aspac 124) on the phone, form number and press '#' (check aspac 127) to transfer the call. No need to dial R1 nr.

The agent only needs to call the R1 number when he wants to do an outgoing call (no incoming call attached)

/Daddy


-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[safron]

Daddy,

ok, not sure what aspac 127 has to do with this as this relates to callback missions?
Problems was, I was trying to dial into the Mx-One R1 to transfer the call to extn on the BP250.
Like you said all they need to dial is * ENQUIRY (aspac-124 =0) dial the four digit extn xxxx (set on REEXI) then hangup. No # required.
fanstastic!! I'm well chuffed.

One thing they did complain about was having to hit '*' 2 or 3 times. Not sure if this is because aspac 124 has to be 3 digits??
Or if the BP250 needs tweaking?

Anyway, thanks guys for you input as always.

Saf.