Joshua So once a transport is pulled from the transports table in realtime during asterisk startup it can't get any updates? Can a new transport be added to the table and the associated endpoints be updated to use the new transport, or are transport types only read at startup across the board? Thanks Bryant ---------------------------------------- From: "Joshua Colp" <jcolp at digium.com> Sent: Tuesday, January 26, 2016 8:10 AM To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com> Subject: Re: [asterisk-users] PJSIP Stun/ICE Bryant Zimmerman wrote:> Joshua > Since there is no automated way currently built in to update the > external signaling and media address information. > Does the realtime pjsip support having the transport contexts section > being pulled from a database table? > I was thinking a cron script updating the table and forcing a reload > each time an IP address changed might a workable solution.No, once loaded the transports can not be changed. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20160126/55b123dd/attachment.html>
Bryant Zimmerman wrote:> Joshua > So once a transport is pulled from the transports table in realtime > during asterisk startup it can't get any updates? > Can a new transport be added to the table and the associated endpoints > be updated to use the new transport, or are transport types only read at > startup across the board?Transports can only be loaded at startup. This stems from PJSIP not being dynamic with transports (it doesn't like its environment changed to that degree while in use). I'm afraid if your IP changes you'd have to restart Asterisk when you are using PJSIP. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org
Bryant, I have the same problem with dynamic public IPs and PJSIP. What is your idea to solve the problem? My suggestion would be to write a script that monitors the change, pjsip.transports.conf updated and Asterisk restarts? Daniel> Am 26.01.2016 um 14:21 schrieb Joshua Colp <jcolp at digium.com>: > > Bryant Zimmerman wrote: >> Joshua >> So once a transport is pulled from the transports table in realtime >> during asterisk startup it can't get any updates? >> Can a new transport be added to the table and the associated endpoints >> be updated to use the new transport, or are transport types only read at >> startup across the board? > > Transports can only be loaded at startup. This stems from PJSIP not being dynamic with transports (it doesn't like its environment changed to that degree while in use). I'm afraid if your IP changes you'd have to restart Asterisk when you are using PJSIP. > > -- > Joshua Colp > Digium, Inc. | Senior Software Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - US > Check us out at: www.digium.com & www.asterisk.org > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3579 bytes Desc: not available URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20160126/e3d59cc0/attachment.bin>
>>>>> "JC" == Joshua Colp <jcolp at digium.com> writes:JC> This stems from PJSIP not being dynamic with transports (it JC> doesn't like its environment changed to that degree while JC> in use). I'm afraid if your IP changes you'd have to restart JC> Asterisk when you are using PJSIP. Wow. I say this having voted for pjsip over the listed alternatives back when the plan to depricate chan_sip was first floated: That should have excluded pj from the options. Which of course means there were no reasonable options. Can ari get around that bug? Lack of full support for traversing nat makes pjsip worthless for a large number of users. And the whole point of realtime is to have all of the rt config fully dymanic. If ari cannot avoid that limitation, chan_sip should get full ongoing maintainance until pjsip is fixed. -JimC -- James Cloos <cloos at jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6