| What hardware is compatible with Callcentric? |
 |
Callcentric has tested and found the following hardware to be compatible with our service:
PBX Hardware:
Grandstream GXW 4XXX/8XXX
pbxnsip - CS410, v 2.1.2.2292
pbxnsip - CS425, v 2.1.2.2292
U4EA - Fusion 200/400, v
IP Phones
Grandstream - BudgeTone 101, v 1.0.6.7
Grandstream - BudgeTone 102, v 1.0.6.7
Grandstream - BudgeTone 200, v 1.1.0.13
Grandstream - GXP2000, v 1.0.1.9
Grandstream - GXP2020, v 1.1.5.15
Hitachi Cable - Wireless IP-5000 WiFi Phone, v 1.5.3 10
Polycom - SoundPoint IP 301, v 1.5.3
Polycom - SoundPoint IP 501, v 1.5.3
Polycom - SoundPoint IP 601, v 1.5.3
Sipura - SPA-841, v 3.1.4
Snom - 105, v 3.56
Snom - 190, v 3.60i
Snom - 200, v 3.56y
Snom - 220, v 3.56y
Snom - 300, v 5.5
Snom - 320, v 4.0
Snom - 360, v 4.0
Snom - 370, v 7.1.30
ATAs (Analog Telephony Adapters)
Cisco - ATA 186/188, v 3.2.1
D-Link - DVG-1402S, v S4.0S49 - We do NOT recommend this device
Grandstream - HandyTone 286, v 1.0.6.7
Grandstream - HandyTone 386, v 1.0.2.9
Grandstream - HandyTone 486 / 487, v 1.0.6.7
Grandstream - HandyTone 488, v 1.0.2.9
Grandstream - HandyTone 496, v 1.0.2.9
Grandstream - HandyTone 502, v 1.0.0.67
Grandstream - HandyTone 503, v 1.0.0.9
Innomedia - SIP MTA-6328, v 3.0.38
Linksys - PAP2, v 3.1.10(LS)
Linksys - PAP2T, v 3.1.10c
Linksys - SPA-2102, v 3.2.10
Linksys - SPA-3102, v 3.2.10
Linksys - SPA901, v 1.12a
Linksys - SPA921, v 4.1.12
Linksys - SPA922, v 4.1.12
Linksys - SPA941, v 4.1.12
Linksys - SPA942, v 4.1.12
Linksys - SPA962, v 5.2.2(SCb)
Linksys - SPA3000, v 3.1.7
Sipura - SPA-1000, v 2.0.13g
Sipura - SPA-1001, v 3.1.5
Sipura - SPA-2000, v 3.1.5
Sipura - SPA-2002, v 3.1.5
Sipura - SPA-2100, v 3.2.1
Sipura - SPA-3000, v 3.1.5
Sinoco - SGW-2200, v Sinoco/SGW-2200_125_522_1s
Telco Systems - AC-211, v 4.62 US (LDR 14)
The hardware above has been tested with the listed versions. Normally older and newer versions of the firmware listed will work, but we have only tested the versions listed above.
Callcentric subscribers have also had success using the following hardware, although we have not tested them ourselves:
Aastra - 9133i, v 1.4.0
AVM - FRITZ!Box, v 06.03.62
Cisco - 7900 Series Phones, v unknown
DrayTek - Various, v1.1
Epygi - Quadro, v3.0
Grandstream - GXV-3000, v 1.0.0.24
Linksys - RT31P2, v 2.0.13
Linksys - RTP300, v 3.1.17
Linksys - WIP300, v 1.00.06
Linksys - WIP330, v 1.00
Linksys - WRTP54G, v unknown
snom - M3 Wireless phone system
UTStarcom - F3000 5.90st
ZyXEL - Prestige 2000W WiFi Phone, v WJ.00.10
Some of the above devices may have features that are not compatible with Callcentric, however the devices above can at a minimum place and receive calls.
Many other vendors hardware should be compatible. If you have questions about other hardware please contact us. |
| RETURN TO TOP |
| Can I use the Callcentric service when I travel? |
|
Yes. Using either the Callcentric software on your computer, or an analog telephone adapter such as the Grandstream. Please be aware that the place you are traveling to must support the minimum requirements to use the service.
Please also note that in some countries using VoIP services like Callcentric may be illegal. It is your responsibility to determine whether using the Callcentric service complies with local laws. |
| RETURN TO TOP |
| What software is compatible with Callcentric? |
|
Callcentric has tested and found the following software to be compatible with our service:
PBX Software:
3CX - Phone System, v 3.1.2434.0
NCH Axon version 1.30
Digium - Asterisk, v 1.2.21 (only registering as SIP, no IAX)
Digium - Trixbox (formerly Asterisk@Home) v 2.2 (only registering as SIP, no IAX)
freePBX - Frontend for Asterisk, v 2.2.0 (only registering as SIP, no IAX)
pbxnsip - PBX, v 2.0.3.1715 (Win32)
Regular Softphones:
Microsoft - Windows Messenger, v 5.1
SJ Labs - SJphone, v 1.60 build 289a
Snom - Softphone, v 3.60j
Virbiage - Soft Phone ( Firefly 3rd party ), v 1.9.9 build 4521
Xten (now CounterPath) - X-Lite, v 2.0 build 1103m
Xten (now CounterPath) - X-Pro, v 2.0 build 1082
Xten (now CounterPath) - eyeBeam, v 1.1 build 3002s
NCH Express Talk version 3.03
Twinkle version 1.0.1 (May 2007)
The software above has been tested with the listed versions. Normally older and newer versions of the software listed will work, but we have only tested the versions listed above.
Callcentric subscribers have also had success using the following software, although we have not tested it ourselves:
Global IPtel - X-TAPI, v1104a
Linphone - Linphone, v1.1.0
Wirlab - KPhone, v4.2
Many other vendors software should be compatible. If you have questions about other software please contact us. |
| RETURN TO TOP |
| Can I use my VoIP phone with your service? |
|
Yes assuming that we support it. Many devices are currently supported and in general you can use any device that supports at least the following:
- SIP 2.0
- RTP over UDP
- DIGEST MD5 authentication
- Fixed Outbound Proxy
- DNS SRV
- G.711 and/or G.729
If after reviewing the supported equipment list you are still unsure if your device will work, please contact us. |
| RETURN TO TOP |
| What voice codec's does Callcentric support? |
|
For calls from one Callcentric user to another any Codec can be used.
For calls to the voicemail system and for error prompting the following codec's can be used:
GSM
G.729A
G.711 mu-law
G.711 A-law
For calls to the PSTN (traditional landline and mobile phones) the following codec's can be used:
G.723 6.3Kbps
G.729A
G.711 mu-law
G.711 A-law
For calls from the PSTN to your Real Phone Number the following codec's will be used:
G.729A
G.711 mu-law
We recommend that you configure your user agent's codec selection in the following order (with 1 being the highest priority, and 9 the lowest), assuming your user agent supports each of the following. If your user agent doesn't support all of these codec's, just skip the ones that it does not have.
1 - G.729
2 - G.723 6.3Kbps
3 - GSM
4 - iLBC
5 - Speex 8Kbps
6 - G.728
7 - G.726 16Kbps
8 - Speex 16Kbps
9 - G.726 24Kbps
10 - G.726 32Kbps
11 - Speex 32Kbps
12 - G.722 48Kbps
13 - G.722 56Kbps
14 - G.722 64Kbps
15 - G.711 mu-law
16 - G.711 A-law |
| RETURN TO TOP |
| Will Callcentric work over my satellite Internet connection? |
|
While it is technically possible for the Callcentric service to work over a Internet connecection via satellite, we do not recommend that you use the Callcentric service in this way.
With a satellite connection you will experience high latency (delay) in your conversations, and may experience echo or dropouts in the voice.
Callcentric will not officially support users that are using the Callcentric service over a satellite based Internet connection. |
| RETURN TO TOP |
| Can I use the Callcentric service with a dialup modem? |
|
Yes, you can use the Callcentric service with a dialup modem of 28.8 kbps or faster. However, in general you will find the Callcentric service to be less reliable and you may experience quality problems with calls on a dialup connection. We strongly recommend that you use the Callcentric service on broadband Internet connection such as ISDN BRI, DSL, Cable, T1, E1, Wi-Fi, Wi-Max, etc.
In order to use the Callcentric service with a modem connected to your computer, you will need user agent software that supports the G.729 codec. For more information on software user agents such as X-Lite and X-Pro, please visit the support area to see compatible software. |
| RETURN TO TOP |
| Does Callcentric support DTMF? |
|
Yes Callcentric does support DTMF.
We support both In-Band DTMF and Out of Band signaling through the industry standard RFC2833 specification.
We recommend sending DTMF through the RFC2833 standard since it provides a more reliable way of transmitting DTMF signals compared to In-Band where compression, especially with highly compressed codecs such as G.729, in combination with poor connection quality can distort DTMF signals and make them unrecognizable.
If you choose to use the In-Band DTMF signaling method and experience problems with sending DTMF tones you can try to solve this by choosing G.711 as your preferred/default codec. This way your signals will be sent but won't be as compressed as when they are sent with G.729, or more highly compressed codecs.
If you are not able to choose RFC2833 standard as your DTMF type in your device, you may also be able to select AVT which is the name used for RFC2833 on some devices. You may also try setting your DTMF signaling type to Auto; this will allow your UA to choose the most suitable signaling type.
Callcentric does not support SIP-Info at this time as a method of transporting DTMF signals.
Here is a short list which explains Callcentric DTMF support for SIP communications:
1 - In-Band: Requires a stable connection and works best with a less compressed codec such as G.711. An unstable connection can still affect DTMF signaling however.
2 - RFC2833/Out of band: Works with any codec, as long as your connection does not suffer from high packet loss/ poor quality
3 - SIP-Info: Not supported at this time
If you still aren't able to send DTMF tones you may open a trouble ticket by logging into your account to contact us. |
| RETURN TO TOP |
|
