Search results for query: *

We saw it comming... The existing sip version has issues talking to the voip provivider. The dtmf implementation is custom by nortel and who knows what else will come up. So long BCM400, and thanks for all the fish... Thanks everybody

That is too much for our budget... We might be able to use an old bcm50a since there is no hardware change, although I think that it has a limitation on the max active sets. Any estimates for cost upgrading the release for the bcm50a? I suppose that upgrading the keycodes is free, and you pay...

Well, there is no redundancy and about 30-40 sets, so it is not a big setup. But replacing hardware is not that much of a problem as buying it:-) Should I assume that the same applies to a BCM50a with software release 2.0.2.05e? You need to replace the hardware to get the latest software version?

Thank you telcodog We ve been using a direct microwave connection to our sip provider, so no authentication is requested. Well, the upgrade may be easy but if you have to upgrade almost all your hardware, then the cost is most likely going to be a big problem.

Hello all, We have a BCM400 version 4.0.2.03. The latest patch installed was System.029-201012. So far and for the past few years we have been using SIP trunking for our external calls to a voip provider that is using ip authentication, since our software version does not allow SIP username...

I thought that this would also move all settings like call forwarding of the old DN. The old DN will stay as it is? Thanks

Hello all, I have a BCM400, and I have setup a DN with some call forwarding, voice mail that works even when the phone is not connected to the BCM (keep DN alive option is checked). I want to use that phone for a different DN but without deregistering the original DN so that call forwarding...

All modules are R-series,, and the software version is 4.1. I am trying to figure out ACLs, ACTs, ACEs but I am still very confused.

Hello all, I have two 8600s in terrabit configuration with IST interconnection and several internal VLANs. All VLANS have IPs and VRRP is enabled and by default all those internal VLANs can route to each other. How is it possible to limit that, so that only some specific VLANs can only talk to...