It looks like Adtran is OK with failing G.168 echo cancellation tests on their higher end NetVanta VoIP gateways.
This is from their latest release notes:

Using the HEAD acoustics test suite, some G.168 echo cancellation test cases fail on the NetVanta 6240
and NetVanta 644. These same tests pass on Total Access 900 Series units. There is no reason to believe
this would affect a customer in the field.

Advertisements

Patton is a US based company but by default their units are not configured for US standards.

Here is how to add US tones and configure the FXS ports to simulate standard US POTS lines:

First for the tone profile:

profile call-progress-tone US_Dialtone
  play 1 1000 350 -13 440 -13

profile call-progress-tone US_Alertingtone
  play 1 1000 440 -19 480 -19
  pause 2 3000

profile call-progress-tone US_Busytone
  play 1 500 480 -24 620 -24
  pause 2 500

profile call-progress-tone US_Releasetone
  play 1 250 480 -24 620 -24
  pause 2 250

profile tone-set US
  map call-progress-tone dial-tone US_Dialtone
  map call-progress-tone ringback-tone US_Alertingtone
  map call-progress-tone busy-tone US_Busytone
  map call-progress-tone release-tone US_Releasetone
  map call-progress-tone congestion-tone US_Busytone

Next we need to configure the ports and interfaces.

port fxs 0 0
  end-of-call-signaling loop-break 1200
  use profile fxs us
  encapsulation cc-fxs
  bind interface FXS0 switch

interface fxs FXS0
  caller-id-presentation mid-ring
  caller-id-format bell
  use profile tone-set US

This must be repeated for each FXS port.

The above settings will set the FXS ports to use the US tones, caller id, other settings needed to simulate standard “Bell” lines.

You will also need to apply the US tones to the SIP interface:

interface sip SIP1
   use profile tone-set US

This is a follow up to my original reiew of the  FF240 http://wp.me/pI64k-A

Multi-Tech released a new firmware (1.1.15) which greatly enhances its functionality (makes it work).
I tested it for a number of days and found that in most instances it had no problem receiving or sending faxes.
The only issue I ran into was when it was sending  or receiving to an IP based fax machine, but at that point it’s  hard to find where the fault is.

The biggest short coming is that the unit does not have caller-id support (yeah I know it’s 2012) which is kind of a pain when you are looking for a fax in your email client.
Multi-Tech says that this will be added in a future release.

After some research it looks like the FF240 is using technology made by Commetrex.
The technology seems to be new but works well. (I will be reviewing their SmartATA in the near future)

Overall the FF240-IP went from an almost useless device to a nice fax server.

There are many used 1st Gen Adtran Total Access 900 Series Gateways out there at much lower prices than the 2nd Gen.

I was curious if there are major differences between the two units.
After some research I found the following:

Feature 1st Gen 2nd Gen
3 Way Conferences via FXS users 0 3
Max TDM to IP Call 24 30
Max T.38 Sessions 1 4
Echo-tail Length 16 ms 64 ms
Supports MGCP No Yes
Flash Memory 32MB 64MB

Based upon Echo-tail length increased to 64ms and the increased number of T.38 faxes I stick to the the 2ng Gen Gateways.

Recently I had a customer that wanted to setup SIP Trunks on their old phone system.
When I arrived onsite I realized that they were using an old T1 and not a PRI.

At first I tried configuring the settings in the GUI but that just created a mess in the config and didn’t work.

After some digging around I got it to work with the following settings:

interface t1 0/2
  tdm-group 1 timeslots 1-24
  no shutdown

voice trunk T02 type t1-rbs supervision wink role network
  description “PBX”
  connect t1 0/2 tdm-group 1
  resource-selection linear ascending
  did digits-transferred 4
  modem-passthrough
  t38
  rtp delay-mode adaptive
  codec-group Generic

The remaining settings are the same as a standard PRI.

The KX-UT670 has both an EHS (electronic hook switch) and 2.5mm headset port on the side.
Being that the Plantronics CS70n is one of the supported headsets I hooked it up to the phone using the following setup:
Plantronics 3.5mm hook switch port to the Panasonic 3.5mm EHS port
Plantronics RJ9 to Panasonic 2.5mm headset port

When pressing the “hook” button on the Plantronics headset the phone would answer and disconnect after a second.

If the hook switch wire is disconnected the headset works and if the headset wire is disconnected the
hook switch works but it wont work together.

I sent an email to Panasonic and they sent me back the following fix:
The phone doesn’t support both the EHS and 2.5mm headset at the same time.
To use the EHS with the Plantronics headset you must disconnect the handset from the phone, plug a RJ9 cable from the phone to the Plantronics and then plug the handset into the Plantronics.

See the following Power Point Link for the exact setup.

As of this posting Panasonic only officially supports five of this IP Camera with the KX-UT670. Link

All the manual says is that the camera must be set to VGA or 720p.
What it doesn’t tell you is that it only supports H.264.

I tested with the Panasonic WV-NW502S (Retails for over$1,000) and it worked fine.

Hopefully they will add support for their less expensive IP Cameras.