BLF keys for remote bridge extensions

[Craig Haydock]

I have two sites, each with their own 3CX PBX, and they are connected via VPN tunnel and over that tunnel they are connected via Master/Slave bridge to one another. Site 1 is using extensions 1xxx and site two using extensions 2xxx. Presence is set to push/pull all extensions from both sides and there are no errors being reported, firewall checker passes, etc.. Calls can be made and transferred across the bridge without a problem. I've even used the call flow designer to direct calls appropriately between the sites. But, what I can't seem to get to work is setting up BLF keys to see extensions at the remote site. When I'm in the web management interface and configure a phone/extension... the BLF dropdown options are limited to only local extensions. None of the remote extensions are available for selection. I can set up custom speed dial to just blindly reach out to that extension... but not with a BLF key. Is this not possible??? What's the point of exchanging extension presence if not for use in BLF keys?

I feel like I must be missing something easy. Any help would be most appreciated.

 

[Alphabetic]

Not possible. Use the client for ext availability.

 

[Craig Haydock]

Not possible. Use the client for ext availability.

That's something I forgot to mention when I posted and has me puzzled. The fact that through the client app it's possible to see remote site presence. But for reasons unknown it's not possible to assign that extension to a BLF key and utilize that presence. It just seems silly to not allow for that capability IMHO. <shrugs> #FeatureRequest ???

 

[Evolute IT]

That's something I forgot to mention when I posted and has me puzzled. The fact that through the client app it's possible to see remote site presence. But for reasons unknown it's not possible to assign that extension to a BLF key and utilize that presence. It just seems silly to not allow for that capability IMHO. <shrugs> #FeatureRequest ???

One uses 3CX HTTPS API Presence. The other uses SIP SUBSCRIBE/NOTIFY concepts.

That's why in the apps it shows, but not on BLFs.

 

[Craig Haydock]

One uses 3CX HTTPS API Presence. The other uses SIP SUBSCRIBE/NOTIFY concepts.

That's why in the apps it shows, but not on BLFs.

Well... not what I wanted to hear... but it's what I needed to hear I guess. Thanks for the info. It makes me feel like the purpose of a bridge is somehow/somewhat broken... but, it is what it is. It just seemed like it should have been a viable capability. Oh well.

 

[Evolute IT]

Well... not what I wanted to hear... but it's what I needed to hear I guess. Thanks for the info. It makes me feel like the purpose of a bridge is somehow/somewhat broken... but, it is what it is. It just seemed like it should have been a viable capability. Oh well.

Understand that 3CX does not use Asterisk or FreeSwitch as stack. It has it's own SIP stack built from the ground up. Therefore, some features that we expect in Asterisk are not in here. BLF Presence is not even part of the stack, only "call status". Thus why the BLF don't turn red for DND and such.

 

[Craig Haydock]

And of course... had I looked at all the slides in the Advanced Cert material on bridging (rather than just watching the video)... it's right there plain as day on slide #12!