Re: [OpenSIPStack] OpenSBC terminate connection

[André M. <an...@ma...>]

Hello Joegen,

I have tested against the latest CVS version, 1.1.5-27, still no 
success. The softswitch still responds with a "400 Bad Request".

Regards,

Andre

jo...@op... schrieb:
> Andre,
> 
> This is a known problem area in OpenSBC.  Since we are a B2BUA and not a 
> proxy we terminate our dialogs based on successful processing of a BYE 
> request.  OpenSBC does not wait for a final response before it destroys 
> connections.  This ensures that the SBC does not end up with ghost 
> sessions as well if a certain UA is not able to handle authenticated BYE 
> requests.  This is the second time I have received this report regarding 
> this problem.  Can you provide me a with a level 5 log for this 
> problematic call offlist?  I'll see if an easy workaround is possible.  
> If you could, please also attach a wire shark capture of the successful 
> call you made using a UA directly calling your softswitch.  My e-mail 
> address is jo...@op...
> 
> Joegen
> 
> André Mamitzsch wrote:
>> Hello,
>>
>> I have seen a strange behavior with the OpenSBC1.1.5RC1. The scenario is 
>> as follows:
>>
>> The OpenSBC is configured in B2BUAUpperReg mode.
>>
>> I place a call from a SIP client (A) to a PSTN Phone (B). The connection 
>> is established whithout any problems. A goes on hook and sends a BYE to 
>> which the SBC immediately replies with a 200 OK.
>>
>> Another BYE message is being sent out to the softswitch platform.
>>
>> The softswitch challenges authentication and therefore responds with a 
>> 401  unauthorized message. Since the SBC, at least that's my assumption, 
>> has already successfully terminated the internal connection there is no 
>> match and the requested authenticated BYE will never be send out. This 
>> behavior results in ghost connections and the billing runs until B goes 
>> on-hook as well.
>>
>> I have tested the same scenario with my SIP client directly connected to 
>> our softswitch platform and did not detect the problem there. Upon 
>> receiving the 401 unauthorized message, the client resends the BYE 
>> containing the authentication information.
>>
>> I have checked the RFC 3261 this morning and tried to find out whether 
>> it is a regular behavior to reply to a BYE message with authentication 
>> challenge or not. I could not find any hint there.
>>
>> How difficult is it to change this behavior and wait for confirmation 
>> before terminating the entire connection ?
>>
>> Regards,
>>
>> Andre
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>   
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - http://www.avg.com 
>> Version: 8.0.175 / Virus Database: 270.8.2/1743 - Release Date: 10/24/2008 8:33 AM
>>
>>   
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel