What happened:
Sending SIP MESSAGE to the outbound proxy which requires authentication results in an endless MESSAGE loop.
What you expected to happen:
SIP MESSAGE should be successfully sent. Outbound proxy authentication should also be successful.
How to reproduce it (as minimally and precisely as possible):
Create a client, log in with it in Jitsi and try to send a message to the number which is not present in Restcomm DB.
Anything else we need to know?:
Environment:
Restcomm Connect version (from startup logs): compiled from master branch (2194dee4fc524cdfd0af77a218ba5f212f97f7c5)
Cloud provider or hardware configuration: hardware
OS (e.g. from /etc/os-release): Ubuntu 18.04.4 LTS
Kernel (e.g. uname -a): 4.4.0 x86_64 GNU/Linux
Deployment method (e.g. docker-compose, with linked docker-compose.yml file,
or application server info + deployment option): JBoss AS 7.2.0.Final
Others:
If you need Jitisi TCP dump or any other info, please let me know
Is this a BUG REPORT or FEATURE REQUEST?:
What happened: Sending SIP MESSAGE to the outbound proxy which requires authentication results in an endless MESSAGE loop. What you expected to happen: SIP MESSAGE should be successfully sent. Outbound proxy authentication should also be successful. How to reproduce it (as minimally and precisely as possible): Create a client, log in with it in Jitsi and try to send a message to the number which is not present in Restcomm DB.
Anything else we need to know?:
Environment:
uname -a): 4.4.0 x86_64 GNU/Linuxdocker-compose, with linkeddocker-compose.ymlfile, or application server info + deployment option): JBoss AS 7.2.0.FinalIf you need Jitisi TCP dump or any other info, please let me know