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

On Thursday, December 14, 2017, 10:05:23 PM, Tony Mountifield (t...@softins.co.uk) wrote: > So I think you really do need to have a single peer section for all sipgate > calls, pointing to one sipgate context in your dialplan that contains all > your various extensions like se2489, sj0151, etc.

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