Hello SIPers,
What is the most prevalently used SIP RFC to implement pay phone. I am
mainly looking for RFC that specify how to implement answer supervision
and pulse metering. Thanks a lot for your time.
- ramesh
___
Sip-implementors mailing list
Sachin Rastogi writes:
> I have a User Agent, which can decode H.264-HP as well as H.264-BP. But it
> can encode only H.264 BP. So how should I share my offer in SDP
Clearly, you can only express this in SDP by providing two different
m-lines, one for the send codec and one for the receive codecs
On 10/6/16 12:40 AM, Sachin Rastogi wrote:
Hi Everyone,
I have a User Agent, which can decode H.264-HP as well as H.264-BP. But it
can encode only H.264 BP. So how should I share my offer in SDP
Option 1 :
m=video 2300 RTP/AVP 100 109
a=rtpmap:100 H264/9
a=fmtp:100 profile-level-id
Neel,
There is no specification that branch parameter MUST be a RFC 4122 GUID. In
fact, RFC 3261 branch parameters are never an RFC 4122 GUID since they
starts with the magic cookie "z9hG4bK". All that it is required that branch
parameter MUST be globally unique. Applications can generate branch
p
Hi,
If branch parameter got introduced in 3261 and this MUST be GUID.
>From 3261:
The branch parameter value MUST be unique across space and time for
all requests sent by the UA. The exceptions to this rule are CANCEL
and ACK for non-2xx responses. As discussed below, a CANCEL reques
