This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
cookbooks:4.4.x:core [2016/03/28 23:26] miconda created |
cookbooks:4.4.x:core [2016/05/23 10:55] giavac [force_rport] Minor edits |
||
---|---|---|---|
Line 125: | Line 125: | ||
"this is a string value" | "this is a string value" | ||
- | 'this is another string value" | + | 'this is another string value' |
// next is a boolean | // next is a boolean | ||
Line 2259: | Line 2259: | ||
==== force_rport ==== | ==== force_rport ==== | ||
- | Force_rport() adds the rport parameter to the first Via header of the received message. Thus, Kamailio will add the received | + | force_rport() adds the rport parameter to the first Via header of the received message. Thus, Kamailio will add the received port to the top most Via header in the SIP message, even if the client does not indicate support for rport. This enables subsequent SIP messages to return to the proper port later on in a SIP transaction. |
- | This is useful for NAT traversal, to enforce symmetric response | + | This is useful for NAT traversal, to enforce symmetric response |
- | The rport parameter is defined in RFC 3581. | + | The rport parameter is defined in [[https:// |
- | Note: there is also a force_rport parameter which changes the gobal behavior | + | Note: there is also a force_rport parameter which changes the global behaviour |
Example of usage: | Example of usage: | ||
force_rport(); | force_rport(); | ||
- | |||
==== add_rport ==== | ==== add_rport ==== | ||
Alias for force_rport(); | Alias for force_rport(); |