3CX Phone System can be provisioned with Cisco 7940 IP Phones, and allow users to reduce their maintenance costs. This post will take you through the benefits of using 3CX Phone System with Cisco 7940.

Cisco 7940 IP Phones have a new boss : 3CX Phone System 12

January 21, 2014 - 03:58pm

Transition gradually to modern IP telephony with 3CX’s support for CISCO 7940 & 7960 phones Cisco 7940 IP phones stand proud on many a desk - they are good quality and look surprisingly good despite their age. Their problem - The Cisco Call

Service Pack 3 Delivers New Mac & Windows Clients and More Features!

Service Pack 3 Delivers New Mac & Windows Clients and More Features!

November 28, 2013 - 04:00pm

We've made great strides with 3CX Phone System 12, continually setting new standards within the PBX industry by providing key mobility and Unified Communications features. Following up from valuable feedback we've received from our customers,

3CX PBX • View topic - Getting Caller ID to work with Grandstream HT-503
3CX PBX • View topic - Getting Caller ID to work with Grandstream HT-503

Getting Caller ID to work with Grandstream 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

Moderators: kevin, 3CX staff

Getting Caller ID to work with Grandstream 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