Examples of AllowEventsHeader

javax.sip.header.AllowEventsHeader

etf.org/rfc/rfc3265.txt">RFC3265, this header is not part of RFC3261.

The AllowEventsHeader includes a list of tokens which indicates the event packages supported by the client (if sent in a request) or server (if sent in a response). In other words, a node sending an AllowEventsHeader is advertising that it can process SUBSCRIBE requests and generate NOTIFY requests for all of the event packages listed in that header.

Any node implementing one or more event packages SHOULD include an appropriate AllowEventsHeader indicating all supported events in all methods which initiate dialogs and their responses (such as INVITE) and OPTIONS responses. This information is very useful, for example, in allowing user agents to render particular interface elements appropriately according to whether the events required to implement the features they represent are supported by the appropriate nodes.

Note that "Allow-Events" headers MUST NOT be inserted by proxies. @author BEA Systems, NIST @version 1.2

org.zoolu.sip.header.AllowEventsHeader

SIP Header Allow-Events


            Header hdr = getHeaderFactory().createHeader("ms-keep-alive",
                    "UAS; tcp=yes; hop-hop=no; end-end=yes; timeout=600");
            response.addHeader(hdr);


            AllowEventsHeader ahdr = getHeaderFactory()
                    .createAllowEventsHeader("presence");
            response.addHeader(ahdr);
        }


        return response;

   }
   /** Gets AllowEventsHeader */
   public AllowEventsHeader getAllowEventsHeader()
   {  Header h=getHeader(SipHeaders.Allow_Events);
      if (h==null) return null;
      return new AllowEventsHeader(h);
   }

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of AllowEventsHeader

Examples of javax.sip.header.AllowEventsHeader

Examples of org.zoolu.sip.header.AllowEventsHeader