[VoiceOps] SIP trunks to a Zultys MX250 anyone?

[Ken Mix]

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%20250%2CScottsdale%2CAZ%2C85258>

[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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20121016/6ce5359f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 14641 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20121016/6ce5359f/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 17174 bytes
Desc: image002.jpg
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20121016/6ce5359f/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 2475 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20121016/6ce5359f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 2465 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20121016/6ce5359f/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 2424 bytes
Desc: image005.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20121016/6ce5359f/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2432 bytes
Desc: image006.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20121016/6ce5359f/attachment-0007.png>