I support what Dale says. For more info, see section 5.3 of RFC 6337.
Thanks,
Paul
On 9/15/11 4:59 PM, Worley, Dale R (Dale) wrote:
>> From: Sproul, Barry K [barry.spr...@verizonwireless.com]
>>
>> I have an issue between 2 vendor platforms that causes permanent audio
>> on hold.
To: ext Sproul, Barry K; sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] Inter Vendor Offer/Answer a=inactive
Looks like a-side don't want talk.
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors
> From: Sproul, Barry K [barry.spr...@verizonwireless.com]
>
> I have an issue between 2 vendor platforms that causes permanent audio
> on hold. Initial invite from party A contains SDP offer with sendrcv
> and multiple codecs. Party B returns 200ok with SDP answer and
> includes attribute of a=in
a.edu
Subject: [Sip-implementors] Inter Vendor Offer/Answer a=inactive
I have an issue between 2 vendor platforms that causes permanent audio
on hold. Initial invite from party A contains SDP offer with sendrcv and
multiple codecs. Party B returns 200ok with SDP answer and includes
attribute of a=inactive
I have an issue between 2 vendor platforms that causes permanent audio on hold.
Initial invite from party A contains SDP offer with sendrcv and multiple
codecs. Party B returns 200ok with SDP answer and includes attribute of
a=inactive with multiple codecs. Party A reinvites with 2 preferred cod