-
|
I haven't found an API function that I could use to disallow target refresh (re-INVITE or UPDATE) and response, for example, with According to call_sdp_change_allowed function negotiation is allowed if this is true: If denying of negotiation is not currently possible, what would be the best way to implement it? |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 10 replies
-
|
I haven't got any comments about this. According to https://www.rfc-editor.org/rfc/rfc6141 it is perfectly OK to reject re-INVITE. See, for example, section 3.1, Figure 1. Is it so that baresip does not currently support rejection of re-INVITE? If it is, could someone give a hint on how to do it? |
Beta Was this translation helpful? Give feedback.
-
|
It might be possible to reject re-INVITE when handling BEVENT_CALL_REMOTE_SDP by calling but I have not figured out how to access |
Beta Was this translation helpful? Give feedback.
-
|
Yes, there is |
Beta Was this translation helpful? Give feedback.
-
|
Another good option would be if I could reject the re-INVITE by calling |
Beta Was this translation helpful? Give feedback.
-
|
Do you mean that I should change this to and return some error code to prevent |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the advice. I called Otherwise OK, but first line of the response could be improved: Do I need to call |
Beta Was this translation helpful? Give feedback.
-
|
Fine, I can use one of the |
Beta Was this translation helpful? Give feedback.
-
|
Christian Spielberger writes:
Do you want to create a PR for the call.c changes? Or should I?
If you have time, please create the PR.
|
Beta Was this translation helpful? Give feedback.
Okay, not so bad. Currently only linux error codes plus the error codes from
re_types.hare supported. The texts come fromstr_error()from re, which fall back tostrerror_r()on linux (and Android?). SIP status codes are not supported.In the following man page you find some of the error nums + their strings.