[asterisk-bugs] [JIRA] (ASTERISK-29242) pjsip: Documentation for transport handling is short / partly wrong

[Alexander Traud (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256079#comment-256079 ] 

Alexander Traud commented on ASTERISK-29242:
--------------------------------------------

Micheal, is ASTERISK-29111 related?

> pjsip: Documentation for transport handling is short / partly wrong
> -------------------------------------------------------------------
>
>                 Key: ASTERISK-29242
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29242
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Documentation
>    Affects Versions: 18.0.1, 18.1.0
>         Environment: CentOS 7 x86_64, pjsip
>            Reporter: Michael Maier
>            Assignee: Unassigned
>
> I did some research on the meaning of transports and what they are used for. I used this documentation [here|https://wiki.asterisk.org/wiki/display/AST/Asterisk+18+Configuration_res_pjsip#Asterisk18Configuration_res_pjsip-endpoint_transport] and [here|https://github.com/asterisk/asterisk/blob/master/configs/samples/pjsip.conf.sample] - the latter list some example transports and states:
> "; You can have more than one of any type of transport, as long as it doesn't
> ; use the same resources (bind address, port, etc) as the others."
> The statement, that there can't be different transports using same bind address and port seems to be wrong as I can define (and use) pretty much transports using the same bindaddr like 0.0.0.0 (you even can omit the port completely if you define a method(?) - I think the port is derived by the standard port of the given method). If you use the port "0", no bind seems to be done (at the beginning) at all (at least you can't see it in netstat).
> You should write something about the usage of a transport when used for a trunk, i.e. an endpoint, which registers itself to an ISP e.g.
> If you do not specify any transport for this trunk, the first appropriate transport would be used automatically according documentation (in FreePBX, it's impossible to not define any transport for a trunk - you always have to define one).
> You should write, that all trunks e.g. are using the same connection to the ISP, if you register more than one number (yes, that's not seldom), if they are using the same transport. If you want asterisk to use another local port for the n-th trunk configuration to the same ISP (and therefore an own connection per registered number), you have to define n equal transports, which only differ in their name (there are ISPs which can't handle correctly n registered numbers using the same connection and I doubt asterisk can - because I faced strange timeout problems under certain conditions e.g.).
> Could you please adjust the existing documentation to clarify those points? Especially, what exactly happens if you use port 0.
> (The asterisk versions I mentioned above are just examples because I must set some version)



--
This message was sent by Atlassian JIRA
(v6.2#6252)