Hello All,
Greg Fausak <greg(a)addabrand.com> wrote:
I am seeing non-unique call IDs from a UA.
SHould I reject a call if the Call-ID is not unique? Has
anyone else messed with this? It is a big accounting problem!
Greg Fausak
I apologize if this is an off-topic question, but this is about SIP. Hope folks dont
mind...
This thread is a bit old, but i am curious about a comment i saw in the Asterisk SIP
channel code.
It is mentioned that some vendors send multiple calls with the same Call-ID and different
tags to
simplify billing. It also says that it is an overhead for the other *sane* SIP
implementations. I
am learning SIP and dont have much idea about billing, but what makes some vendors think
that it
is easy for billing, where as it is a big problem for some others? What is the right way
of doing
it? How can such differences bring consistancy among different SIP implementations? What
method
does SER follow?
This is from the Asterisk SIP channel code:
/* In principle Call-ID's uniquely identify a call, however some vendors
(i.e. Pingtel) send multiple calls with the same Call-ID and different
tags in order to simplify billing. The RFC does state that we have to
compare tags in addition to the call-id, but this generate substantially
more overhead which is totally unnecessary for the vast majority of sane
SIP implementations, and thus Asterisk does not enable this behavior
by default. Short version: You'll need this option to support conferencing
on the pingtel */
Regards,
=====
Girish Gopinath <gr_sh2003(a)yahoo.com>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail