[Devel] Processing REGISTER requests

Klaus Darilion klaus.mailinglists at pernau.at
Thu Oct 6 18:58:00 CEST 2005


Hi Dan!

Would you provide a patch? Because there are other important things that 
should be added and I do not want our developers to get overloaded (too 
much).

klaus


Dan Pascu wrote:
> On Thursday 06 October 2005 19:07, Klaus Darilion wrote:
> 
>>>First registration.
>>>
>>>Phone 1:
>>>  callid = somecallid
>>>  cseq   = 101
>>>  ip     = 10.0.0.1
>>>  port   = 5060
>>
>>Ok! Now the second phone will register:
>>
>>>Phone 2:
>>>  callid = anothercallid
>>>  cseq   = 101
>>>  ip     = 10.0.0.1
>>>  port   = 5060
>>
>>Now ser will use your algorithm:
>>
>>1. Check for callid: not found
>>
>> > 2. if previous step failed to find an entry use the current
>> > algorithm to lookup by contact.
>>
>>This will match the registration from phone 1. Thus, combining call-id
>>and the existing algorithm won't work!
> 
> 
> That's true if you use fix_nated_register() and store private contacts, 
> but still this will improve the case where you store public contacts.
> Overall won't work worse, but the same or better. I don't claim it's a 
> panacea.
> 
> 
> 




More information about the Devel mailing list