Tapi and Ip Office 3.0(531)

[MisterLister]

IP403 3.0(531)
IP400 DT30 5.0(531)
TAPI 1.0.0.25
Phone Manager 3.0.14

I had recently upgraded our phone system to version 3.0 from version 2.1(24). since the upgrade we have had a problem with our inhouse call logging system.

On v2.1 when an external call was passed from extA to extB, extB would get a popup giving all the callers details
Company Name, Contract Number etc...
Now there are no popups unless the external call goes directly to the extB via the DDI.

Is there any known issues with the TAPI within this firmware or is there a new option that has to be checked to allow extA to pass to extB the external CLI?

thanks
Mark

 

[JeSTeROCK]

Depends which way the call is transfered. If done with a blind transfer then it will pop up correctly.

If using a supervised transfer it will try and pop from the internal extension number

 

[MisterLister]

1.
the external call comes in answered by extA, the call is placed on hold, extA dials extB, when the ringing starts extA puts the handset down.

No popup at extB.


2.
the external call comes in answered by extA, the call is placed on hold, extA dials extB, extB answers and talks to extA, extA puts the handset down.

No popup at extB.


3.
the external call comes in directly to extB via the DDI.

Popup appears at extB.


extA = reception
extB = a user within the org.

hopes this gives a clearer picture to what is happening with the calls.

 

[JeSTeROCK]

Try using the phone manager or softconsole to doa blind transfer and see if that works

 

[MisterLister]

have tested your suggestion jesterock, all four tests failed to make a popup appear on extB.

when we used v2.1 no matter what ext put through the call or how; there would be a popup appear at the recieving ext.

looks like i will end up down grading the ip office equipment to get back the function we have lost by doing the upgrade.

 

[intrigrant]

Hm, my docs tells me only to use the 2.1 user software for 3.0DT versions. Did i miss something?

 

[aramsay]

This is a "feature" that we found was introduced somewhere around 2.1.29

It's there on the 3.0.59 as well; especially bad on analogue extensions where you don't have phone manager, as even after the transfer you still don't see the CallerID (obviously).

We've just had to learn to live with it

 

[MisterLister]

intrigrant wrote
Hm, my docs tells me only to use the 2.1 user software for 3.0DT versions. Did i miss something?

you are correct with using user cd 2.1 PhoneManager 2.1.7
but trying to get around this problem i installed 3.0.14 onto a test pc but still did not fix the prob.
the pm3.0.14 seems to be working fine even after i downgraded the ipo 400+403 to version 2.1. but there is more testing to be done on the phone manager before i am happy with the new version.

 

[ripper65]

I have tested differences with CLI on extn B when performing supervised transfer from extn A so I think the fault lays with the core software. Version 3.0 (531) has just had a maintenance release to 3.0 (535) which has the same fixs as 2.1.(44) it would be worth trying 3.0 (535).