Saurav
We always try to complete call somehow as providing reliable service to
user is utmost important and i have seen solutions voilating standards in
actual deployments to provide services to end user.
And luckily in our scenario standard is recommending the acceptance of diff
payloads to make c
On 11/5/14 7:05 AM, Brett Tate wrote:
But my newer question is even by sending BYE for this
flow A is not violating any RFC. Since from the booth
RFCs mentioned above the expected behavior mentioned
by Ankur is SHOULD way not in MUST. So A behavior
may not the be best one but also not a violatio
> But my newer question is even by sending BYE for this
> flow A is not violating any RFC. Since from the booth
> RFCs mentioned above the expected behavior mentioned
> by Ankur is SHOULD way not in MUST. So A behavior
> may not the be best one but also not a violation of RFC.
>
> Whether my above
Hi,
I have observed two points here,
1. UA A doing wrong here in SDP Offer
Here dynamic payload is used for registered CODER ALAW(8) & uLAW(0) &
repetition of
the same coder with different payload two times(one registered payload
(e.g. 8,0) and one dynamic payload(e.g. 106,107)).
> >a=rtpmap:10
Hi Sourav,
Well, yes, there might be an indication in the BYE message or the
UA's error log why the BYE is sent and/or why no media has been
exchanged. If a media mismatch is the cause, one might have
expected a 4XX response instead.
You need a
Hi Brett & Ankur,
At first thanks to both of you for your prompt answer.
So after considering RFC 3264 ( importantly the section 8.3.2 mentioned in
Ankur's latest reply) & RFC 4566, I came to this conclusion instead of sending
A could have continue the call.
But my newer question is even
