konsumingfire
Programmer
Am supporting a client who has this older Symposium version for Meridian. Using a custom TAPI 3.0 activex control that performs the dialing through a web page, commands the symposium server, which then connects through meridian which in turn connects to a digital m2008(?) desktop phone with headset for communication. At least I think this is how their end works. I inherited this code and this problem, so even though I am familiar with TAPI, I am pretty new to the Nortel world.
Client has been experiencing inability to disconnect the line, but usually only when the dialed number is disconnected and the call is intercepted by a phone company automated operator saying the line has been disconnected. Happens at other *seemingly* random times, usually related to some type of line interrupt, but far less frequently.
Also, I have been told that if the caller waits long enough (1 to 2 minutes but has been up to 10 minutes) the line will eventually disconnect and they will regain control over the phone.
In the code, I am letting the caller hang up the phone under all TAPI callstate events EXCEPT CS_DISCONNECTED. This is to keep the caller from hanging up an already disconnected line, which causes a system hang if it isn't handled.
I have used the logger.exe on their symposium server to monitor live call events, but am not sure even what to look for. Didn't see anything terribly suspicious.
I have not ruled out that it might be their symposium server configuration or meridian settings or some such thing, and at this point I am leaning toward that direction because TAPI is relatively simple, and I have spent a couple of weeks poring over the code and can't seem to find any obvious problems except for shoddy programming style and some kludgy algorithms; however, materially everything seems OK.
Client claims to have more than enough free licenses.
Client has been experiencing inability to disconnect the line, but usually only when the dialed number is disconnected and the call is intercepted by a phone company automated operator saying the line has been disconnected. Happens at other *seemingly* random times, usually related to some type of line interrupt, but far less frequently.
Also, I have been told that if the caller waits long enough (1 to 2 minutes but has been up to 10 minutes) the line will eventually disconnect and they will regain control over the phone.
In the code, I am letting the caller hang up the phone under all TAPI callstate events EXCEPT CS_DISCONNECTED. This is to keep the caller from hanging up an already disconnected line, which causes a system hang if it isn't handled.
I have used the logger.exe on their symposium server to monitor live call events, but am not sure even what to look for. Didn't see anything terribly suspicious.
I have not ruled out that it might be their symposium server configuration or meridian settings or some such thing, and at this point I am leaning toward that direction because TAPI is relatively simple, and I have spent a couple of weeks poring over the code and can't seem to find any obvious problems except for shoddy programming style and some kludgy algorithms; however, materially everything seems OK.
Client claims to have more than enough free licenses.
