Customer has a Panasonic PBX and used to get phone service from SBC; now they get it from XO, which uses a MUX to do voice over IP. Since they made this change, *67 (caller ID blocking) doesn't work. However, when a tech plugs a butt set into the MUX and dials *67, it works fine. Any ideas?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
*67 (caller ID blocking) failing with new MUX
- Thread starter johnathcc
- Start date
- Thread starter
- #4
Actually, the KSU is passing on the DTMF tones as it should. Normal calls complete normally; *67 calls ring at the other end, but then when the party answers or the call gets transferred to voice mail, the KSU reports a busy signal.
Apparently the MUX is passing back something -- a particular voltage? -- to the KSU that the KSU thinks means "line busy". It's really odd that it happens only on *67 calls, and that *67 calls work just like regular calls until the other ends picks up.
I'm going to work from both ends -- ask the telco provider (XO) to check into the MUX's behavior, and look up specs on the Panasonic VB43060.
Apparently the MUX is passing back something -- a particular voltage? -- to the KSU that the KSU thinks means "line busy". It's really odd that it happens only on *67 calls, and that *67 calls work just like regular calls until the other ends picks up.
I'm going to work from both ends -- ask the telco provider (XO) to check into the MUX's behavior, and look up specs on the Panasonic VB43060.
- Status