Ticket #1501 (closed Bugs: fixed)

Opened 5 years ago

Last modified 5 years ago

Never Override CallerID Works...Backwards

Reported by: SexyKen Assigned to:
Priority: major Milestone: 2.2
Component: Core - Trunks/Routing Version: 2.2rc1
Keywords: FollowMe, CallerID, Override callerID Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

Okay -- I had one heck of a time getting Caller ID to work for my FollowMe setup. I had everything setup properly...and things weren't working.

So I decided to setup things the wrong way. I enabled "Never Override CallerID" -- it was Enabled, I applied the changes, low and behold, FollowMe Original caller ID's started to pass :-)

Just letting you guys know!

Change History

12/05/06 11:58:18 changed by p_lindheimer

  • priority changed from minor to major.
  • status changed from new to closed.
  • resolution set to fixed.

FIX WILL BREAK 'WORKING' CONFIGS since logic is backwards. r3270 and r 3271.

The logic was backwards. I chose to fix the logic as intended instead of reverse what the checkbox does. I chose this because the normal use case is to NOT enable this field since that is the behavior most people want and most VoIP providers don't break if you send them a foreign CID, they just ignore it if they don't support spoofing.

This means that if you have checked the box to override the bug, an update will undo what you worked around and the trunk settings will have to be changed. (so we need to make sure to get this in the release notes/change log).

01/08/07 13:46:44 changed by

  • milestone deleted.

Milestone 2.2 deleted

01/08/07 14:35:27 changed by vgster

  • milestone set to 2.2.