Re: [Asterisk-Users] sip register incoming call contexts?
Hello,
I have set up 2 different fwd.pulver.com accounts on my Asterisk. One will ring all my phones through one context, while the other account was set up to fool Nigerian scam artists, and will go directly to a special voicemail (after a few rings to give the impression of ringing a real telephone). I will not even know somebody called until I get the voicemail in the mail.
The first register goes like this:
register => 18469:[EMAIL PROTECTED]/89
while the number that goes directly to the answering machine is as follows:
register => 18336:[EMAIL PROTECTED]/36
Then I match the digits (36 and 89) within the contexts.
89 triggers the [inbound-fwd] context, while 36 triggers [boguscall]:
[boguscall]exten => 36,1,NoOp(This is context boguscall)exten => 36,2,Wait(0)exten => 36,3,Ringingexten => 36,4,Wait(15)exten => 36,5,Voicemail(su36)exten => 36,6,Hangup
[inbound-fwd]
exten => 89,2,Goto(ringall,${EXTEN},1) ; will go to context [ringall]
[ringall] ; Dial all telephones in the houseexten => _X.,1,Dial(SIP/30&SIP/31&SIP/32,35),t
Thor
On 10/10/05, Steve Gladden <[EMAIL PROTECTED]> wrote:
Sorry this is a bit of a newbie question, I've been at this for a fewmonths and still have not quite figured this one out.
I've been able to setup one itsp (incoming calls) (sip account) with aregister line like this:register => nnn:[EMAIL PROTECTED]
-or-register => nnn:[EMAIL PROTECTED]/nnnto come directly into an extension in the dialplanIt seems that this only works with the default context in the dialplan.
I have another sip account from another provider that I would likeall of it's incoming calls to come into the s, extension ofa new context but I have been unable to figure outhow to bring calls from a register line into an alternate context.
It seems that register lines are limited to only being used in thegeneral section of sip.conf and you are limited to one context=statement there.Is there a way to register a second account and have it's calls come into
another context in the dialplan?register lines only seem to work in [general] and it seems like youare limited to only one inbound context here.I would like the two inbound call accounts to be 'isolated' from each other
and not have to come in on the same incoming context in the dialplan.I'd also like to be able to have them have their own contexts with thierown s, (start) extension available.Thanks!Steve
___--Bandwidth and Colocation sponsored by Easynews.com --Asterisk-Users mailing list
Asterisk-Users@lists.digium.comhttp://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation sponsored by Easynews.com --
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] sip register incoming call contexts?
I did try this and did get it to register as this peer. However inbound calls to that number are still coming into the context defined in [general] sip.conf I now have two numbers configured, the new peer as you sugested and my original that just has the register line without an associated peer section. BOTH numbers are still coming into the context defined in [general] THis is fine for the number of which I did not create a peer section for. The other number that I did indeed create a peer section for is not coming into the context that I set within the peer context= I of course am doing a full stop of asterisk and restart/reload for each test. Am I still doing something wrong here? Thanks! Steve >Create a peer with a host= setting that matches the IP of the service >provider's proxy. Set context for this peer. There are several examples >out there, one is http://edvina.net/broadvoice/ >/Olle > Steve Gladden wrote: >> Sorry this is a bit of a newbie question, I've been at this for a few >> months and still have not quite figured this one out. >> >> >> I've been able to setup one itsp (incoming calls) (sip account) with a >> register line like this: >> >> register => nnn:[EMAIL PROTECTED] >> >> -or- >> >> register => nnn:[EMAIL PROTECTED]/nnn >> to come directly into an extension in the dialplan >> >> >> It seems that this only works with the default context in the dialplan. >> >> >> I have another sip account from another provider that I would like >> all of it's incoming calls to come into the s, extension of >> a new context but I have been unable to figure out >> how to bring calls from a register line into an alternate context. > > Create a peer with a host= setting that matches the IP of the service > provider's proxy. Set context for this peer. There are several examples > out there, one is http://edvina.net/broadvoice/ > > /Olle > ___ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] sip register incoming call contexts?
Yep & thanks for the reply, I figured out pretty quickly after one test that the /s did not work. The issue remains that I have been unsuccessful in getting an incoming call to come into any other context other than the one specified in sip.conf [general] section Anything I'm missing here? I have my context that I want incoming calls to come into setup as a peer (as I was instructed here context= inside of peer definition) and I have the context in extensions.conf yet the calls are still landing in the context defined in sip.conf [general] section. What the heck am I missing here? am completely restarting asterisk and reload and sip reload each try just to be sure. Steve > >> OK, I'm starting to get somwhere with this, I'm at least registering >> now.. >> however My inbound calls are still coming into the context defined >> in [general] of sip.conf and not into the context I have defined >> in my peer and extensions.conf >> >> Here is what I have done: >> >> IN sip.conf: >> >> register => nnn:[EMAIL PROTECTED] >> ;also tried register => 2484987171:[EMAIL PROTECTED]/s > > The above statement with /s is not doing what you think it is. That > statement would essentially tell your provider to dial "s" at your > site for incoming calls, and their isn't such a thing as s. > > The register statement without the "s" (as in [EMAIL PROTECTED]) will have > your provider send calls to you with "no digits dialed" by them. > > When a call comes into your machine with "no digits dialed", the > exten => s part of your dialplan will be executed. The "s" extension > is a special case matching no dialed digits. You can't force it by > registering with a /s at the end. > >> exten => s,1,answer >> exten => s,2,wait(1) >> exten => s,3,Playback(testaudiofile) >> exten => s,4,wait(1) >> exten => s,5,hangup > > Verify that your register statement is doing what you expect by > doing a 'sip show registry'. > > > ___ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] sip register incoming call contexts?
> OK, I'm starting to get somwhere with this, I'm at least registering now.. > however My inbound calls are still coming into the context defined > in [general] of sip.conf and not into the context I have defined > in my peer and extensions.conf > > Here is what I have done: > > IN sip.conf: > > register => nnn:[EMAIL PROTECTED] > ;also tried register => 2484987171:[EMAIL PROTECTED]/s The above statement with /s is not doing what you think it is. That statement would essentially tell your provider to dial "s" at your site for incoming calls, and their isn't such a thing as s. The register statement without the "s" (as in [EMAIL PROTECTED]) will have your provider send calls to you with "no digits dialed" by them. When a call comes into your machine with "no digits dialed", the exten => s part of your dialplan will be executed. The "s" extension is a special case matching no dialed digits. You can't force it by registering with a /s at the end. > exten => s,1,answer > exten => s,2,wait(1) > exten => s,3,Playback(testaudiofile) > exten => s,4,wait(1) > exten => s,5,hangup Verify that your register statement is doing what you expect by doing a 'sip show registry'. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] sip register incoming call contexts?
OK, I'm starting to get somwhere with this, I'm at least registering now.. however My inbound calls are still coming into the context defined in [general] of sip.conf and not into the context I have defined in my peer and extensions.conf Here is what I have done: IN sip.conf: register => nnn:[EMAIL PROTECTED] ;also tried register => 2484987171:[EMAIL PROTECTED]/s [ptest] type=peer ;Enter your closest proxy server host=sip.myprovider.net fromdomain=sip.myprovider.net fromuser=nnn secret=:ppp context=incoming2test ;Disable canreinvite if you are behind a NAT canreinvite=no ;Don't try to authenticate on incoming calls insecure=very nat=yes In extensions.conf: [incoming2test] exten => s,1,answer exten => s,2,wait(1) exten => s,3,Playback(testaudiofile) exten => s,4,wait(1) exten => s,5,hangup ; It never makes it into here but gets grabbed by s, defined in [general] section of sip.conf Any ideas?? Thanks! Steve -- > Long list of questions to follow: > > Short version: > > Does the register line mate to a peer or is a register line totally > unrelated to a peer that is defined? > > When using a register line does it have to refer to actual hostnames? > or can you refer to the peer name in the register line instead > of an actual hostname/IP > > like this: register => :@peername/ > > [peername] ; where peername does NOT = a hostname or ip address > > - > > > Long version, > > > > Thanks, I have actually tried this and am still confused. > Please bear with me... > > Also I was unclear on my first message and did not state that I also need > to have a few seperate incoming contexts work from the same provider > as well as two different providers. > >>From the link you provided the confusion starts wit hthe very first line: > It reads, > > "register => @sip.broadvoice.com:: id>@sip.broadvoice.com/" > > I'm used to: register => > @sip.broadvoice.com:password/ > > This example has the "@sip.broadvoice.com:password/" > actually iterrated twice like: > > "@sip.broadvoice.com:: id>@sip.broadvoice.com/" > > (the same thing twice with a colon ":" in the middle. > Is this an error? > > Next: > > You suggest to create a peer with the context= to what I need. > > This brings me back to the same problem of the > [peer] name of [provider.net] > > I don't think I can make several peers called [my.provider.net] > > If I do.. register line will not know which one to use > as they would all be called [my.provider.net] > > Do I need to make several different names and then do some tricks > in DNS to make the different hostnames resolve to the same IP > of my provider that I need? > > Please remember I am also trying to get several accounts from the same > provider/IP to come into their own contexts. as well as an account or two > from another provider. > > I get your point on what to do but I still do not undertand how to make > several seperate peers that use the same IP/host yet bring their calls > into separate contexts. > > The example shows using your providers hostname as the name of the peer. > > I guess you could name them something else but then how does the > register line work with the peer if you do not use the hostname??? > > can you have something like this work? > so far I have tried this and it has been unsuccessful. > > I'm still unclear as to if the registerline needs to use actual > hostnames or can it use the name of the peer and get it from the > peer section? > > And does the name of the peer somehow mate the register line with the peer > if the name of the peer matches the ?hostname? in the register line, > And does it even need to be an actual hostname? > > Can you only use the real hostname in the peer and NOT use the hostname > in the register line? > > I hope you can undertand my confusion on this with all the examples using > hostnames and none of the examples using two incoming contexts with > the same hostname yet different sip accounts. > > Thank you for your help and your patience. > > I think I almost understand this but not quite yet! > > > > register => username:[EMAIL PROTECTED]/extension > > [testpeer] > type=peer > ;Enter your closest proxy server > host=sip.myprovider.com > fromdomain=sip.myprovider.com > fromuser= > secret= > context=my-incoming-context-3 > ;Disable canreinvite if you are behind a NAT > canreinvite=no > ;Don't try to authenticate on incoming calls > insecure=very > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> Steve Gladden wrote: >>> Sorry this is a bit of a newbie question, I've been at this for a few >>> months and still have not quite figured this one out. >>> >>> >>> I've been able to setup one itsp (incoming calls) (sip account) with a >>> register line like this: >>> >>> register => nnn:[EMAIL PROTECTED] >>> >>> -or- >>> >>> register => nnn:[EMAIL PROTECTED]/nn
Re: [Asterisk-Users] sip register incoming call contexts?
Long list of questions to follow: Short version: Does the register line mate to a peer or is a register line totally unrelated to a peer that is defined? When using a register line does it have to refer to actual hostnames? or can you refer to the peer name in the register line instead of an actual hostname/IP like this: register => :@peername/ [peername] ; where peername does NOT = a hostname or ip address - Long version, Thanks, I have actually tried this and am still confused. Please bear with me... Also I was unclear on my first message and did not state that I also need to have a few seperate incoming contexts work from the same provider as well as two different providers. >From the link you provided the confusion starts wit hthe very first line: It reads, "register => @sip.broadvoice.com::@sip.broadvoice.com/" I'm used to: register => @sip.broadvoice.com:password/ This example has the "@sip.broadvoice.com:password/" actually iterrated twice like: "@sip.broadvoice.com::@sip.broadvoice.com/" (the same thing twice with a colon ":" in the middle. Is this an error? Next: You suggest to create a peer with the context= to what I need. This brings me back to the same problem of the [peer] name of [provider.net] I don't think I can make several peers called [my.provider.net] If I do.. register line will not know which one to use as they would all be called [my.provider.net] Do I need to make several different names and then do some tricks in DNS to make the different hostnames resolve to the same IP of my provider that I need? Please remember I am also trying to get several accounts from the same provider/IP to come into their own contexts. as well as an account or two from another provider. I get your point on what to do but I still do not undertand how to make several seperate peers that use the same IP/host yet bring their calls into separate contexts. The example shows using your providers hostname as the name of the peer. I guess you could name them something else but then how does the register line work with the peer if you do not use the hostname??? can you have something like this work? so far I have tried this and it has been unsuccessful. I'm still unclear as to if the registerline needs to use actual hostnames or can it use the name of the peer and get it from the peer section? And does the name of the peer somehow mate the register line with the peer if the name of the peer matches the ?hostname? in the register line, And does it even need to be an actual hostname? Can you only use the real hostname in the peer and NOT use the hostname in the register line? I hope you can undertand my confusion on this with all the examples using hostnames and none of the examples using two incoming contexts with the same hostname yet different sip accounts. Thank you for your help and your patience. I think I almost understand this but not quite yet! register => username:[EMAIL PROTECTED]/extension [testpeer] type=peer ;Enter your closest proxy server host=sip.myprovider.com fromdomain=sip.myprovider.com fromuser= secret= context=my-incoming-context-3 ;Disable canreinvite if you are behind a NAT canreinvite=no ;Don't try to authenticate on incoming calls insecure=very > Steve Gladden wrote: >> Sorry this is a bit of a newbie question, I've been at this for a few >> months and still have not quite figured this one out. >> >> >> I've been able to setup one itsp (incoming calls) (sip account) with a >> register line like this: >> >> register => nnn:[EMAIL PROTECTED] >> >> -or- >> >> register => nnn:[EMAIL PROTECTED]/nnn >> to come directly into an extension in the dialplan >> >> >> It seems that this only works with the default context in the dialplan. >> >> >> I have another sip account from another provider that I would like >> all of it's incoming calls to come into the s, extension of >> a new context but I have been unable to figure out >> how to bring calls from a register line into an alternate context. > > Create a peer with a host= setting that matches the IP of the service > provider's proxy. Set context for this peer. There are several examples > out there, one is http://edvina.net/broadvoice/ > > /Olle > ___ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asteri
Re: [Asterisk-Users] sip register incoming call contexts?
Steve Gladden wrote: > Sorry this is a bit of a newbie question, I've been at this for a few > months and still have not quite figured this one out. > > > I've been able to setup one itsp (incoming calls) (sip account) with a > register line like this: > > register => nnn:[EMAIL PROTECTED] > > -or- > > register => nnn:[EMAIL PROTECTED]/nnn > to come directly into an extension in the dialplan > > > It seems that this only works with the default context in the dialplan. > > > I have another sip account from another provider that I would like > all of it's incoming calls to come into the s, extension of > a new context but I have been unable to figure out > how to bring calls from a register line into an alternate context. Create a peer with a host= setting that matches the IP of the service provider's proxy. Set context for this peer. There are several examples out there, one is http://edvina.net/broadvoice/ /Olle ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] sip register incoming call contexts?
Thank you for your reply and your help. I am still confused here and apologize. To some degree I still do not know what I am doing. We use 2 ITSP's and one of them we have multiple SIP accounts on so I will not be able to do this by IP address. For incoming calls we use a register line in the [general] section of sip.conf like: register => nnn:[EMAIL PROTECTED] We do not have an 'itsp section' for incoming calls. incoming calls come into the context defined in the general section of sip.conf. This is how we learned how to do it from the documentation my understanding is that anything else that involves sections like [itsp-provider out] yada= yada= yada= -or- [itsp-provider-in] yada= yada= yada= Works for permanent non-registered types of connections. I've experimented with trying to put register lines within anything else other than [general] in sip.conf and it does not work and causes a busy signal for an incoming caller. My further under(possibly-mis)undertanding is that with our type of itsp (sip) it requires us to register for incoming calls, and there may be no other way to accept incoming calls from our ITSP, It also seems that register lines only work in the [general] section of sip.conf which only allows me to define one single incoming context is this correct? So the matching by IP address is interesting but confusing and may not apply to what I am trying to do. I will not be able to match by ip with seeveral incoing sip (phone numbers) that I would like to come into their own context but come from the same IP address. Thanks!! Steve > Ok :) > > -- > From: Rich Adamson[SMTP:[EMAIL PROTECTED] > Reply To: Asterisk Users Mailing List - Non-Commercial Discussion > Sent: Monday, October 10, 2005 11:25 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [Asterisk-Users] sip register incoming call contexts? > > >> Sorry this is a bit of a newbie question, I've been at this for a few >> months and still have not quite figured this one out. >> >> >> I've been able to setup one itsp (incoming calls) (sip account) with a >> register line like this: >> >> register => nnn:[EMAIL PROTECTED] >> >> -or- >> >> register => nnn:[EMAIL PROTECTED]/nnn >> to come directly into an extension in the dialplan >> >> >> It seems that this only works with the default context in the dialplan. >> >> >> I have another sip account from another provider that I would like >> all of it's incoming calls to come into the s, extension of >> a new context but I have been unable to figure out >> how to bring calls from a register line into an alternate context. >> >> It seems that register lines are limited to only being used in the >> general section of sip.conf and you are limited to one context= >> statement there. >> >> Is there a way to register a second account and have it's calls come >> into >> another context in the dialplan? >> >> register lines only seem to work in [general] and it seems like you >> are limited to only one inbound context here. >> >> I would like the two inbound call accounts to be 'isolated' from each >> other >> and not have to come in on the same incoming context in the dialplan. >> >> I'd also like to be able to have them have their own contexts with thier >> own s, (start) extension available. > > Try using something like: > deny=0.0.0.0/0.0.0.0 > permit=147.135.8.129/255.255.255.0 > permit=147.135.0.129/255.255.255.0 > permit=147.135.4.128/255.255.255.0 > > in each sip.conf itsp definition to limit which contexts will match. > Obviously, replace the above permit's IP addresses with the correct > ones for your provider. > > > ___ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > > ___ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] sip register incoming call contexts?
Ok :) -- From: Rich Adamson[SMTP:[EMAIL PROTECTED] Reply To: Asterisk Users Mailing List - Non-Commercial Discussion Sent: Monday, October 10, 2005 11:25 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject:Re: [Asterisk-Users] sip register incoming call contexts? > Sorry this is a bit of a newbie question, I've been at this for a few > months and still have not quite figured this one out. > > > I've been able to setup one itsp (incoming calls) (sip account) with a > register line like this: > > register => nnn:[EMAIL PROTECTED] > > -or- > > register => nnn:[EMAIL PROTECTED]/nnn > to come directly into an extension in the dialplan > > > It seems that this only works with the default context in the dialplan. > > > I have another sip account from another provider that I would like > all of it's incoming calls to come into the s, extension of > a new context but I have been unable to figure out > how to bring calls from a register line into an alternate context. > > It seems that register lines are limited to only being used in the > general section of sip.conf and you are limited to one context= > statement there. > > Is there a way to register a second account and have it's calls come into > another context in the dialplan? > > register lines only seem to work in [general] and it seems like you > are limited to only one inbound context here. > > I would like the two inbound call accounts to be 'isolated' from each other > and not have to come in on the same incoming context in the dialplan. > > I'd also like to be able to have them have their own contexts with thier > own s, (start) extension available. Try using something like: deny=0.0.0.0/0.0.0.0 permit=147.135.8.129/255.255.255.0 permit=147.135.0.129/255.255.255.0 permit=147.135.4.128/255.255.255.0 in each sip.conf itsp definition to limit which contexts will match. Obviously, replace the above permit's IP addresses with the correct ones for your provider. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] sip register incoming call contexts?
> Sorry this is a bit of a newbie question, I've been at this for a few > months and still have not quite figured this one out. > > > I've been able to setup one itsp (incoming calls) (sip account) with a > register line like this: > > register => nnn:[EMAIL PROTECTED] > > -or- > > register => nnn:[EMAIL PROTECTED]/nnn > to come directly into an extension in the dialplan > > > It seems that this only works with the default context in the dialplan. > > > I have another sip account from another provider that I would like > all of it's incoming calls to come into the s, extension of > a new context but I have been unable to figure out > how to bring calls from a register line into an alternate context. > > It seems that register lines are limited to only being used in the > general section of sip.conf and you are limited to one context= > statement there. > > Is there a way to register a second account and have it's calls come into > another context in the dialplan? > > register lines only seem to work in [general] and it seems like you > are limited to only one inbound context here. > > I would like the two inbound call accounts to be 'isolated' from each other > and not have to come in on the same incoming context in the dialplan. > > I'd also like to be able to have them have their own contexts with thier > own s, (start) extension available. Try using something like: deny=0.0.0.0/0.0.0.0 permit=147.135.8.129/255.255.255.0 permit=147.135.0.129/255.255.255.0 permit=147.135.4.128/255.255.255.0 in each sip.conf itsp definition to limit which contexts will match. Obviously, replace the above permit's IP addresses with the correct ones for your provider. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] sip register incoming call contexts?
Sorry this is a bit of a newbie question, I've been at this for a few months and still have not quite figured this one out. I've been able to setup one itsp (incoming calls) (sip account) with a register line like this: register => nnn:[EMAIL PROTECTED] -or- register => nnn:[EMAIL PROTECTED]/nnn to come directly into an extension in the dialplan It seems that this only works with the default context in the dialplan. I have another sip account from another provider that I would like all of it's incoming calls to come into the s, extension of a new context but I have been unable to figure out how to bring calls from a register line into an alternate context. It seems that register lines are limited to only being used in the general section of sip.conf and you are limited to one context= statement there. Is there a way to register a second account and have it's calls come into another context in the dialplan? register lines only seem to work in [general] and it seems like you are limited to only one inbound context here. I would like the two inbound call accounts to be 'isolated' from each other and not have to come in on the same incoming context in the dialplan. I'd also like to be able to have them have their own contexts with thier own s, (start) extension available. Thanks! Steve ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
