search for: parameternam

..........> <Hash....> <Status> <RTT(ms)..> ========================================================================================= Aor: pbx-node-1 0 Contact: pbx-node-1/sip:myurl:5060 771bf6a7d4 Created 0.000 ParameterName : ParameterValue =================================================== authenticate_qualify : false contact : sip:myurl:5060 default_expiration : 3600 mailboxes : max_contacts : 0 maximum_expiration : 7200 minimum_expiration : 60 outbound_proxy...

Hello, How should I configure Asterisk (13.7.0) to get persistently PJSIP SIP messages in a log file and not in console ? I would expect adding "debug=yes" in pjsip.conf to produce the same output as "pjsip set logger on". Am I understanding correctly ? Best regards -------------- next part -------------- An HTML attachment was scrubbed... URL:

..........> <Hash....> <Status> <RTT(ms)..> ========================================================================================= Aor: pbx-node-1 0 Contact: pbx-node-1/sip:myurl:5060 771bf6a7d4 Created 0.000 ParameterName : ParameterValue =================================================== authenticate_qualify : false contact : sip:myurl:5060 default_expiration : 3600 mailboxes : max_contacts : 0 maximum_expiration : 7200 minimum_expiration : 60 outbound_proxy...

Rui, I have created D64474 to change comments explicitly stating the parameter names for constants ( /*parameterName=*/<constant> ). I did this by hand to match the new variable names. Do you know if there would be a way to update these comments with a tool similar to what you used to change these names? Perhaps it would be much more difficult, I'm guessing clang's AST doesn't have a way to des...

...ge > these names for doxygen comments? > > On Wed, Jul 10, 2019 at 7:12 AM Alex Brachet-Mialot < > alexbrachetmialot at gmail.com> wrote: > >> Rui, >> >> I have created D64474 to change comments explicitly stating the parameter >> names for constants ( /*parameterName=*/<constant> ). I did this by hand to >> match the new variable names. Do you know if there would be a way to update >> these comments with a tool similar to what you used to change these names? >> Perhaps it would be much more difficult, I'm guessing clang's AST do...

Hi all, I have an issue with asterisk 13 and pjsip. I guess it is somehow Firewall related, but I'm unsure. A registration to Sipgate is established successfully: <Registration/ServerURI..............................> <Auth..........> <Status.......> ==========================================================================================

...ransport-tls Transport: <TransportId........> <Type> <cos> <tos> <BindAddress....................> ========================================================================================= Transport: transport-tls tls 0 0 0.0.0.0:5061 ParameterName : ParameterValue ====================================================== async_operations : 1 bind : 0.0.0.0:5061 ca_list_file : cert_file : /etc/asterisk/sslcert.pem cipher : cos...

...s for doxygen comments? >> >> On Wed, Jul 10, 2019 at 7:12 AM Alex Brachet-Mialot >> <alexbrachetmialot at gmail.com> wrote: >> >> Rui, >> >> I have created D64474 to change comments explicitly stating the >> parameter names for constants ( /*parameterName=*/<constant> ). I >> did this by hand to match the new variable names. Do you know if >> there would be a way to update these comments with a tool similar to >> what you used to change these names? Perhaps it would be much more >> difficult, I'm guessing clang'...

On 06/05/2017 at 11:30 AM, Joshua Colp wrote: > On Sun, Jun 4, 2017, at 10:40 AM, Michael Maier wrote: >> On 06/04/2017 at 01:41 PM Telium Technical Support wrote: >>> Just a guess (without knowing about your network), but are the two ends >>> points on public networks and visible to one another? If not the reinvite >>> may be passing an internal (nat'ed)

...w registration pjsip_sipgate <Registration/ServerURI..............................> <Auth..........> <Status.......> ========================================================================================== pjsip_sipgate/sip:sipgate.de:5060 pjsip_sipgate Registered ParameterName : ParameterValue ======================================================== auth_rejection_permanent : true client_uri : sip:2636146e0 at sipgate.de:5060 contact_user : 2636146e0 endpoint : expiration : 600 fatal_retry_...

...> >> On Wed, Jul 10, 2019 at 7:12 AM Alex Brachet-Mialot > >> <alexbrachetmialot at gmail.com> wrote: > >> > >> Rui, > >> > >> I have created D64474 to change comments explicitly stating the > >> parameter names for constants ( /*parameterName=*/<constant> ). I > >> did this by hand to match the new variable names. Do you know if > >> there would be a way to update these comments with a tool similar to > >> what you used to change these names? Perhaps it would be much more > >> difficult, I'...

Hi Rui, I’m totally positive on switching to camelCase convention. In fact I have been always uncomfortable with the current naming approach. My only suggestion/concern is that we should provide a transition path not only for the trunk code in the repository, but for eventual out-of-trunk code with implementations of custom architectures. I have currently a custom backend implemented on top of