Re: [asterisk-users] SIP trunks going to the wrong context

In article <1513290358.2926.4.ca...@linuxista.com>, Frank Vanoni wrote: > I don't know if it applies to your problem, but I also had some > troubles with multiple account on same SIP provider.  > Here what works for me: > > > In sip.conf: > > > register =>

Re: [asterisk-users] SIP trunks going to the wrong context

I don't know if it applies to your problem, but I also had some troubles with multiple account on same SIP provider.  Here what works for me: In sip.conf: register => 11:qwe...@sip.provider.zz/11 ; Trunk1 register => 22:asd...@sip.provider.zz/22 ; Trunk2 register =>

Re: [asterisk-users] SIP trunks going to the wrong context

In article , Ade Vickers wrote: > Hi all, > > I'm trying to resolve a weird issue with SIP routing. > > I have a number of SIP trunks, from a selection of providers, all of > which are registered in

[asterisk-users] SIP trunks going to the wrong context

Hi all, I'm trying to resolve a weird issue with SIP routing. I have a number of SIP trunks, from a selection of providers, all of which are registered in sip.conf: [general] context=default allowguest=no allowoverlap=no udpbindaddr=0.0.0.0 tcpenable=yes

Re: [asterisk-users] Is it possible to have two endpoints to the same IP address where one uses IP based authentication and the other requires asterisk to register to that system?

On Wed, Dec 13, 2017 at 10:51 AM, Dan Cropp wrote: > Currently using PJSIP. First, they want me to get this working with the > existing PJSIP configuration, but then setup a second box using chan_sip > performing similar work. > > > > For PJSIP… > > I currently have an

Re: [asterisk-users] Rewrite Outgoing Number

asterisk-users-boun...@lists.digium.com wrote on 12/14/2017 09:52:32 AM: > From: "basti" > To: asterisk-users@lists.digium.com > Date: 12/14/2017 09:52 AM > Subject: Re: [asterisk-users] Rewrite Outgoing Number > Sent by: asterisk-users-boun...@lists.digium.com > >

Re: [asterisk-users] General Kernel practices on CentOS

CentOS 7 works well with Asterisk. Install latest CentOS7 with updates install asterisk I am running FreePBX on CentOS 7. Ron On 14/12/2017 10:38 AM, Olivier wrote: Hello, I'm used to install Asterisk on Debian stable platforms. A customer is asking how I would proceed on a CentOS platform.

Re: [asterisk-users] Rewrite Outgoing Number

On 14/12/2017 10:36 AM, basti wrote: On 14.12.2017 16:30, basti wrote: Hello, I am new on asterisk and do some tests on freepbx. I have 2 SIP provider: Provider1: In-/Out- Flatrate, only 1 Number Provider2: Incoming Flatrate, Outgoing Cost depend on destination, 3 numbers These are trunks.

Re: [asterisk-users] Rewrite Outgoing Number

ok thanks for the answer, i will try it. sorry for the question: in which file should it be configured? On 14.12.2017 16:41, kevin.lar...@pioneerballoon.com wrote: > > Kevin Larsen - Systems Analyst - Pioneer Balloon - Ph: 316-688-8208 > > asterisk-users-boun...@lists.digium.com wrote on

Re: [asterisk-users] Explain how to maintain a compiled from source Asterisk instance ?

On Fri, Dec 08, 2017 at 04:08:02PM +0100, Olivier wrote: > Hello, > > When compiling Asterisk from source, the classical ./configure, make and > make install commands are issued. > > > If a vulnerabilty is found within Asterisk code, then Asterisk source code > is patched and depending on what

Re: [asterisk-users] Rewrite Outgoing Number

Kevin Larsen - Systems Analyst - Pioneer Balloon - Ph: 316-688-8208 asterisk-users-boun...@lists.digium.com wrote on 12/14/2017 09:36:06 AM: > From: "basti" > To: asterisk-users@lists.digium.com > Date: 12/14/2017 09:36 AM > Subject: Re: [asterisk-users] Rewrite

[asterisk-users] General Kernel practices on CentOS

Hello, I'm used to install Asterisk on Debian stable platforms. A customer is asking how I would proceed on a CentOS platform. After a short research (see [1] as an example), I'm wondering what are general kernel practices on CentOS regarding Asterisk and when targeting stability: - Is it

Re: [asterisk-users] Rewrite Outgoing Number

On 14.12.2017 16:30, basti wrote: Hello, I am new on asterisk and do some tests on freepbx. I have 2 SIP provider: Provider1: In-/Out- Flatrate, only 1 Number Provider2: Incoming Flatrate, Outgoing Cost depend on destination, 3 numbers On Asterisk site i have 3 phones (branch ??, don't know how

[asterisk-users] Rewrite Outgoing Number

Hello, I am new on asterisk and do some tests on freepbx. I have 2 SIP provider: Provider1: In-/Out- Flatrate, only 1 Number Provider2: Incoming Flatrate, Outgoing Cost depend on destination, 3 numbers On Asterisk site i have 3 phones (branch ??, don't know how its called in asterisk) Is it

[asterisk-users] Explain HangupCauseClear() and HANGUPCAUSE_KEYS behaviour

Hello, I'm giving HangupCauseClear() a try on a Debian Stretch / Asterisk 13.18.3 stack. My dialplan is: exten = 1234,1,Set(CHANNEL(hangup-handler-push)=myhandler,s,1) same = n,Dial(SIP/foo/1234) same = n,Gosub(myhandler,s,1) same = n,HangupCauseClear() same = n,Dial(SIP/bar/1234) [myhandler]

Re: [asterisk-users] Can't install package asterisk-dbgsym on Stretch

On Fri, Dec 08, 2017 at 06:11:47PM +0100, Olivier wrote: > Hello, > > On a fresh Debian Stretch setup, I have: > $ cat /etc/apt/sources.list.d//dbgsym.list > deb http://debug.mirrors.debian.org/debian-debug/ stretch-debug main > > # apt-get update > ... > # apt-get install asterisk gdb > > #

Re: [asterisk-users] [OT] Overview of Homer installation on Debian Stretch

1. The simplest option would be to run the Docker multicontainer-setup as described on the HOMER wiki here: https://github.com/sipcapture/homer/wiki/Docker-Install 2. Sure it is. Just edit your homer configuration to reflect the remote DB server 3. If you really want to learn and

Re: [asterisk-users] PJSIP OPTIONS

On Wed, Dec 13, 2017, at 09:38 PM, volga...@networklab.ca wrote: > Hello Joshua, > What will be example of endpoint configuration that not require > authentication from specific ip ? An endpoint doesn't know about an IP address. The identify I previously mentioned is what associates the request