Incoming Calls Have to be Parked or Held before Caller Can Hear the User

[Nortel4Ever]

IPO 11.1.3.0.0 Build 23 with PRI, 2 DS30, 1 DS16, 21 IP phones all in the same physical location at the rest of the system.
IP Phone (J159) users will receive a call but the caller cannot hear the IP Phone user until the call is either Held or Parked first. After that the call can proceed as normal.
WAN on the IPO is the DHCP server for the phones and it is connected to a switch port tagged with a VLAN ID. The phones are programmed with that VLAN ID so logically there is nothing between the phones and the IPO. Incoming call are first answered by an Auto Attd on the VM Pro, and the VM Pro is connected through the customer's production network which the IPO's LAN port is also connected to,
I have tried disabling "Allow Direct Media Path" on a few of these problem phones to see if that would correct the issue, but it had no effect.

 

[Menniss]

Is this all phones all the time? Just curios what a call from the PRI direct not via VM Pro? What about IP to IP phone?
I don't know if this could be cause but I never put IP phones in the LAN 2 interface.

Looks like you are going to need to grab some traces.

I assume the switch the phones are on is part of the production network as it has a VLAN but then why use the LAN 2 interface? You don't have both the LAN 1 and LAN 2 on the same subnet do you?

If it was me I would try a phone direct on the LAN 2 interface and see what that does. Actually, I would move them to the LAN 1.

 

[Nortel4Ever]

We have put IP phones on LAN 2 using the IPO as DHCP server many times and very large sites with no issues until now. LAN 1 is on the customer's subnet, LAN 2 is the default 192.168.43.x with 200 DHCP addresses.
I have asked the customer's IT guy to try putting a phone on the production network and re-registering it to the IPO to see if that makes a difference.

 

[sizbut]

First point of call is surely to upgrade to the latest 11.1.3 service pack (11.1.3.2) - if only to avoid the scary number of "system restart" bugs listed in the release notes.

 

[Travis Harper]

We have put IP phones on LAN 2 using the IPO as DHCP server many times and very large sites with no issues until now. LAN 1 is on the customer's subnet, LAN 2 is the default 192.168.43.x with 200 DHCP addresses.
I have asked the customer's IT guy to try putting a phone on the production network and re-registering it to the IPO to see if that makes a difference.

Could be an incorrect NAT type setting. Sounds like signalling is working but RTP is failing. Phone can see the IPO and register, but talk path can't find the device on the far end and is sending the Audio to the wrong LAN interface.