| Summary: | ASTERISK-20950: Add configuration support to the new SIP channel driver for the 'standard' transports | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 NewSIP |
| Date Opened: | 2013-01-18 09:23:07.000-0600 | Date Closed: | 2013-02-13 14:49:22.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_pjsip |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Using the [SIP Data Access Layer Objects|https://wiki.asterisk.org/wiki/display/AST/SIP+Data+Access+Layer+Objects] page as a guide, create transports configuration objects for the following:
* General transport object * TLS configuration object Do this for the UDP, TCP, and TLS transports. Since WebSockets are not supported by pjproject out of the box, that will be a separate effort. Add the necessary hooks so that, when a SIP session is created for a particular endpoint that has a defined transport, the correct transport is chosen for the SIP session by pjproject. | ||
| Comments: | |||