Skip to content

Conversation

wosrediinanatour
Copy link

The account configuration AccountSipConfig::transportId and Account::setTransport() was not mentioned.

The account configuration `AccountSipConfig::transportId`
and `Account::setTransport()` was not mentioned.
within the request path of the call).
- Configure the transport of the accounts to have explicit control
(:cpp:any:`AccountSipConfig::transportId`/:cpp:any:`Account::setTransport()`
or :cpp:any:`pjsua_acc_config::transport_id`/:cpp:any:`pjsua_acc_set_transport()`).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually the account's transport binding is for different purposes (e.g: selecting IP version or network interface) and cannot be used for specifying transport type for sending a SIP request. The transport type is specified in the SIP request message itself (e.g: via target URI or proxy/route) as described in the docs. So if you send a request using transport type that is different to the binding (e.g: account is bound to UDP while request specifies a TCP target), the request will fail to send.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. Thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants