tbrummell
Guru
- Joined
- Jan 8, 2011
- Messages
- 1,275
- Reaction score
- 339
I have a deployed 16-15-1 server that was then restored from a 13.x backup with a weird Outbound CID issue.
When a call is placed from extension x, the Outbound CID is displayed as programmed in FPBX on the extension. FPBX CDR shows the Extension name, and Outbound CID as expected. Voip.ms CDR shows the Outbound CID in their record, as expected.
Here is where it gets strange.
When a call is placed from extension y, the Outbound CID is displayed as the Extension name & number, not the Outbound CID that is programmed. FPBX CDR shows Extension name/number & Outbound CID as being the same, and Voip.ms CDR shows the Extension name/number as well.
Before you ask, the Extension name/number is the phone location/internal extension, vs the Outbound CID being phone primary Users name/primary user PSTN number. Both phones are set to use PAI, and otherwise identical except for brand. x is a Snom 370, y is an Aastra 6757. But that shouldn't matter, should it? Maybe I can snag a 6757 here at work and add it in to the system as a test.
The only thing I can think of is this is another remnant of the restore process from IPBX 13. I never did rectify my problem of no Direct Page (*80) Feature Code being available anymore after restore.
Has anyone else noticed this in their CDR? I got wind of it as my wife called her parents from the master bedroom and that is exactly what showed up on their display, not to mention the internal extension number of the phone.
The only other thing between my test, and her call, her parents PSTN has an Inbound route programmed for it, to go direct to a ring group, where as my test number (work DID) does not. Again, shouldn't matter but tossing it in there as a FYI. Will do some more digging.
When a call is placed from extension x, the Outbound CID is displayed as programmed in FPBX on the extension. FPBX CDR shows the Extension name, and Outbound CID as expected. Voip.ms CDR shows the Outbound CID in their record, as expected.
Here is where it gets strange.
When a call is placed from extension y, the Outbound CID is displayed as the Extension name & number, not the Outbound CID that is programmed. FPBX CDR shows Extension name/number & Outbound CID as being the same, and Voip.ms CDR shows the Extension name/number as well.
Before you ask, the Extension name/number is the phone location/internal extension, vs the Outbound CID being phone primary Users name/primary user PSTN number. Both phones are set to use PAI, and otherwise identical except for brand. x is a Snom 370, y is an Aastra 6757. But that shouldn't matter, should it? Maybe I can snag a 6757 here at work and add it in to the system as a test.
The only thing I can think of is this is another remnant of the restore process from IPBX 13. I never did rectify my problem of no Direct Page (*80) Feature Code being available anymore after restore.
Has anyone else noticed this in their CDR? I got wind of it as my wife called her parents from the master bedroom and that is exactly what showed up on their display, not to mention the internal extension number of the phone.
The only other thing between my test, and her call, her parents PSTN has an Inbound route programmed for it, to go direct to a ring group, where as my test number (work DID) does not. Again, shouldn't matter but tossing it in there as a FYI. Will do some more digging.