[SIPForum-discussion] Multiple "Supported" SIP header values

[Joshua Hedrick]

We have a SIP/IMS First office Application Systems Engineer position
open with a telecommunications company in Raleigh, North Carolina for a
long-term, open-ended contract that can be pretty flexible on pay.
Thanks!  Please forward on resumes or information about people if anyone
is interested.  Thanks!
 
Joshua G. Hedrick
Technical Recruiter
Apex Systems, Inc.
5430 Wade Park Blvd, Suite 302
Raleigh, NC 27607
919-836-1234
Toll Free: 800-552-5090
Fax: 919-836-1225
jhedrick at apexsystemsinc.com 
www.apexsystemsinc.com <http://www.apexsystemsinc.com/> 

 


________________________________

	From: discussion-bounces at sipforum.org
[mailto:discussion-bounces at sipforum.org] On Behalf Of manish srivastava
	Sent: Wednesday, January 07, 2009 3:26 AM
	To: cperry15 at gmail.com
	Cc: discussion at sipforum.org
	Subject: Re: [SIPForum-discussion] Multiple "Supported" SIP
header values
	
	
	Yes you can have multiple values in Supported header separated
by comma
	 
	for example 
	 
	Supported: 100rel, timer

	 

	 
	Regards
	Manish


	 
	On 1/6/09, cperry15 at gmail.com <cperry15 at gmail.com> wrote: 

		We have a SIP Application server. We are looking to add
some custome development to support Geolocation 
		
		I have notice that out of the box our SIP App server has

		
		"Supported: timer " 
		
		
		When looking at the Geolocation Specs. I noticed that
the Supported Header is only Geolocation 
		
		Can you have multiple values in the Supported Header 
		
		Is the a delimiting character that would be used like a
comma or a semicolon 
		
		i.e (Supported: timer; geolocation) 
		
		-CP
		_______________________________________________
		This is the SIP Forum discussion mailing list
		TO UNSUBSCRIBE, or edit your delivery options, please
visit http://sipforum.org/mailman/listinfo/discussion
		Post to the list at discussion at sipforum.org
		
		


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20090107/32b500db/attachment-0002.html>