Tony, Thanks for the insight. We're fighting many other fires right now so. unfortunately this may go on the back-burner until we have more time to figure it out.
-- Jay _____ From: Tony Graziano [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2008 8:42 AM To: [EMAIL PROTECTED]; [email protected]; Jay Reeder Subject: Re: [sipx-users] New Polycom Firmware - MOH locks up Mediant 2000 I have tested the 3.1 firmware (briefly) with Patton gateways and MOH worked. It broke moh which works through my ingate with bandwidth.com. When looking at my logs on my ingate I saw a "not supported" message coming back from bandwidth.com. At the same time, the caller got silence but taking them off hold worked and audio did not break. I decided to wait for the official 3.10.4 release to try 3.1 again to follow that through. If your Mediant is acting that wild, I would suggest two things: 1. Mediant in debug mode sending to a syslog server 2. call trace from sipx Granted the Mediant will lock up, it's probably worth a shot to get the last message possible before it goes away. I believe the issue will be in either the firmware for the Mediant or the configuration of it (or it may just not be supportable at this time by them). In my case I was running 3.10.2 using two different gateways with different results, but nothing that locked anything up or dropped any calls with 3.1 firmware. I think once you have debug logs you could ask the appropriate questions or at least provide adequate information to see if there is a resolution available from AudioCodes. I am not an AudioCodes user, Patton simply has never had the issues I have experienced with AudioCodes, so I am a bit biased there, and will admit to it. We have a couple of blue Audiocodes doorstops here, but no black Patton doorstops. Tony >>> "Jay Reeder" <[EMAIL PROTECTED]> 10/22/2008 8:08:54 AM >>> No, I didn't downgrade the firmware. It was the patch found here http://track.sipfoundry.org/browse/XCF-2716?page=com.atlassian.jira.plugin.s ystem.issuetabpanels:all-tabpanel that enables MOH for polycom phones in the sipx polycom config file template. As soon as I reversed that out of my phone profiles, calls could again be put on hold (and transferred) and the Mediant didn't crash. But we don't have MOH anymore. The relevant line removed was: <musicOnHold voIpProt.SIP.musicOnHold.uri="[EMAIL PROTECTED]"/> (where domain.com matches our domain) When that line was in the phones, we could call phone to phone, place calls on hold, and hear hold music. However, calls through the mediant placed on hold or attempted transfer would effectively lock-up the Mediant with all calls dropping, admin access not available, ping failure, etc. The NIC port light on the switch (for the Mediant) was going wild though. -- Jay _____ From: Picher, Michael [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2008 4:09 AM To: Jay Reeder; [email protected] Subject: RE: [sipx-users] New Polycom Firmware - MOH locks up Mediant 2000 Do you mean since you downgraded to Polycom 3.0.3b? If not, what is the MoH patch you are talking about? Thanks, Mike From: Jay Reeder [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 5:40 PM To: Picher, Michael; [email protected] Subject: RE: [sipx-users] New Polycom Firmware - MOH locks up Mediant 2000 Ok, thanks! Since removing the MOH patch to the sipx config file things have appeared to be fine. But we're not doing anything interesting.. just placing and receiving calls. -- Jay _____ From: Picher, Michael [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 5:34 PM To: Jay Reeder; [email protected] Subject: RE: [sipx-users] New Polycom Firmware - MOH locks up Mediant 2000 It is not but some have seen some problems with 3.1.0. I think it's worth a test. From: Jay Reeder [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 5:28 PM To: Picher, Michael; [email protected] Subject: RE: [sipx-users] New Polycom Firmware - MOH locks up Mediant 2000 Michael, I haven't. We were previously using 2.2.2 and upgraded to the 3.1.0 for the MOH. :-) Is the MOH also supported in firmware 3.0.3b? -- Jay _____ From: Picher, Michael [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 5:23 PM To: Jay Reeder; [email protected] Subject: RE: [sipx-users] New Polycom Firmware - MOH locks up Mediant 2000 Have you tried the same with Polycom firmware 3.0.3b? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jay Reeder Sent: Tuesday, October 21, 2008 10:59 AM To: [email protected] Subject: [sipx-users] New Polycom Firmware - MOH locks up Mediant 2000 Guys, I know this isn't the correct forum but has anyone seen this issue? We're using sipXecs version 3.11 with Polycom 330 phones (Bootrom version 4.1.1 and SIP version 3.1.0b). Incoming calls are received through an Audiocodes Mediant 2000 gateway with firmware version 5.20A.033.006 (via ISDN PRI) and outgoing calls are routed back through the same gateway over the PRI. When a call comes from the ISDN PRI through the Mediant 2000 to one of the polycom phones (on the new firmware, routed by sipX) and that call is put on hold, the Mediant "locks up". At that point we can't ping the Mediant or access the web admin. The Mediant's network switch port is flashing like crazy and all calls are effectively cut off. The call that was put on hold never hears hold music and all calls are disconnected. Has anyone seen this type of behavior before? Is there a setting in the Mediant that might affect this? Unfortunately I can't do much testing until after business hours. Thanks, Jay
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
