Hello, We have customers terminating static and registered trunks on their Zultys systems with no issues. We are running AcmePacket SBCs in front of our switch. Regards, Ken From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Sanjay Srinivasan Sent: Tuesday, October 16, 2012 12:55 PM To: voiceops at voiceops.org Subject: [VoiceOps] SIP trunks to a Zultys MX250 anyone? I have a customer opportunity to deliver SIP trunks to a Zultys MX 250 IP PBX. In the world of IP PBXs, that name is not one I run in to a lot. Does anyone have experience with this box? SIP implementation quality? If you have done this, any obvious, basic issues? My SIP delivery mechanism would be via ACME Packet. Thanks, SANJAY SRINIVASAN | Anywhere (480) 385-7062 | Fax (480) 385-7007 | ssrinivasan at telesphere.com<mailto:ssrinivasan at telesphere.com> Telesphere | 9237 E. Via de Ventura, Ste 250 | Scottsdale, AZ 85258<http://maps.google.com/maps?f=q&q=9237%20E.%20Via%20de%20Ventura,%20Ste%2025...> [cid:image001.jpg at 01CDABA2.E7E57A40]<mailto:features at telesphere.com> [www.telesphere.com]<http://www.telesphere.com/> [Facebook]<http://www.facebook.com/telesphere> [Twitter]<http://www.twitter.com/telesphere> [LinkedIn]<http://www.linkedin.com/companies/telesphere> [YouTube]<http://www.youtube.com/user/telesphere> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Although the company has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Telesphere.

We have been testing it on our 2 SBCs - ACME and Sansay. Initial testing has revealed that it changes the SDP Media port between the Initial INVITE and the follow up INVITE (with credentials). That seems to work on ACME , but not on Sansay. The other issue we noted on ACME was that calls hairpinned back to the SIP trunk get no Audio either way, when you clearly see 2 way RTP traffic between Zultys and ACME. From looking at similar issues in the past, the TTL on RTP packets usually is the culprit going all the way to the Terminating carrier - not gotten to the bottom of this one completely yet. On Tue, Oct 16, 2012 at 12:54 PM, Sanjay Srinivasan < ssrinivasan at telesphere.com> wrote:

I have a customer opportunity to deliver SIP trunks to a Zultys MX 250 IP PBX. In the world of IP PBXs, that name is not one I run in to a lot.****

** **

Does anyone have experience with this box? SIP implementation quality? If you have done this, any obvious, basic issues? My SIP delivery mechanism would be via ACME Packet.****

** **

Thanks,****

** **

*SANJAY SRINIVASAN* | Anywhere (480) 385-7062 | Fax (480) 385-7007 | ssrinivasan at telesphere.com Telesphere | 9237 E. Via de Ventura, Ste 250 | Scottsdale, AZ 85258<http://maps.google.com/maps?f=q&q=9237%20E.%20Via%20de%20Ventura,%20Ste%2025...> ****

** <features at telesphere.com>****

[image: www.telesphere.com] <http://www.telesphere.com/>****

[image: Facebook] <http://www.facebook.com/telesphere>****

[image: Twitter] <http://www.twitter.com/telesphere>****

[image: LinkedIn] <http://www.linkedin.com/companies/telesphere>****

[image: YouTube] <http://www.youtube.com/user/telesphere>****

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Although the company has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Telesphere.****

** **

_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops