Is 3.7 compatible with 3.6 with regards to networking?

[BCMprogrammer]

Does any currently have a 3.7 BCM networked with 3.6's?

The reason I ask is because I'm having troubles with a new 3.7 that I installed yesterday. The problem is no other site can dial directly to the 3.7 site's phones across the network. The calls go to the prime set of this site. No troubles calling from new site to other sites, however.

I have confirmed target line settings several times, private rcv'd digits, being the main focus. Yes, I've rebooted a few times, the bcm and the baystacks.

All BCM's can ping each other.

The other 4 BCM's are all 3.6 and can call each via IP trunking directly with 4 digit dialing.


This new site has all I2002's connected to 2 stacked Baystack 460 PoE switches, with no VLAN's, and no IP address programmed to it- pretty much straight out of the box with no software upgrades (same as 2 of the other sites that have baystacks and IP phones).

The 3.7 also has the newest patch which was only the Win NT security update.


Basically, this system matches the settings of the other sites and can call directly to the other sites via dest codes routing across VOIP lines and IP trunking with the appropriate remote gateway settings, BUT cannot receive direct calls from the other sites.

So, if someone has a 3.7 working fine in this type of environment, then I will continue to quadruple check every single setting, otherwise it seems to be an issue to elevate to ITAS.

 

[BCMprogrammer]

I just found out the new site is NOT a 3.7. I'm embarrassed I made that mistake. Anyhow, still troubleshooting the problem. One possibility is the system didn't have the Cumulative 2.0 patch loaded. It had all the later patches (15) but not the cumulative. I'll post again after this gets loaded.

 

[3Sixty]

Is it an earlier version?

Might need the interop patch

Marshall

http://www.marshallshouse.co.uk

 

[BCMprogrammer]

BCM 400 3.6 build 3.1A

 

[biv343]

Build 3.1A includes cumulative patch 2. Found that out when I tried to apply CP2 and it wouldn't go. Called ITAS and they informed me that build 2.2C has no patches, but 3.1A has CP-2 applied at the factory.

Unfortunately, that doesn't explain why your BCM's can't call this new system.

 

[3Sixty]

Have you watched a call come in to the system on the BCM monitor to see what digits are being presented etc.

Marshall

http://www.marshallshouse.co.uk

 

[BCMprogrammer]

Update- this problem has been fixed. The cause was in the target lines received digits.

The private digits did not match the public digits, and in this design the intention was to have a PRI with one range of digits that were different than the private network digits.

Apparently a private network cannot be set this way without having the MCDN license.

The work around was to have the 'private network' digits assigned to different target lines and then assigne 2 target lines to each phone- one for the PRI DID, one for direct dial digits.