On Fri, 2009-10-16 at 10:14 -0400, Carolyn Beeton wrote: > The Bliss IE draft for Shared Appearances > (http://tools.ietf.org/id/draft-ietf-bliss-shared-appearances-03.txt) > requires proxies to add an Alert-Info header into INVITEs sent to > shared users (5.4): > > "The Appearance Agent MUST be able to communicate with the forking > proxy to learn about incoming calls and also to pass the appearance > number to the proxy to insert in the Alert-Info header field." > > Can anyone comment on this requirement and how we might implement it? > It seems to me that it would force the SAA and the Proxy to be > co-resident, and an authplugin in the Proxy would have to communicate > with the SAA process on every outgoing INVITE.
Would it be possible to route those INVITEs to the SAA (or some subsystem thereof), which would then redirect the INVITE to the real AOR with "?Alert-Info=xxx"? That would let the SAA decorate the incoming INVITE with Alert-Info without involving the proxy. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
