Alcatel Unleashed

Hi all,

i have a very weird one i have been working on for some time.

Basically i have a R6 OXO (all IP), many of the users use pimphony - switchboard user has Pimphony operator and about 10 users use Pimphony Pro.

The operator (who also uses a 4038) gets calls external calls on the 4038 and about 2 seconds later the calls flash up on Pimphony. When transferring the transfers also have around a 2/3 second delay whereas it is instantaneous from the handset.

Originally this was reported to Alcatel and they looked at clearing the cache/inodes on Pimphony -as a result a new build of Pimphony was released. the problem carried on so they blamed the PC. the PC was replaced with a top spec PC - graphics acceleration tried on varying levels, changed a few options on the very memory hugry Pimphony application, still no difference.

Alcatel then blamed the network - "must be a QOS issue." after carrying out an IP audit prioritising the Pimphony and Telephony traffic, giving the PC its own connection to the LANX card (not via the 4038 or even via the customers network!) still no difference.

I thought maybe its a configuration issue, after trying a few things myself - such as playing with the way the calls were routing, but i could not make any improvements.

Now Alcatel are out of ideas and sitting on our escalation, my question is why is it only the operator? also tried numerous PC's and different versions of Pimphony...

wonder if any of you have experienced this or a similar issue and how it was rectified?

Hum lets see.
Pimphony interconnects to OXO to see what is going on the 4038. So, when you run ethereal traces when something happens on the 4038, is there any network event from OXO to Pimphony? If not I'd point to OXO. 2 seconds is a lot of delay for CSTA events.

Did you try to use different config on operator (such as Pimphony basic with 4038; or 4035, or 4039, or 4019 with Pimphony Pro)? That is to try and see if it is a problem with the association of Pimphony Pro with 4038.

Regards.