01 August 2012

The minor change below has been reflected in the setup post. Randomly during a few different calls, participants would hear the phone ring before the call was transferred to voicemail. Of course, with the call in the vm system, the staff member is disconnected in the process (although the vm transfer is a big problem on its own).

This happened several times before the logs highlighted a possible cause, in part because debug levels had been reduced to avoid unnecessary network traffic. The key SIP operation was that the SPA8800 Line 1 was re-registering with the IVR. That apparently interrupted the call that was being routed such that it reinvited (SIP command INVITE) the IVR to the call. Since we've configured our phones to only accept 1 call (to avoid call waiting beeps), the IVR kicks the refreshed call into vm. The call would not drop after every REGISTER, but it only dropped after a REGISTER.

I was thoroughly convinced that the problem would have to be solved by the SPA8800 since it was registering and it was issuing the new INVITE. Dozens of different configurations failed to have any impact on the problem, and nothing in Axon lined up with the problem. I was reviewing yet another marginally relevant configuration document when an assumption came to light.

  1. Axon's recommended configurations for FXO adapters included a 60-second registration expiration.
  2. Axon has a setting:
    Advanced Line Settings > SIP Compatibility Options > Disable call activity polling (only use if call breaks after 60 seconds)
  3. It dawned on me that the 60 seconds referenced in the compatibility option might have been contingent upon using their recommended registration expiration.

Once I considered that the Axon interface's parenthetical might just be inaccurate (at least given our 3600 second expiration), it only took me a few seconds to check that box and resolve the problem.

blog comments powered by Disqus