Open Source Training Seminar FreePBX Paid Support

Ticket #1907 (closed Bugs: fixed)

Opened 1 year ago

Last modified 1 year ago

180 Ringing sent before 486 Busy Here and 503 Service Unavailable

Reported by: aydiosmio Assigned to:
Priority: minor Milestone: 2.3
Component: Core Version: 2.3-branch
Keywords: Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

In doing Verizon Biz Wholesale VOIP interop testing, we were required not to send a 180 Ringing before sending a 486 or 503 when an endpoint was busy/unavailable. I'd like to scrounge up the original purpose for the existing behavior (100 -> 180 -> 486/503) and establish what the proper behavior or setting option should be.

Change History

04/20/07 06:14:26 changed by p_lindheimer

If I understand the issue correctly, this was coming in on anonymous sip calls - I would tent to agree that no matter what - if an anonymous call is going to be rejected it should not send ringing first. If anonymous is enabled, why would we want to send ringing prior to routing the call?

Rob - I think you added the ringing originally, does it really need to be there for some other reason - doesnt' seem correct?

06/25/07 07:53:55 changed by p_lindheimer

  • version changed from 2.2.1 to 2.3-branch.

TODO: remove the ringing in the anonymous sip context, let the normal dialplan send ringing when appropriate.

07/26/07 07:43:58 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to fixed.

r4537 will be out next time core module is published.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads