You can forget about it.
SIP protocol is butchered, H323 is incomplete, proprietary protocol... is proprietary.

It took us better part of the month to integrate Asterisk to OS500.
There are bugs upon bugs in SIP and H323. Not to mention IP stack crashes in MCP2 if you’re not careful with extension diversions to VoIP trunks.
The only way to recover is to reset MCP2.

Our Samsung distributor would not even support you if they hear you doing SIP.
“Not supported” is all I get.

We originally wanted to connect a bunch of SIP phones to OS500. Bought 2 MGI’s and then found out that any SIP phones in
MMC840 are being ignored. After some debugging it works out that OS500 does not support SIP’s REGISTER command so you cannot authenticate any SIP phones to it.

We ended up building asterisk system that was working as a relay/proxy in front of OS500
The best thing is that we can now route calls to any VoIP provider that supports proper SIP/IAX2 protocols.


Quote
<font face="Verdana, Arial" size="2">Originally posted by FONEFXR:
Has anyone out there experimented with or have implemented any type of IP connection between the IDCS500 Rel 2 system via a MGI card or any other means to another manufactures switch specificly the Avaya's IP Office. If so could you give a little detial and email me. Thanks</font>