Difference SIP/H323

[hofmad]

Hey there,
our customer is using 99% SIP phones and I found out that they don't support all the features of the WTI Web Service with DMCC...
I can register the extension with "registerTerminal" but the "MakeCall" function is only working, if there is a SIP (Soft-)Phone registered. With H323 I can place the same call without having another physical or "virutal" phone registered.
Additionally I can "press" every H323 Button virtually with the "ButtonPress" function on H323, but at least the "hntpos-bsy" Button on SIP can't be "pressed" with this function.

Will there be DMCC enhancements to fully support SIP in the (near) future?? Or is PPM the only way to do this? (Much work just to press one button)...

Thanks.

[flynn1]

DMCC and WTI provide less support for SIP stations than for H.323. This is described in Chapter 8: Session Initiation Protocol (SIP) of "Avaya Aura Application Enablement Services Overview and Specification".

In summary, for SIP stations, DMCC & WTI support:
1. Most Third-party functions such as Make Call
2. Media functions as used by a call recorder (Media Start/Stop events) but only if the application registers the terminal in Independent mode.

It does not support other First Party functions (e.g. button press or lamp events.).

Martin

[jtb1]

Will there be DMCC enhancements to fully support SIP in the (near) future?? A: no
Or is PPM the only way to do this? A: I am not aware that you can do it with PPM - but you learn something new every day. I would think the mechanism is through Feature Name Extensions. SIP is different than H.323 in enough ways the DMCC protocol could not be extended to work in that environment (particularly because the phone itself supports a functional call model - not a stimulus one).