Hi, everyone!
Check out my new blog [1] that describes how to enhance your SIP proxy
calls with complex media capabilities in a SIP-compliant manner, using
the new Media Exchange module[2]!
[1]
https://blog.opensips.org/2020/03/26/enhanced-media-capabilities-in-opensips-3-1/
[2] https://ope
Thanks a lot for your explanation, Ben! I thought that there can be an
issue with Server A not accepting my new SIP response, it looks like
they're doing matching only based on SIP To tag and completely ignoring any
Call-ID or DID matching as well as From tag matching, in my case From tag
is alway
I see. If that is your need then you will get a new tag. As far as I know it
would be a feature enhancement to change that behavior, though someone from
OpenSIPS team may need to check me on that. It is operating within the RFC for
this [1]:
When the proxy is aggregating information from severa
But the question is still here - how can I send a different t_reply code
from failure_route? And then stop processing any further SIP messages?
пт, 27 мар. 2020 г. в 01:23, Yury Kirsanov :
> The problem is that I need to go through a list of SIP servers, analyze
> response of each of them and if
The problem is that I need to go through a list of SIP servers, analyze
response of each of them and if it's an error like 4XX, 5XX or 6XX I need
to send appropriate response to originating server. Let's say I'm not only
adding a Reason field but upon receipt of 404 Not Found I want to respond
with
Also, for this:
“Now, for some reason, OpenSIPS forwards original reply from Server B to Server
A with the same 'To' tag as in 183 Session Progress”
Server B is retransmitting the 404 because it did not receive an ACK. The
retransmission does not trigger failure_route and so is not manipulated
“I don't need to proxy response from server B, I need to analyze its response
and send a response to server A according to my needs”
But the only thing you are doing is adding a reply header? You can add that to
Server B’s reply without creating a whole new reply. Do you have some other
change
Hi,
As per my original email:
1. I was doing exactly as you suggested, in failure_route I'm using
t_reply("404","Not Found") and it comes out with a wrong To: tag.
2. I don't need to proxy response from server B, I need to analyze its
response and send a response to server A according to my needs.
You don’t have to call t_reply from failure_route. The default action of
failure_route is already to relay the response back upstream [1], unless you
created a new branch. Simply call append_to_reply and then exit. It is the
t_reply call that is confusing things.
[1] - https://www.opensips.org/
Something like:
failure_route[1] {
if (t_check_status("4[0-9][0-9]")) {
t_reply("404", "whatever ");
break;
}
}
Taken from https://opensips.org/pipermail/users/2009-September/008294.html
On Thu, 26 Mar 2020 at 08:13, Yury Kir
Hi,
I'm using an OpenSIPS as a proxy between two servers. First one is sending
SIP INVITE to OpenSIPS, then OpenSIPS forwards request to second server.
I'm creating a dialog on initial INVITE. Second server then replies with
SIP 183 Session Progress, plays back a message and then responds with 4XX
11 matches
Mail list logo
