You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I would like to suggest adding it to diego.go, to preserve the To field, in situations where a b2b receives the request from a different domain but the To realm is different.
example:
The text was updated successfully, but these errors were encountered:
Hi @SilvaMendes thanks for reporting. This could be yes and no. I guess this needs to be proven more is it worth. I think this is not even default behavior for asterisk. (Correct me if I am wrong).
Still passing custom headers is possible (yes content type and from is added always). So you can pass your own (TO header)
Anyway I would like to see some reference todo this change. I know cases where you do not want to share your internal domains or just letting endpoint to accept requested domain.
Hi @SilvaMendes so we are probably speaking some multi tenant setup. So yes I could see here some sense to have that default.
Yeah per RFC nothing is wrong here, just I want to weight is this something should be default behavior. Like topology hidding.
Anyway I think I will accept this feedback, but I need to add more logic in order to increase flexiblity
Hello, I would like to suggest adding it to diego.go, to preserve the To field, in situations where a b2b receives the request from a different domain but the To realm is different.

example:
The text was updated successfully, but these errors were encountered: