El Miércoles, 29 de Abril de 2009, Manoj Priyankara [TG] escribió:
> Hi All,
>
> I have seen some equipment vendors have implement security functions
> such as DDoS protection in the P-CSCF. According to my understanding
> this should be a function of the SBC. Is this a standard thing?
Please, whe
Hi All,
I have seen some equipment vendors have implement security functions
such as DDoS protection in the P-CSCF. According to my understanding
this should be a function of the SBC. Is this a standard thing?
Thanks
BR,
Manoj
___
Sip-implementors m
Hi All,
I have seen some equipment vendors have implement security functions
such as DDoS protection in the P-CSCF. According to my understanding
this should be a function of the SBC. Is this a standard thing?
Thanks
BR,
Manoj
-Original Message-
From: sip-implementors-boun...@lists.cs.
Paul Kyzivat wrote:
Dushyant Dhalia wrote:
In 3GPP specs, related to IMS procedure, it's written that P-CSCF
sends the SUBSCRIBE request to I-CSCF which in turns finds the
address of S-CSCF through Cx query. My question is why can't P-CSCF
send the SUBSCRIBE directly to S-CSCF using Service-
My experience has been that Session Timers (periodic reINVITEs to the
endpoints mid-call) are a perfectly viable signaling-only solution to
the problem of billing discrepancies / ad infinitum CDRs due to lack
of media handling.
I don't think the people who think you can do billing purely out
Dushyant Dhalia wrote:
> In 3GPP specs, related to IMS procedure, it's written that P-CSCF sends
> the SUBSCRIBE request to I-CSCF which in turns finds the address of
> S-CSCF through Cx query. My question is why can't P-CSCF send the
> SUBSCRIBE directly to S-CSCF using Service-Route it recei
It seems that usually people who ask about billing assume that something
in the signaling path can just generate billing records at start and end
of call, or save some data from start of call and generate a CDR when
the call ends.
But that is naive. If you are only on the signaling path, not th
Scott Lawrence wrote:
> On Mon, 2009-04-27 at 02:22 +0800, Avasarala Ranjit-A20990 wrote:
>> Hi
>>
>> I do not think a SIP entity can return a 302 response with contact
>> containing "mailto:"; because SIP is not a email protocol like SMTP. So I
>> feel its an error to receive "mailto: in Contact
Hi Vijay,
I think that any media specific data should be passed as the fmtp parameter,in
a way that the SDP does not have to understand them,and regarding the
offer-answer SDP delaing with the fmtp parameters,this is what rfc 3264 says,
"The interpretation of fmtp parameters in an offer depen
Hi Vijay,
you should check whether the same rtpmap value is being used by both the
offerer and the answerer for the dynamic payloads,for the dynamic payloads the
value should be in the range 96-127,and atleast one codec should overlap among
the negotiated codec.
the payload type mappings fro
[Resending to the correct sip-implementors mailing list]
Though the PIDF-LO format allows one to convey multiple alternate locations,
I am wondering if there are any implementations using multiple PIDF-LO
documents. The following are use cases where I think it may be required to
signal multiple lo
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
12 matches
Mail list logo
