We have been making a development on a SIP application server for using RCC feature of OCS (app server is switching function and MOC is computing function). Here is the problem: - I've seen that when a CSTA xml body contains deviceIDs in SIP uri format, MOC (or OCS) ignores that message and RCC call cannot be established. However, when I set related deviceID field as tel:+<number> format, everything is ok, call establishes. For instance, Established Event below fails since callingDevice is in sip uri format:
But when I set the callingDevice in tel uri format just as below, call establishes: <?xml version="1.0" encoding="UTF-8"?> <EstablishedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed4"> <monitorCrossRefID>3189b79032a8c4253d75950dd3b84ff4369600a</monitorCrossRefID> <establishedConnection> <callID>08a0e79032c97a5013d759505d734aefa018a1f@47.168.59.152</callID> <deviceID>tel:+12165223007</deviceID> </establishedConnection> <answeringDevice> <deviceIdentifier>tel:+12165223007</deviceIdentifier> </answeringDevice> <callingDevice> <deviceIdentifier>tel:+12165224556 </deviceIdentifier> </callingDevice> <calledDevice> <deviceIdentifier>tel:+12165223007</deviceIdentifier> </calledDevice> <lastRedirectionDevice> <notRequired/> </lastRedirectionDevice> <cause>newCall</cause> </EstablishedEvent>
Is there any limitation or restriction that we should use tel uri format in deviceID fields for MOC, although there isn't a restriction about it in ECMA (269,323 and TR87)?