Hi All,
The Advice of Charge (AOC) service allows the served user to be informed of IP
Multimedia session related charging information.
In order to support Advice of Charge during the call (AOC-D), there is a way
like SIP method to give charging information to served user during the call.
As per
RFC 3261 states that large SIP requests, within 200 bytes of the
maximum transmission unit (MTU), should be transmitted over TCP.
Transport over TCP avoids UDP fragmentation, and the switch to TCP can
occur even if the gateway is configured to use UDP.
I am reading that Dynamic transport selection
Saúl Ibarra Corretgé wrote:
> Well, those 2 things just can't happen at the same time :-S If you are
> not in the media path and DTMF tones are not sent to you there is very
> little you can do there IMHO.
That is true if DTMF is carried in the media and not in signaling.
I fail to understand wh
From: Mikko Lehto [msle...@gmail.com]
> 2833-style DTMF is very common in "pure SIP" situations and is supported by
> many telephone models.
Sure.
But what can you do when you have a requirement to 1) allow direct RTP
and 2) to capture keyevents for middl
On Mon, Jan 31, 2011 at 6:36 PM, Mikko Lehto wrote:
> Worley, Dale R (Dale) wrote:
>
>> 2833-style DTMF is very common in "pure SIP" situations and is supported by
>> many telephone models.
>
> Sure.
> But what can you do when you have a requirement to 1) allow direct RTP
> and 2) to capture key
Worley, Dale R (Dale) wrote:
> 2833-style DTMF is very common in "pure SIP" situations and is supported by
> many telephone models.
Sure.
But what can you do when you have a requirement to 1) allow direct RTP
and 2) to capture keyevents for middlebox services?
--
Mikko
___
From: sip-implementors-boun...@lists.cs.columbia.edu
[sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Mikko Lehto
[msle...@gmail.com]
With INFO mess, few NOTIFY event mechanisms, RFC 2833/4733 and RFC 4730
in mind, what do you think is the be
