<?xml version="1.0"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
		<channel><title>[Thinktel Support Center] Recently Changed Articles</title><link>http://support.jumpshop.com/index.php/rss/kb/recent_changes</link><description></description><item><title>How do I factory reset my Linksys or Cisco phone and reprovision it?</title><description>Factory Resetting Phone  
  
Select the menu button on your phone (below voicemail button, looks like a sheet of paper with a folded corner) and scroll down to the Factory Reset menu choice.  Select this feature and follow the steps to factory reset the device.  
  
Once completed and the phone has powered back up to main screen press the options button on your phone and scroll down to the Network menu choice.  In here you should find the phones ip address on the local network.   
  
Go to your computer, open your web browser, and enter http://192.168.x.x replacing the x.x part with the ip address obtained in the address bar of the browser and navigate to the site.  You'll see an administration panel where you can view the status of your phone as well as configure it.  
  
At the top right section you should see two links.  Click admin first, wait for the page to reload.  Next click on advanced and wait for page to reload.  
  
Provisioning the phone  
  
Click on the Provisioning Tab and ensure 'Provision Enable' is set to yes  
  
Set 'Profile Rule' to: http://provision.thinktel.ca/init.cfg  
  
Click on 'Submit All Changes'  
  
Your Cisco/Linksys device will reboot up to four times with firmware potentially being upgraded if out of date  
  
Please note: It can take up to 10 minutes for your device to populate in our provisioning servers  
  
Quote your device MAC address or serial number when placing orders for VoIP service on your Cisco/Linksys hardware  
</description><link>http://support.jumpshop.com/index.php/kb/article/92</link><pubDate>Thu, 17 Jun 2010 13:29:13 GMT</pubDate><guid isPermaLink="false">2387e2159b323d714d5566a415377a59</guid></item><item><title>Support for the T.38 Protocol</title><description>ThinkTel supports T.38 in the following scenarios:  
  
2-way Direct media VoIP calls.  
2-way TDM-to-VoIP (and vice versa) calls.  
2-way TDM-to-TDM calls between two different Universal Media Gateways (UMG).  
  
T.38 is not supported in the following cases:  
  
Non-direct media VoIP calls, regardless of whether T.38 is supported by the endpoints.  
Multi-way calls (including tapped calls, for instance).  
Faxes using V.34  
Calls where an Originating or Terminating Application Server has been invoked.  
BLES-to-VoIP (and vice versa) calls.  
Calls where no leg is over IP (!)  
  
Behavoir that initates T.38:  
  
1. If a fax-specific tone is detected, the call will be reprogrammed to G.711 (if it is not already using it).  
2. If a reINVITE was received from a SIP device, it will be rejected.  This should not cause the call to fail - instead the SIP device should send a reINVITE requesting the use of G.711 instead  
  
  
Note that some tones are used in both fax and modem calls. If such a tone is detected on a call using a low-bandwidth codec, the CFS will reprogram the call to G.711. If a fax-specific tone is subsequently detected, the call will only then be reprogrammed to use T.38. This "double fallback" is actually the normal case, since fax calls tend to start with the CNG or CED tones, and these are also used in modem calls.  
  
</description><link>http://support.jumpshop.com/index.php/kb/article/55</link><pubDate>Thu, 06 May 2010 20:09:55 GMT</pubDate><guid isPermaLink="false">0273b7fc6c9deb4b28ef50148b6399a3</guid></item><item><title>Supported routers/firewalls for Thinktel voice traffic</title><description>&lt;h3&gt;Problem: &lt;/h3&gt;
Do I need a special router/firewall for voice traffic?
&lt;br&gt;
&lt;br&gt;
&lt;hr&gt;
&lt;br&gt;
&lt;h3&gt;Solution: &lt;/h3&gt;&lt;p&gt;
Not all NAT firewall/routers can handle voice traffic properly. Symptoms of this include inability to receive calls inbound, dropped calls and no one being able to hear you when placing an outbound call. Most firewall/router devices have firmware upgrades available to deal with SIP properly, so its always good measure to upgrade to the latest stable firmware. Many older devices have no updated firmware and may need to be replaced.&lt;br&gt;

&lt;br&gt;&lt;strong&gt;
  * Routerboard Series &lt;/strong&gt;All Routerboard models have excellent support for VoIP services. Great support for tunning QoS rules. ThinkTel uses the Routerboard 750 and other models on all our retail installations.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;* 

&lt;br&gt;&lt;strong&gt;
  * Linksys WRT54G &lt;/strong&gt;Hardware version 5 requires new firmware immediately after being removed from its box.Version 4 and older are fine.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;* Linksys WRT54C&lt;/strong&gt; All versions appear to work fine.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;* Linksys WRT54GS&lt;/strong&gt; (non SRX model) All versions appear to work fine.&lt;/p&gt;&lt;p&gt;
*&lt;strong&gt; AOpen Broadband Routers&lt;/strong&gt; Work out of the box and are cheap at about $30.00&lt;br&gt;
&lt;br&gt;
  * &lt;strong&gt;Linksys SRX gear (all models thus far)&lt;/strong&gt; cause us registration problems with Sipura/PAP2 devices. NAT keep alive fails which results in loss of inbound calling.&lt;/p&gt;&lt;p&gt;
&lt;br&gt;&lt;strong&gt;
  * D-Link DI-604&lt;/strong&gt; and friends have some problems with early NAT timeouts, causing temporary failures (this has been hit or miss)&lt;br&gt;
&lt;br&gt;&lt;strong&gt;
  * Cisco PIX 501 - 525&lt;/strong&gt; Version 6.3 firmware and greater works with or without SIP handling enabled.&lt;br&gt;
&lt;br&gt;&lt;strong&gt;
  * Cisco IOS&lt;/strong&gt; with SIP CBAC disabled&lt;br&gt;
&lt;br&gt;&lt;strong&gt;
  * OpenBSD software firewalls&lt;/strong&gt; (FreeBSD works fine, OpenBSD loses NAT sessions)&lt;br&gt;
&lt;br&gt;&lt;strong&gt;
  * Windows 2000/2003/XP Firewall/NAT&lt;/strong&gt;- Not a good thing, introduces extreme jitter into the stream, but works&lt;br&gt;
&lt;br&gt;&lt;strong&gt;
  * Linux IPTables&lt;/strong&gt; Works fine, sometimes needs higher UDP timeout setting, but not normally&lt;br&gt;
&lt;strong&gt;&lt;br&gt;
  * SPA-2100/SPA-2102&lt;/strong&gt; as a router by itself works fine (with other VoIP behind it) &lt;br&gt;
&lt;/p&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/29</link><pubDate>Thu, 06 May 2010 19:10:50 GMT</pubDate><guid isPermaLink="false">f6b7c1badf8abca641e05675b1d21ffe</guid></item><item><title>What should my Quality of Service settings be ?</title><description>Your site router (or layer 3 switch) should be set to have the DSCP or ToS setup with:  
  
SIP TOS/DiffServ Value: 0x68	  
RTP TOS/DiffServ Value: 0xb8  
  
SIP is for call signaling and RTP is for the media paths on the live call.</description><link>http://support.jumpshop.com/index.php/kb/article/88</link><pubDate>Wed, 24 Mar 2010 19:30:00 GMT</pubDate><guid isPermaLink="false">29f3920bac27aeef8d083a5d1aabfd5b</guid></item><item><title>Inbound Caller ID is wrong on my Toll Free numbers</title><description>Toll-Free Numbers often need the inbound caller ID to terminate the call properly. Often cell carriers will pass the pilot number of their clients local rate centre instead of their actual number. This is the wrong inbound caller ID you are seeing on toll free number.   
  
Unfortunately, there is nothing we can do about this.</description><link>http://support.jumpshop.com/index.php/kb/article/66</link><pubDate>Tue, 19 Jan 2010 16:26:08 GMT</pubDate><guid isPermaLink="false">f3dee874f5f370e62d9717cf0363a9d8</guid></item><item><title>Can I test my internet link for VoIP?</title><description>&lt;p&gt; &lt;/p&gt;&lt;p&gt;To test your internet access for voice media, follow this link:&lt;/p&gt;&lt;p&gt;&lt;a href="http://voiptest.thinktel.ca" mce_href="http://voiptest.thinktel.ca"&gt;Thinktel VoIP test &lt;/a&gt; &lt;/p&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/50</link><pubDate>Tue, 15 Dec 2009 21:40:11 GMT</pubDate><guid isPermaLink="false">b8ff99bf225b8bba509a725af449ba72</guid></item><item><title>I receive no caller ID name on my Rogers Wireless handset</title><description>This is a direct issue with the Rogers network and their policy on how they handle caller ID from remote networks. As explained by one of our upstream providers:  
  
Calls from analogue lines on the MTSallstream network  
displays name and number on Rogers cell phone. Calls that are  
originating from other sources (such as pri/sip etc) which have a  
different method of generating name display are discarded by Rogers  
gateway switch. I worked with Rogers and confirmed by Rogers trace that  
name was being passed along. I also spoke with Bell IXC and they stated  
that this was a known problem with Rogers. They spent several weeks  
troubleshooting this with them.  
  
Unfortunately, there is nothing more I can do with this issue.  
</description><link>http://support.jumpshop.com/index.php/kb/article/69</link><pubDate>Thu, 04 Jun 2009 19:04:50 GMT</pubDate><guid isPermaLink="false">6a1810f928cfe4e0154d77d061ed8d86</guid></item><item><title>Successful SIP PBX Interops</title><description>- Communigate Pro  
- Vonexus   
- Broadsoft  
- Nortel SIP Gateways  
- CCM (Cisco Call Manager)   
- Asterisk 1.2.x - 1.4.x  
- CallWeaver  
- Sutus  
- Broadsoft  
- Dialogix  
- Avaya  
- Toshiba Strata  
- Fonality  
- Acme Packet  
- Siemens  
- Natural Convergence  
- Pingtel  
- Epygi  
- Linksys  
- AdTran  
- VegaStream  
- Audio Codes  
- Next Tone  
- Freeswitch  
- Cisco UC520 (Call Manager Express &amp; Call Unity Express)  
- Microsoft Response Point</description><link>http://support.jumpshop.com/index.php/kb/article/37</link><pubDate>Thu, 28 May 2009 22:37:19 GMT</pubDate><guid isPermaLink="false">2141ce9e2f5ab40e75bdfd865d722a6f</guid></item><item><title>What is a pilot number used for on my SIP Trunk?</title><description>Every SIP trunk has a number in one of our rate centres that is used to identify you in CDRs from our swich, including defining the local calling area of your SIP trunk. This is a pilot number. It is used in the same way that a telco would deliver a PRI to your location; however the difference with our SIP trunk is that you can add DIDs to it from any of our rate centres, where a local PRI is just DIDs in that local rate centre that is defined by its pilot number.</description><link>http://support.jumpshop.com/index.php/kb/article/68</link><pubDate>Wed, 20 May 2009 00:26:06 GMT</pubDate><guid isPermaLink="false">65464c3e927b2332e7ea9912c5acde34</guid></item><item><title>Freeswitch sample config</title><description>By spec, our SIP trunk only authenticates by IP address. For the case of Freeswitch, we can enable authentication in order for an error free configuration.  
  
The following the minimal needed to establish a functional SIP Trunk with JumpShop:  
  
  
Realm: vp.jumpshop.com or eico.jumpshop.com  
Username: given to you.  
Password: set in the same place  
  
Also enter the proxy to be either vp.jumpshop.com or eico.jumpshop.com.  
  
  
</description><link>http://support.jumpshop.com/index.php/kb/article/67</link><pubDate>Tue, 31 Mar 2009 15:28:38 GMT</pubDate><guid isPermaLink="false">4c63283d9b6e370b9ff23ae30e44e306</guid></item><item><title>I have an IP phone/ATA that I would like to peer to Thinktel. How do I do that?</title><description>&lt;p&gt; &lt;/p&gt;&lt;p&gt;These are the essential configuration values for your phone/ata will be:&lt;/p&gt;&lt;p&gt;1. The SIP username. This will be the 10 digit number we provide.&lt;/p&gt;&lt;p&gt;2. The SIP password. This password we will provide for you to register to our switch.&lt;/p&gt;&lt;p&gt;3. The SIP proxy. Set your phone/ata's SIP proxy to be: vp.thinktel.ca (Setting the Outbound SIP Proxy is typically not needed)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;These values should allow proper SIP registration and call flow assuming your local network handles with SIP properly. &lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt; &lt;/p&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/52</link><pubDate>Wed, 03 Sep 2008 20:21:38 GMT</pubDate><guid isPermaLink="false">f06932d5c44b6e5b89a39e2b8f8d62bc</guid></item><item><title>Is my Linksys/Sipura SPA3102 supported by your company?</title><description>We do not support the Linksys/Sipura SPA3102 because of problems with the firmware related to T.38 and provisioning.  Please see the following URL for a list of supported devices.&lt;br /&gt;  
&lt;br /&gt;  
http://wiki.thinktel.ca/Provisioning_with_Thinktel</description><link>http://support.jumpshop.com/index.php/kb/article/65</link><pubDate>Fri, 15 Aug 2008 19:36:06 GMT</pubDate><guid isPermaLink="false">d7f51ab5494f403c8988257c7db6f68a</guid></item><item><title>Grandstream GXE issues</title><description>The GXE has a 'SIP Keepalive' setting that needs to be disabled or set to 'none' within the web adminstration of this PBX. It uses a keep alive method our switch does not understand.</description><link>http://support.jumpshop.com/index.php/kb/article/64</link><pubDate>Fri, 15 Aug 2008 19:17:43 GMT</pubDate><guid isPermaLink="false">137c4756646c530ec447ceef99ef046c</guid></item><item><title>SNOM phones cannot receive or make calls on my PPPOE internet connection</title><description>SNOM IP phones are known for sending very large packets (1500 bytes) that may be dropped by routers that are connected to PPPOE internet connections. PPPOE internet connections have a maximum packet payload of 1492 bytes, which may not be fragmented by the site router and simply dropped. &lt;br /&gt;  
&lt;br /&gt;  
A solution to this is to use a router that will fragment the packet or attempt to forward it as is. Otherwise, non PPPOE internet access must be used if SNOM phones are to be used onsite.</description><link>http://support.jumpshop.com/index.php/kb/article/63</link><pubDate>Wed, 30 Jul 2008 18:03:56 GMT</pubDate><guid isPermaLink="false">244629a4e09491c69c1b6ca9ee7a9ea3</guid></item><item><title>Xten Lite &amp; Eyebeam Softphone configuration</title><description>Recent version of Xten lite require some non-obvious settings to work properly when using Thinktel VoIP service. After launching Xten Lite, follow these steps exactly:&lt;br&gt;&lt;br&gt;1.) Dial ***7469 and click Send.&lt;br&gt;2.) In the window that pops up, type 'rinstance' in filter. A number of values should pop up for this. For the entry labelled 'Proxy 0', change its value to 0 instead of 1.&lt;br&gt;3.) Close the window and save changes.&lt;br&gt;4.) Restart Xten lite.&lt;br&gt;5.) Configure the Xten for your Subscriber line. Set domain to vp.thinktel.ca, username to the 10 digit number and the appropriate password.&lt;br&gt;6.) Save changes and restart xten lite. Your number should be registered to the switch with active phone service.</description><link>http://support.jumpshop.com/index.php/kb/article/59</link><pubDate>Wed, 18 Jun 2008 19:58:08 GMT</pubDate><guid isPermaLink="false">6abe277cddda376f5b806bf56fbc9237</guid></item><item><title>Low volume on voicemail</title><description>If you have a SIP trunk and are using Asterisk for voicemail. we have found Asterisk records the volume quite low in its voicemail files.One approach is to use a post-voicemail command in the voicemail configuration, which can run Sox on the saved files and amplify them automatically.&lt;br /&gt;  
&lt;br /&gt;  
A recommended level for amplification of these is -7dB from maximum.</description><link>http://support.jumpshop.com/index.php/kb/article/62</link><pubDate>Wed, 14 May 2008 05:06:14 GMT</pubDate><guid isPermaLink="false">38ba1bf0ba7349c1f14c68ac3b4ad6cf</guid></item><item><title>How do I force uncompressed or compressed audio on my linksys ata adapter?</title><description>&lt;p&gt; &lt;/p&gt;&lt;p&gt;To force uncompressed audio (G711), tap *027110 &lt;/p&gt;&lt;p&gt;To force compressed audio (G729), tap *02729 &lt;/p&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/35</link><pubDate>Wed, 23 Apr 2008 02:58:01 GMT</pubDate><guid isPermaLink="false">3e0d7205e4e5804cc9784de7e252b22e</guid></item><item><title>Can not receive calls</title><description>&lt;h3&gt;Problem: &lt;/h3&gt;&#xD;
Customer is unable to receive inbound calls.  &#xD;
&lt;br&gt;&#xD;
&lt;br&gt;&#xD;
&lt;hr&gt;&#xD;
&lt;br&gt;&#xD;
&lt;h3&gt;Solution: &lt;/h3&gt;&#xD;
This is related to the IP Handset (IP Centrex), or the Gateway Device (IBL, PRI) ability to register to Thinktels network.  There are a few possibilities:&lt;br /&gt;&#xD;
1.	Power Outages&lt;br /&gt;&#xD;
2.	Loss of Internet Connectivity &lt;br /&gt;&#xD;
3.	Router / Firewall security options are blocking VOIP traffic.&lt;br /&gt;&#xD;
Note:  Calls should still route to Auto Attendent and/or VM.  Customer can also choose emergency routing options, i.e. route to cellular phones.&lt;br /&gt;&#xD;
</description><link>http://support.jumpshop.com/index.php/kb/article/16</link><pubDate>Wed, 23 Apr 2008 02:54:31 GMT</pubDate><guid isPermaLink="false">a8272862427427d7bdca2ccb2e8c5feb</guid></item><item><title>Call are Dropping but only sometimes</title><description>&lt;p&gt; &lt;/p&gt;&lt;p&gt;This may indicate that the phone is not reregistering on its set interval with the Thinktel switch (3600s) . The switch will assume that the device is no longer present and will drop any calls that may be in progress. &lt;/p&gt;&lt;p&gt; - Verify the latest firmware is being ran on the phone/adapter. &lt;/p&gt;&lt;p&gt; - If you are running your phone behind a NAT firewall that is SIP aware, packet mangling may be occuring.&lt;/p&gt;&lt;p&gt;- If you have other IP handsets or ATAs, check if they are also configured with the same phone number. This could create registration conflicts and sudden call drops while the other devices registers on the same number.&lt;br&gt; &lt;/p&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/42</link><pubDate>Wed, 23 Apr 2008 02:44:11 GMT</pubDate><guid isPermaLink="false">bf88c790317748557a65ce585903a874</guid></item><item><title>Calls drop 30 seconds into call</title><description>This may occur if you are using an ATA or IP Phone peered directly to Thinktel's switch.&lt;br&gt;What happens is our switch sends a SIP 'keep alive' every 30 seconds to make sure the call is still active. It does this be sending a SIP re-invite for the live call, in which we expect a 200 OK respsonse, that we then ACK back. If no response is receive, the call is terminated by the switch.&lt;br&gt;&lt;br&gt;This could be caused by:&lt;br&gt;&lt;br&gt;- A SIP aware firewall that is mangling packets.&lt;br&gt;- NAT issues on your router and does not support SIP properly&lt;br&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/56</link><pubDate>Wed, 23 Apr 2008 02:43:36 GMT</pubDate><guid isPermaLink="false">eac24772ce25c91bf82ca3c4478c0fa9</guid></item><item><title>Asterisk &amp; DTMF</title><description>&lt;p&gt;Asterisk normally handles RFC2883 in a strange manner:&lt;br&gt;&lt;br&gt;From the phone:&lt;br&gt; Audio Audio Audio DigitStart Duration Duration DigitEnd Audio Audio&lt;br&gt;&lt;br&gt;It waits until it sees 'DigitEnd' before it does anything, then it sends (in a tight for loop):&lt;br&gt;&lt;br&gt;DigitStart Start Start End End End (takes about 1ms normally)&lt;br&gt;&lt;br&gt;So,&#xD;
this consumes the DTMF entirely (duration is lost), and it sends it in&#xD;
such a short period that devices that use the other definition of how&#xD;
long to make DTMF (you can either use Duration field, the Asterisk way,&#xD;
or the start playing with the start message, stop at the end way, which&#xD;
our switch does) end up generating the worlds shortest DTMF sequences.&lt;br&gt;&lt;br&gt;Thus,&#xD;
the side effect of this patch, by slowing the packet rate down to&#xD;
around 80ms for the entire period, is it won't accept further&#xD;
DTMF/audio for those 80ms (Asterisk, that is, it will delay everything&#xD;
by that amount). So, really fast DTMF dialers can miss a keystroke. &lt;/p&gt;&lt;p&gt;For SIP peers running Asterisk 1.0.x - 1.2.x, a patch can be provided &lt;a target="_blank" href="http://wiki.thinktel.ca/Image:Rtp.c"&gt;here&lt;/a&gt;&lt;br&gt; &lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/5</link><pubDate>Wed, 23 Apr 2008 02:43:19 GMT</pubDate><guid isPermaLink="false">e4956c1c1f0e2e7b6bae6fd08d87c831</guid></item><item><title>Calls are Dropping after a few seconds of being answered</title><description>&lt;p&gt; &lt;/p&gt;&lt;p&gt;This typically means there is no reply to the 200 OK from the Thinktel switch. The 200 OK indicates the call has been answered.&lt;/p&gt;&lt;p&gt; The phone could possibly be:&lt;/p&gt;&lt;p&gt; - Responding to the 200 OK but is routing to the wrong place.&lt;/p&gt;&lt;p&gt; - The phone is responing on the wrong port. ie: port 0&lt;/p&gt;&lt;p&gt; - The phone is responding back to the wrong IP address. &lt;/p&gt;&lt;p&gt; - A SIP aware firewall may be mangling packets or not forwarding SIP ACKs in NAT scenarios. We have seen this behavoir in Juniper firewalls. &lt;/p&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/41</link><pubDate>Wed, 23 Apr 2008 02:43:00 GMT</pubDate><guid isPermaLink="false">df2b592fb080f02e5c533d730dfbc257</guid></item><item><title>Astra IP Phone service is up and down.</title><description>&lt;p&gt;Astra phones do not support a proper NAT keep alive (as of writting this article) and can cause fadding in and out of inbound calling.&lt;/p&gt;&lt;p&gt; details of fix will be posted soon.&lt;br /&gt;&lt;/p&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/39</link><pubDate>Wed, 23 Apr 2008 02:42:36 GMT</pubDate><guid isPermaLink="false">ef67ee56b3f817f4098cace3d1ff57df</guid></item><item><title>How do I request a number(s) to be ported to Thinktel?</title><description>&lt;p&gt; &lt;/p&gt;&lt;p&gt;Thinktel can provide LNP (local number portability) to centres in our on-net footprint. To request a port, please complete the following form:&lt;/p&gt;&lt;p&gt;http://support.thinktel.ca/ports&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt; To view our current on-net and off-net foot print, refer to the following Wiki &lt;a title="on-net footprint" href="http://wiki.thinktel.ca/Thinktel_Footprint"&gt;article&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;&lt;br&gt; &lt;/p&gt;</description><link>http://support.jumpshop.com/index.php/kb/article/45</link><pubDate>Wed, 23 Apr 2008 02:41:29 GMT</pubDate><guid isPermaLink="false">ae64c8b31bd5d0ea9d5c7b0305ea3505</guid></item><item><title>What are the supported codecs?</title><description>&lt;p&gt; &lt;/p&gt;&lt;p&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;&lt;strong&gt;- G.711 - Pulse code modulation (PCM) of voice frequencies on an 64 kbps channel. mu-Law companding (PCMU) and a-Law companding (PCMA)&lt;br&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;&lt;strong&gt;- G.726-32 / G.721 - 32 kbit/s adaptive differential pulse code modulation (ADPCM)&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style="font-family: arial,helvetica,sans-serif;"&gt;&lt;strong&gt;- G.729 - Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear-prediction (CS-ACELP), including annex A and B.&lt;br&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;br&gt;* Do not use G.726 with Asterisk/Trixbox/CallWeaver</description><link>http://support.jumpshop.com/index.php/kb/article/43</link><pubDate>Wed, 23 Apr 2008 02:40:59 GMT</pubDate><guid isPermaLink="false">42f2241ff4cb18c184d23c9903f36bf5</guid></item></channel></rss>
