3CX logo

3CX Phone System v12.5 Beta 2 Brings New & Improved Features

November 21, 2014 - 04:05pm

We are pleased to announce that the second beta release of 3CX Phone System v12.5 is now available for download. Based on your feedback, this release offers new and improved features, including the flexibility to configure your own ports and support for

globe communicatio

Experiencing Growing Pains? How Unified Comms Can Benefit Your Multilocation Corporation

November 05, 2014 - 01:11pm

Your company has experienced so much success that it has expanded into multiple locations, which means that congratulations—and an upgraded phone system—are in order. Now that your business has scaled, chances are you’ve outgrown your legacy phone

3CX PBX • View topic - Getting Caller ID to work with "Unsupported IP Phone" HT-503
3CX PBX • View topic - Getting Caller ID to work with "Unsupported IP Phone" HT-503

Getting Caller ID to work with "Unsupported IP Phone" HT-503

User to User - Answers are provided by the community. 3CX does NOT provide technical support via this forum. Commercial grade support should NOT be expected

Moderator: 3CX staff

Getting Caller ID to work with "Unsupported IP Phone" HT-503

Postby mcbsys » Fri Oct 10, 2008 6:23 am

This discussion was started some time ago along with other HT-503 issues:

http://www.3cx.com/forums/successful-first-implementation---grandstream-ht-2159.html

I thought I'd start a new discussion specifically regarding Caller ID.

With some fiddling, I have occasionally gotten the HT-503 to "read" incoming Caller ID and pass it along to 3CX, which then passes it to my phone. But so far it is erratic. Often the HT-503 doesn't detect the Caller ID, it just passes along the virtual extension (10000).

Values I'm testing:

Caller ID Scheme: Bellcore/Telcordia [I'm in San Diego, CA and this is the U.S. standard]
FSK Caller ID Minimum RX Level (dB): -40 [Changing this from -96 to 0 didn't make a difference]
FSK Caller ID Seizure Bits: 240 [at least one standard says to expect 30 bytes x 8 = 240 bits]
FSK Caller ID Mark Bits: 180 [one document says the mark signal is 150ms or 180 bits]

It's the last two values that I've been fiddling with the most. There is lots of info online as to what these mean, for example:

http://www.adventinstruments.com/resources/giart/giSTD2a.htm
http://www.asttechlabs.com/documents/make%20the%20call.cfm
http://www.tech-faq.com/caller-id.shtml

The main message from these documents is that the device receiving the Caller ID signal must be able to accept a wide range of values for Seizure and Mark Bits, since there are multiple standards, and variables within the standards. (This variety is especially evident in that first link.) However it seems that the HT-503 is looking for a very specific values for Seizure and Mark Bits.

Is this a design flaw? I see no way for a normal user to know exactly how many Seizure and Mark bits are being sent by the local telephone company, so how can the user set Seizure and Mark Bits for reliable Caller ID?

Mark
mcbsys
Specialist
Specialist
 
Posts: 76
Joined: Wed Oct 08, 2008 11:15 pm
Location: San Diego, California

Return to 3CX Phone System - General


Who is online

Users browsing this forum: No registered users and 1 guest