Re: Issue with PJSIP contacts being "unavailable"
"Joshua C. Colp" <[email protected]>
| Newsgroups | gmane.comp.telephony.pbx.asterisk.devel |
|---|---|
| Message-ID | <CAM0A2Z2-sQUnC1CVJ-qQQMsg3eP9dK+Px2bfmLBAor+TmnHeiQ@mail.gmail.com> |
On Tue, Jun 27, 2023 at 7:33 PM <[email protected]> wrote: <snip> > Thanks - just to clarify, if such a connection *isn't* found, this won't > help me right now? It would still use the default transport even with > rewrite_contact=yes? > If the transport goes down in that scenario, then the Contact should get removed because it is an ephemeral port and you can't establish an outbound connection to it. > > In that case, I'm thinking the new option would add on to this by > extending that behavior to if there isn't an active connection and it > needs to set up a new one. Basically "use the contact to determine the > transport, unconditionally" is essentially what it would do. > The scenario where this would only work is if rewrite_contact is set to no, and a Contact is bound from a REGISTER. > > I guess for devices that don't register, you wouldn't necessarily have a > contact so maybe that's why this isn't done all the time? But those are > probably the cases where specifying a transport explicitly would > probably make more sense anyways, and I'm not concerned about those, > only things that register and as such a contact would always be available. > -- Joshua C. Colp Asterisk Project Lead Sangoma Technologies Check us out at www.sangoma.com and www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev