Blogs

Showing 1 - 5 of 21 results.
Items per Page 5
of 5
First Previous Last

Forums

« Back to SIP Line Questions

Callback service with RFC 4235 and 3rd party SIP Device

Combination View Flat View Tree View
Threads [ Previous | Next ]
Callback service with RFC 4235 and 3rd party SIP Device
Answer
6/25/09 8:04 PM
Hello:
 
We are developing a SIP device and we have implemented several SIP features and RFC´s. In fact we had implemented RFC 4235 for Callback services subscription (dialog info + xml), but when testing this feature with a CUCM v6.1.1 the subscription does not work and when debugging SIP messages, the application media shows the message (399 dialog package not licensed).

We checked the same application media is used in Cisco IP Phones with SIP firmware, so we don´t know what to do in order to verify the feature with CUCM (it was verified with Asterisk and it works)

Regards

Jose
Flag

RE: Callback service with RFC 4235 and 3rd party SIP Device
Answer
6/23/10 9:49 AM as a reply to Jose Ignacio Guzman Crespo.
As implemented by Cisco SIP phones, I believe the callback feature utilizes some proprietary SIP extensions developed by Cisco.  Use of these extensions requires a special licensing agreement with Cisco, and a Cisco Options Package (.cop) installer to define a new custom device type on UCM.  Devices which connect as the built-in 'standard 3rd party SIP' devices cannot use these extended features.
Flag

Collateral


No files available