[SIPForum-discussion] RFC 2833 payload negotiation ...

[Manpreet Singh]

Offer is based off what it would like to receive and prefer to send. But
whatever the answer contains, the offerer has to send that payload type only
(for same media type), in which case A should send 100. ( both are using
different payload types for same telephony events.)

Please refer rfc 3264 section 5.1

M. 

-----Original Message-----
From: Madabhushi Pramod [mailto:madabhushi_p at yahoo.com] 
Sent: Thursday, August 25, 2005 11:48 AM
To: An open list for discussion of SIP-related topics
Cc: PMadabhushi at shoretel.com
Subject: [SIPForum-discussion] RFC 2833 payload negotiation ...

Do we negotiate RFC 2833 receive payload or transmit payload in
TELEPHONE-EVENT?

Lets take an example:

1) SIP device A calls SIP device B
2) A sends SIP INVITE with RFC 2833 payload as '96' in TELEPHONE-EVENT
3) B answers the call and send RFC 2833 payload as '100' in TELEPHONE-EVENT
as part of 200 Response.

When A sends out-of-band DTMFs to B (using Rfc 2833), which payload it
should use - 100 or 96?

Are we negotiating receive or transmit capabilities?

Is this documented anywhere?

Thanks
Pramod Madabhushi

Pramod Madabhushi
email: mpramod at hotmail.com,
       madabhushi_p at yahoo.com
Phone:001-408-204-8077


		
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs 
 
_______________________________________________
discussion mailing list
discussion at sipforum.org
http://sipforum.org/mailman/listinfo/discussion