gmane.comp.telephony.pbx.asterisk.user archive

382 archived articles, newest first (page 3 of 4). Latest articles →

Re: AMI versions
Tue, 11 Jul 2023 15:40:27 -0300
"Joshua C. Colp" <[email protected]> • #293855
Re: AMI versions
Tue, 11 Jul 2023 18:37:29 +0000
"TTT" <[email protected]> • #293854
Re: AMI versions
Tue, 11 Jul 2023 15:57:44 +0000
Sean Bright <[email protected]> • #293853
AMI versions
Tue, 11 Jul 2023 15:54:57 +0000
"TTT" <[email protected]> • #293852
Re: asterisk sees private IP address of a device behind NAT
Tue, 11 Jul 2023 10:18:37 +0200
Antony Stone <[email protected]> • #293851
asterisk sees private IP address of a device behind NAT
Tue, 11 Jul 2023 10:00:22 +0200
Fourhundred Thecat <[email protected]> • #293850
Re: Memory leak
Tue, 11 Jul 2023 06:21:11 +0500
Tahir Almas Dhesi <[email protected]> • #293849
Re: Is there a way to compile app_macro in 16.30.1
Mon, 10 Jul 2023 20:57:50 -0400
[email protected] • #293848
Is there a way to compile app_macro in 16.30.1
Mon, 10 Jul 2023 20:55:03 -0400
"Federico" <[email protected]> • #293847
Re: Memory leak
Sat, 8 Jul 2023 17:48:01 -0400
[email protected] • #293846
Memory leak
Sat, 8 Jul 2023 17:32:27 -0400
"Federico" <[email protected]> • #293845
Re: Asterisk Release 20.3.1
Sat, 8 Jul 2023 09:49:01 +0200
Michael Maier <[email protected]> • #293844
Re: Asterisk Release 20.3.1
Fri, 7 Jul 2023 13:50:04 -1000
Jean-Denis Girard <[email protected]> • #293843
Re: Asterisk Release 20.3.1
Fri, 7 Jul 2023 19:49:00 -0300
"Joshua C. Colp" <[email protected]> • #293842
Re: Asterisk Release 20.3.1
Fri, 7 Jul 2023 11:40:21 -1000
Jean-Denis Girard <[email protected]> • #293841
Asterisk Release 20.3.1
Fri, 07 Jul 2023 20:10:00 +0000
Asterisk Development Team <[email protected]> • #293840
Asterisk Release certified-18.9-cert5
Fri, 07 Jul 2023 19:39:14 +0000
Asterisk Development Team <[email protected]> • #293839
Asterisk Release 19.8.1
Fri, 07 Jul 2023 19:08:25 +0000
Asterisk Development Team <[email protected]> • #293838
Asterisk Release 18.18.1
Fri, 07 Jul 2023 19:07:40 +0000
Asterisk Development Team <[email protected]> • #293837
Asterisk Release 16.30.1
Fri, 07 Jul 2023 19:01:15 +0000
Asterisk Development Team <[email protected]> • #293836
Re: problem getting dahdi-linux to work with kernel 6.1.0-10
Thu, 6 Jul 2023 19:24:43 -0400
[email protected] • #293835
problem getting dahdi-linux to work with kernel 6.1.0-10
Thu, 06 Jul 2023 19:08:18 -0400
John Covici <[email protected]> • #293834
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Thu, 6 Jul 2023 13:46:22 -0400
Michael Ulitskiy <[email protected]> • #293833
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Thu, 6 Jul 2023 14:32:58 -0300
"Joshua C. Colp" <[email protected]> • #293832
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Thu, 6 Jul 2023 13:22:19 -0400
Michael Ulitskiy <[email protected]> • #293831
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Thu, 6 Jul 2023 13:47:04 -0300
"Joshua C. Colp" <[email protected]> • #293830
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Thu, 6 Jul 2023 12:46:24 -0400
Eric Wieling <[email protected]> • #293829
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Thu, 6 Jul 2023 12:42:32 -0400
Michael Ulitskiy <[email protected]> • #293828
Re: Getvar of CHANNEL not working for a couple of items
Thu, 6 Jul 2023 16:23:06 +0000
"TTT" <[email protected]> • #293827
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Wed, 5 Jul 2023 17:22:54 -0400
Michael Ulitskiy <[email protected]> • #293826
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Wed, 5 Jul 2023 16:19:44 -0400
Michael Ulitskiy <[email protected]> • #293825
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Wed, 5 Jul 2023 20:59:35 +0200
Michael Maier <[email protected]> • #293824
Re: Getvar of CHANNEL not working for a couple of items
Wed, 5 Jul 2023 13:01:51 -0300
"Joshua C. Colp" <[email protected]> • #293823
Re: Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Wed, 5 Jul 2023 11:58:10 -0400
Michael Ulitskiy <[email protected]> • #293822
Re: Getvar of CHANNEL not working for a couple of items
Wed, 5 Jul 2023 15:50:25 +0000
"TTT" <[email protected]> • #293821
Re: Getvar of CHANNEL not working for a couple of items
Wed, 5 Jul 2023 05:48:38 -0300
"Joshua C. Colp" <[email protected]> • #293820
Re: Getvar of CHANNEL not working for a couple of items
Tue, 4 Jul 2023 22:51:56 +0000
"TTT" <[email protected]> • #293819
Getvar of CHANNEL not working for a couple of items
Tue, 4 Jul 2023 22:37:09 +0000
"TTT" <[email protected]> • #293818
Re: Get channel variables via ARI/AMI
Mon, 3 Jul 2023 12:32:29 -0300
"Joshua C. Colp" <[email protected]> • #293817
Re: Get channel variables via ARI/AMI
Mon, 3 Jul 2023 15:27:09 +0000
"TTT" <[email protected]> • #293816
Re: Get channel variables via ARI/AMI
Sun, 2 Jul 2023 17:11:39 -0300
"Joshua C. Colp" <[email protected]> • #293815
Re: Get channel variables via ARI/AMI
Sun, 2 Jul 2023 19:39:04 +0000
"TTT" <[email protected]> • #293814
Re: Get channel variables via ARI/AMI
Sun, 2 Jul 2023 16:35:29 -0300
"Joshua C. Colp" <[email protected]> • #293813
Re: Get channel variables via ARI/AMI
Sun, 2 Jul 2023 19:18:11 +0000
"TTT" <[email protected]> • #293812
Re: SetCallerPres command gone
Sat, 01 Jul 2023 16:21:04 +0000
Sean Bright <[email protected]> • #293811
Re: SetCallerPres command gone
Sat, 1 Jul 2023 15:40:27 +0000
"TTT" <[email protected]> • #293810
SetCallerPres command gone
Sat, 1 Jul 2023 15:37:28 +0000
"TTT" <[email protected]> • #293809
Re: AGI script commands
Sat, 1 Jul 2023 01:02:15 -0400
Eric Wieling <[email protected]> • #293808
AGI script commands
Sat, 1 Jul 2023 01:52:08 +0000
"TTT" <[email protected]> • #293807
Setting codec on originating (calling) channel with chan_pjsip (SIP_CODEC_INBOUND equivalent)
Fri, 30 Jun 2023 09:30:07 -0400
Michael Ulitskiy <[email protected]> • #293806
SDP a=ice-ufrag & a=ice-pwd UNSUPPORTED OR FAILED
Wed, 28 Jun 2023 16:14:23 +0200
Jonas Kellens <[email protected]> • #293805
Re: Issue with PJSIP contacts being "unavailable"
Tue, 27 Jun 2023 08:29:12 -0300
"Joshua C. Colp" <[email protected]> • #293804
Issue with PJSIP contacts being "unavailable"
Tue, 27 Jun 2023 07:21:52 -0400
[email protected] • #293803
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 19:50:00 -0500
Jeff LaCoursiere <[email protected]> • #293802
Re: Get channel variables via ARI/AMI
Tue, 27 Jun 2023 00:46:25 +0000
"TTT" <[email protected]> • #293801
Re: Get channel variables via ARI/AMI
Tue, 27 Jun 2023 00:45:00 +0000
"TTT" <[email protected]> • #293800
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 17:21:34 -0500
Jeff LaCoursiere <[email protected]> • #293799
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 17:19:55 -0500
Jeff LaCoursiere <[email protected]> • #293798
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 20:30:55 +0000
"TTT" <[email protected]> • #293797
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 16:12:11 -0400
Eric Wieling <[email protected]> • #293796
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 16:55:43 -0300
"Joshua C. Colp" <[email protected]> • #293795
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 19:35:24 +0000
"TTT" <[email protected]> • #293794
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 16:07:41 -0300
"Joshua C. Colp" <[email protected]> • #293793
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 19:03:43 +0000
"TTT" <[email protected]> • #293792
Re: Get channel variables via ARI/AMI
Mon, 26 Jun 2023 11:00:00 -0300
"Joshua C. Colp" <[email protected]> • #293791
Get channel variables via ARI/AMI
Mon, 26 Jun 2023 13:56:13 +0000
"TTT" <[email protected]> • #293790
Re: Why is WebRTC treated differently from regular SIP in Asterisk
Sat, 24 Jun 2023 05:33:03 -0300
"Joshua C. Colp" <[email protected]> • #293789
Re: WebRTC signaling
Sat, 24 Jun 2023 05:29:50 -0300
"Joshua C. Colp" <[email protected]> • #293788
Why is WebRTC treated differently from regular SIP in Asterisk
Sat, 24 Jun 2023 02:38:34 +0000
"TTT" <[email protected]> • #293787
WebRTC signaling
Sat, 24 Jun 2023 02:18:41 +0000
"TTT" <[email protected]> • #293786
Re: PMS integration
Fri, 23 Jun 2023 10:09:54 -0700
Brandon Shults <[email protected]> • #293785
PMS integration
Thu, 22 Jun 2023 11:44:42 -0500
Jeff LaCoursiere <[email protected]> • #293784
Re: Asterisk not replacing private FROM ip with public IP in INVITE
Wed, 21 Jun 2023 16:10:43 -0300
"Joshua C. Colp" <[email protected]> • #293783
Re: Asterisk not replacing private FROM ip with public IP in INVITE
Wed, 21 Jun 2023 19:07:04 +0000
"TTT" <[email protected]> • #293782
Re: Asterisk not replacing private FROM ip with public IP in INVITE
Wed, 21 Jun 2023 18:58:13 +0000
"TTT" <[email protected]> • #293781
Re: Asterisk not replacing private FROM ip with public IP in INVITE
Wed, 21 Jun 2023 18:56:44 +0000
"TTT" <[email protected]> • #293780
Re: Asterisk not replacing private FROM ip with public IP in INVITE
Wed, 21 Jun 2023 12:52:53 -0600
Carlos Chavez <[email protected]> • #293779
Re: Asterisk not replacing private FROM ip with public IP in INVITE
Wed, 21 Jun 2023 14:46:11 -0400
Eric Wieling <[email protected]> • #293778
Asterisk not replacing private FROM ip with public IP in INVITE
Wed, 21 Jun 2023 18:36:58 +0000
"TTT" <[email protected]> • #293777
Re: PJSIP not performing outbound authentication
Wed, 21 Jun 2023 18:11:04 +0000
"TTT" <[email protected]> • #293776
Re: PJSIP not performing outbound authentication
Wed, 21 Jun 2023 17:55:12 +0000
"TTT" <[email protected]> • #293775
Re: Multiple phones on same PJSIP account
Wed, 21 Jun 2023 17:31:22 +0000
"TTT" <[email protected]> • #293774
Re: PJSIP not performing outbound authentication
Wed, 21 Jun 2023 17:30:59 +0000
"TTT" <[email protected]> • #293773
Re: PJSIP not performing outbound authentication
Wed, 21 Jun 2023 13:31:00 -0400
Henning Follmann <[email protected]> • #293772
Re: PJSIP not performing outbound authentication
Wed, 21 Jun 2023 11:25:43 -0600
Carlos Chavez <[email protected]> • #293771
PJSIP not performing outbound authentication
Wed, 21 Jun 2023 17:19:11 +0000
"TTT" <[email protected]> • #293770
Re: Multiple phones on same PJSIP account
Wed, 21 Jun 2023 10:10:28 -0600
Carlos Chavez <[email protected]> • #293769
Re: Multiple phones on same PJSIP account
Wed, 21 Jun 2023 13:09:57 -0300
"Joshua C. Colp" <[email protected]> • #293768
Re: Multiple phones on same PJSIP account
Wed, 21 Jun 2023 18:02:27 +0200
Antony Stone <[email protected]> • #293767
Re: Multiple phones on same PJSIP account
Wed, 21 Jun 2023 15:52:16 +0000
"TTT" <[email protected]> • #293766
Re: Multiple phones on same PJSIP account
Mon, 19 Jun 2023 16:46:41 +0200
Antony Stone <[email protected]> • #293765
Re: Multiple phones on same PJSIP account
Mon, 19 Jun 2023 14:26:05 +0000
"TTT" <[email protected]> • #293764
Re: Multiple phones on same PJSIP account
Mon, 19 Jun 2023 15:59:41 +0200
Antony Stone <[email protected]> • #293763
Re: Multiple phones on same PJSIP account
Mon, 19 Jun 2023 09:29:42 -0400 (EDT)
Doug Lytle <[email protected]> • #293762
Multiple phones on same PJSIP account
Mon, 19 Jun 2023 13:09:44 +0000
"TTT" <[email protected]> • #293761
Re: Expanding my answering-machine system
Sun, 18 Jun 2023 09:42:26 -0300
"Joshua C. Colp" <[email protected]> • #293760
Re: Expanding my answering-machine system
Sun, 18 Jun 2023 08:22:52 -0400
Steve Matzura <[email protected]> • #293759
Re: Get SIP Call-ID from ARI
Sat, 17 Jun 2023 21:02:51 -0300
"Joshua C. Colp" <[email protected]> • #293758
Re: Get SIP Call-ID from ARI
Sat, 17 Jun 2023 23:40:56 +0000
"TTT" <[email protected]> • #293757
Re: Expanding my answering-machine system
Sat, 17 Jun 2023 20:27:54 -0300
"Joshua C. Colp" <[email protected]> • #293756
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.