[reSIProcate] Using Update for provideOffer()

[Kovar, William (Bill)]

yes the endpoint can't handle Update w/SDP. I need to support Update for
display updates from one end (the switch) but I don't want to send
Update w/SDP to my endpoints.
 
Bill Kovar
bkovar at avaya.com
Avaya, Inc.
(732) 852-2609
 


  _____  

	From: Scott Godin [mailto:slgodin at icescape.com] 
	Sent: Tuesday, April 03, 2007 5:10 PM
	To: Kovar, William (Bill);
resiprocate-devel at list.resiprocate.org
	Subject: RE: [reSIProcate] Using Update for provideOffer()
	
	

	DUM will use UPDATE messages if the application lists it as a
support Method (which you have done) and if the far end advertises that
it supports update messages, in it's Allow header.  There is no switch
to disable this behaviour.  Is your far end having trouble handling a
hold via UPDATE?

	 

	From: resiprocate-devel-bounces at list.resiprocate.org
[mailto:resiprocate-devel-bounces at list.resiprocate.org] On Behalf Of
Kovar, William (Bill)
	Sent: Tuesday, April 03, 2007 3:25 PM
	To: resiprocate-devel at list.resiprocate.org
	Subject: [reSIProcate] Using Update for provideOffer()

	 

	In the past, when I sent an offer via provideOffer() when doing
a 3rd party Hold, an actual Invite would be sent out on the session. I
am now seeing, with different endpoints than what I tested with, that
the provideOffer() is using the Update method to send the offer.

	 

	I have enabled Update support, but the original endpoints I
tested with, Update was not used for re-invites.

	 

	Can someone enlighten me as to why the Update would be used
instead of the Invite? And how I might control it?

	 

	Bill Kovar

	bkovar at avaya.com

	Avaya, Inc.

	(732) 852-2609

	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070403/ff2acc65/attachment.htm>