Closed deruelle closed 7 years ago
I am implementing such feature on the DMZ side in order to fix UA's Via/Contact headers. MZ side is supposed to be (mostly), in the same LAN segment as the target SIP server. Are you considering some NAT issues on the MZ side?
I made a typo when creating the issue.
@deruelle NAT issues still happen, need to double check
@deruelle NAT Patch for REGISTER is up on cloud
@ocarriles I just tested. When I registered 13 and I try to call 11 (11 is not registered). I get the announcement that tells 11 is not available correctly but I don't get the BYE.
I am online at the box. you can call 2002
El 25/11/2016 a las 19:15, Jean Deruelle escribió:
@ocarriles https://github.com/ocarriles I just tested. When I registered 13 and I try to call 11 (11 is not registered). I get the announcement that tells 11 is not available correctly but I don't get the BYE.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RestComm/sbc/issues/19#issuecomment-263027666, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ7NkvAtaLXyTknScosI7rCURevVmzG9ks5rB14agaJpZM4JKihe.
-- Ing. Oscar Andrés Carriles Ingenieria eolos IT CORP mail : ocarriles@eolos.la Phone ARG: +541150323352 ext. 2125 Phone USA: +13056005922 ext. 2125 twitter : @eolosIT facebook : Eolos linkedin : eolosIT skype : eolos.la web : www.eolos.la
Let's do it on Tuesday. Everybody is sleeping there :)
last pull updated on cloud :)
Tested successfully today
Handle patching of SDP and SIP Messages to handle NAT topologies correctly