[Spce-user] 200 OK answer from wrong socket after BYE from peer

[Klisch, Martin]

Hi,

when using extra_sockets for an "internal" routing connection to our Softswitch I have the faulty behavior of not using the configured extra socket for the 200 OK of a BYE sent by the Softswitch.

In picture:

Hangup in PSTN -> Softswtich -> BYE -> NGCP on extra socket 1.2.3.4 ... 200 OK from default NGCP socket 1.1.1.1 -> Softswitch

After analyzing it seems that there is a problem with the routing via SEMS. So in the BYE from LB to SEMS I can see the correct P-Sock-Info header with the extra socket. But as SEMS tears down the connection as B2BUA there is P-Out-Socket in the 200 OK generated by SEMS. Therefore the default socket of the LB is used to send the 200 OK back to the Softswitch. Of course the Softswtich does never see the 200 OK because of firewall and routing setting.

Is this as designed or a bug? My current workaround is setting the correct FS after checking for 200 OK replies of BYE messages with the help of the received header.

Thanks in advance!

--
Mit freundlichen Grüßen,
Best regards,

Martin Klisch
Communication Concept GmbH
Voice and Data
Theklaer Strasse 42
04347 Leipzig

Telefon: +49 341 23405 211
Fax:     +49 341 23405 190
Mobile:  +49 151 24038213
Mail:    m.klisch at ccgmbh.de


Communication Concept GmbH

Registergericht: Amtsgericht Leipzig
Registernummer:  HR 6383
Geschäftsführer: Rainer Strehle,Torsten Below, André Mamitzsch,Thomas Eibeck

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20130429/2a403bd9/attachment.html>