- Community Home
- >
- Networking
- >
- Legacy
- >
- IP Telephony - NBX
- >
- Re: Error in the TAPI log
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2010 01:31 AM
07-08-2010 01:31 AM
Error in the TAPI log
Hello, I have an application that relies on the NBXTSP TAPI driver (v. 6.0.10). The driver is running against an NBX V3000 Analog (v 6.0.63). All this runs on Windows 2003 R2 23-bit (Service Pack 2).
My app runs perfectly fine for months at a time. However, every now and then, TAPI will become confused (I can't really find a better word) and as a result my app will crash. I dug into the NBXTSP logs (located at C:\Program Files\3Com\NBX\NBX TSP\logs) and found the following errors:
0706:011213 NBXTSP E T049C **** GetPhoneExtension(): Extension is not found under key (null)!
0706:011213 NBXTSP L T0924 TSPI_lineGetExtensionID() invoked (returning 0)
0706:011213 NBXTSP L T049C TSPI_lineGetDevCaps() invoked ### device 7
0706:011213 NBXTSP E T049C **** GetPhoneExtension(): Extension is not found under key (null)!
0706:011213 NBXTSP L T0924 TSPI_lineGetExtensionID() invoked (returning 0)
0706:011213 NBXTSP L T049C TSPI_lineGetDevCaps() invoked ### device 8
Best regards
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2010 11:14 AM
07-28-2010 11:14 AM
Re: Error in the TAPI log
I am using my own app that I wrote. I am simply using the NBX TAPI driver in my app to see what's going on in the system and facilitate things like transfers and so forth.
You mentioned that I can open a bug with you guys. Could you point me to a link? I actually found a bunch of bugs with the TAPI driver, but worked around most of them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2010 01:31 AM
07-08-2010 01:31 AM
Re: Error in the TAPI log
Hello, I have an application that relies on the NBXTSP TAPI driver (v. 6.0.10). The driver is running against an NBX V3000 Analog (v 6.0.63). All this runs on Windows 2003 R2 23-bit (Service Pack 2).
My app runs perfectly fine for months at a time. However, every now and then, TAPI will become confused (I can't really find a better word) and as a result my app will crash. I dug into the NBXTSP logs (located at C:\Program Files\3Com\NBX\NBX TSP\logs) and found the following errors:
0706:011213 NBXTSP E T049C **** GetPhoneExtension(): Extension is not found under key (null)!
0706:011213 NBXTSP L T0924 TSPI_lineGetExtensionID() invoked (returning 0)
0706:011213 NBXTSP L T049C TSPI_lineGetDevCaps() invoked ### device 7
0706:011213 NBXTSP E T049C **** GetPhoneExtension(): Extension is not found under key (null)!
0706:011213 NBXTSP L T0924 TSPI_lineGetExtensionID() invoked (returning 0)
0706:011213 NBXTSP L T049C TSPI_lineGetDevCaps() invoked ### device 8
Best regards
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2010 09:13 AM
07-13-2010 09:13 AM
Re: Error in the TAPI log
It sounds like some extension is trying to talk tapi to the pc, but is not registered.
check the extensions in the Control Panel/Phone and Modem options/nbx TSP and make
sure all the extensions are there
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2010 02:38 AM
07-14-2010 02:38 AM
Re: Error in the TAPI log
Since this error only happens once in a long while (so far happened 2 times in 14 months), the customer simply reboots the PC and everything is back to normal. They typically can't wait for me to wake up (i am on the wrong coast) and deal with their issue, because it's a 24x7 operation and they can't afford to be down for long. Thus, at the time the problem occurs it's impossible for me to see whether all extensions are in the ControlPanel/PhoneAndModemOptions list.
Are you saying that this problem is replicatable? In other words, all I have to do is to remove a previously registered extension from the ControlPanel/PhoneAndModemOptions list and I'll get the same error?
Or by "register", do you mean, registering the extensions with the NBX web interface?
Any suggestions on what to do to further troubleshoot this issue would be very welcome.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2010 01:53 PM
07-19-2010 01:53 PM
Re: Error in the TAPI log
Anyone have any ideas where I should go next troubleshooting this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2010 03:50 PM
07-28-2010 03:50 PM
Re: Error in the TAPI log
Do you have a contract with us ?
1800 876-3266 is our direct number .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2010 04:00 PM
07-28-2010 04:00 PM
Re: Error in the TAPI log
I do not have a contract. I did speak to folks at this number, and will probably use it on a one time basis. I think the price was quoted as $675 iirc.
But it seems like I can't file a bug unless I have a contract. I am just a contractor for a company that owns one of these NBX v3000 puppies, trying to help them out.
It's doubtful they'll be buying any contracts.