BLF no lonking working V10 with bridged pbx

Discussion in '3CX Phone System - General' started by acolville, Jan 9, 2012.

Thread Status:
Not open for further replies.
  1. acolville

    Joined:
    Jul 27, 2009
    Messages:
    80
    Likes Received:
    0
    I have 3 3cx pbx's linked via bridges.

    Up until V10 it was possible for phones on each pbx to have function keys programmed for BLF for extensions on the other pbx's eg:

    Phone Id = 100@192.168.0.1
    BLF : 200@192.168.1.1

    Now an error occurs in the log as follows:
    20:58:11.447 [CM102001]: Authentication failed for SipReq: SUBSCRIBE 200@192.168.1.1:5060 tid=-jtrso8xq65qn cseq=SUBSCRIBE contact=100@192.168.0.1:2052 / 6 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

    I assume that this is due to the improved anti hacking system in V10, but is there a way around this?
     
  2. kevin

    kevin Member

    Joined:
    Nov 23, 2006
    Messages:
    316
    Likes Received:
    1
    The bridge connection delivers presence functionality to MyPhone clients, but does not do BLF relay.

    You *may* be able to work around this limitation by pointing the BLF lamp to the second PBX directly, but you would need to have an extension on the second PBX also, and some way to insert this second set of credentials into the phone to be able to authenticate correctly also to the second PBX, giving you (potentially) access to BLF information on the second PBX. If the phone does not provide such a mechanism, you can attempt to reduce the challenge by making sure that the phone in question uses the same common Extension Number, Authentication ID, and Authentication Password on both PBX machines.

    Note that this implies that the extension must have direct routing to both PBXs to give you a chance.
    Note also that this suggestion is hypothetical at best, and your mileage may vary.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.