Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Kamailio should never simply drop messages with some invalid characters or "slightly" broken headers (or other values) because it must be flexible in accepting. One of the big advantages of Kamailio is the ability to allow fixing broken messages. So unless it is really broken that basic SIP parsing cannot be done, it should be left for config writer to decide when to drop or try to fix.
I am not sure if you are right with the & character here, because it is in the display name is not in the URI. Are you sure that & is not allowed in the display name? The references you pasted refer to URI, as I got it at first read.
Also, the main role of the proxy should be checking validity of all values in the signaling, but dispatching traffic, letting the end points to decide what they can handle or not. For example, if the sdp has some invalid codec id or parameters, is not the proxy that should catch that.
Then, not everything has to be done in the C code, there can be conditions done also via regexp matching or using existing functions such as:
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.