[Asterisk-Users] Context mix-up
I have two fwd accounts, and I want them to behave differently. It took me a while to figure out why it wouldn't work, but finally I realized that the last definition in sip.conf is the one that steals the show. Simplified, I have this: register = account1:[EMAIL PROTECTED]/88 register = account2:[EMAIL PROTECTED]/87 [fwdaccount1] context = context1 host=fwd.pulver.com . [fwdaccount2] context = context2 host=fwd.pulver.com . In extensions.conf: [context1] exten = 88,1,NoOp(Testing context1) [context2] exten = 87,1,NoOp(Testing context2) What happens in my case, is that every call goes into the context defined _last_ in sip.conf. So any call to account1 will be branded context2 and fail, because extension 88 is not defined in context2. Calls to account2 will work ok. If the two definitions in sip.conf trade places, the whole thing will work the other way around. [fwdaccount2] context = context2 host=fwd.pulver.com . [fwdaccount1] context = context1 host=fwd.pulver.com . Calls to either account will be branded context1 and fail if account 2 was called. If this is how it is supposed to work, the workaround must be to let both accounts enter the same context and differentiate their behavior based on the extension dialed. Not difficult, but I thought it would be possible to let them have different contexts from the start. Thor ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Context mix-up
Help, my messages to the list disappear. I will post a follow-up to this message in just a sec. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Context mix-up
I have two fwd accounts, and I want them to behave differently. It took me a while to figure out why it wouldn't work, but finally I realized that the last definition in sip.conf is the one that steals the show. Simplified, I have this: register = account1:[EMAIL PROTECTED]/88 register = account2:[EMAIL PROTECTED]/87 [fwdaccount1] context = context1 host=fwd.pulver.com . [fwdaccount2] context = context2 host=fwd.pulver.com . In extensions.conf: [context1] exten = 88,1,NoOp(Testing context1) [context2] exten = 87,1,NoOp(Testing context2) What happens in my case, is that every call goes into the context defined _last_ in sip.conf. So any call to account1 will be branded context2 and fail, because extension 88 is not defined in context2. Calls to account2 will work ok. If the two definitions in sip.conf trade places, the whole thing will work the other way around. [fwdaccount2] context = context2 host=fwd.pulver.com . [fwdaccount1] context = context1 host=fwd.pulver.com . Calls to either account will be branded context1 and fail if account 2 was called. If this is how it is supposed to work, the workaround must be to let both accounts enter the same context and differentiate their behavior based on the extension dialed. Not difficult, but I thought it would be possible to let them have different contexts from the start. Thor ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Context mix-up
Thor: All your messages seem to be making it to the list ok - I've seen this email at least 3 times. Are you perhaps blocking the list somewhere in your anti-spam setup? Roger Thor Atle Rustad wrote: I have two fwd accounts, and I want them to behave differently. It took me a while to figure out why it wouldn't work, but finally I realized that the last definition in sip.conf is the one that steals the show. Simplified, I have this: register = account1:[EMAIL PROTECTED]/88 register = account2:[EMAIL PROTECTED]/87 [fwdaccount1] context = context1 host=fwd.pulver.com . [fwdaccount2] context = context2 host=fwd.pulver.com . In extensions.conf: [context1] exten = 88,1,NoOp(Testing context1) [context2] exten = 87,1,NoOp(Testing context2) What happens in my case, is that every call goes into the context defined _last_ in sip.conf. So any call to account1 will be branded context2 and fail, because extension 88 is not defined in context2. Calls to account2 will work ok. If the two definitions in sip.conf trade places, the whole thing will work the other way around. [fwdaccount2] context = context2 host=fwd.pulver.com . [fwdaccount1] context = context1 host=fwd.pulver.com . Calls to either account will be branded context1 and fail if account 2 was called. If this is how it is supposed to work, the workaround must be to let both accounts enter the same context and differentiate their behavior based on the extension dialed. Not difficult, but I thought it would be possible to let them have different contexts from the start. Thor ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Roger Hill 07739 707 180 Perseverance is the hard work you do after you get tired of doing the hard work you already did. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Context mix-up
I have now received the messages I sent today, this seems to have happened after I updated some settings at digium.com's list server. Why that would matter, I don't know. According to the list server, I had a bounce score of 1 (of 5). Therefore I changed a setting or two just let the server I still exist. Maybe the fault lies within gmail.com? Still, the two I sent yesterday remain in cyberspace. I have been able to post follow-ups all along, but yesterday, when creating a new thread, I didn't see it, nor any replies. Thor ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Context mix-up
I have two fwd accounts, and I want them to behave differently. It
took me a while to figure out why it wouldn't work, but finally I
realized that the last definition in sip.conf is the one that steals
the show.
Its a common issue with sip since it matches on ip address, etc. Check
the archives on 'how' sip finds a matching sip.conf entry. Change your
fwd accounts to iax and you will have more control.
In my case with fwd #61890, incoming calls include the fwd number, so
extensions.conf entries like this:
exten = 61890,1,NoOp,${CALLERID}
exten = 61890,2,Goto(bus-ivr-main|s|1)
exten = 61890,3,Hangup
work just fine. Your second number would simply have a different
exten = statement.
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Context mix-up
I have now received the messages I sent today, this seems to have happened after I updated some settings at digium.com's list server. Why that would matter, I don't know. According to the list server, I had a bounce score of 1 (of 5). Therefore I changed a setting or two just let the server I still exist. Maybe the fault lies within gmail.com? Still, the two I sent yesterday remain in cyberspace. I have been able to post follow-ups all along, but yesterday, when creating a new thread, I didn't see it, nor any replies. I had the same problem which resulted from our broadband connection being down for a couple of days over Thanksgiving. Apparently an undeliverable email from the list server triggers a 'stop' function, and revisiting the list server page returns the sending of email again. Not a problem for me as long as one is aware of the functionality. (Kind of hard to miss it though with 200+ emails per day.) ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Context mix-up
I have two fwd accounts, and I want them to behave differently. It took me a while to figure out why it wouldn't work, but finally I realized that the last definition in sip.conf is the one that steals the show. Simplified, I have this: register = account1:[EMAIL PROTECTED]/88 register = account2:[EMAIL PROTECTED]/87 [fwdaccount1] context = context1 host=fwd.pulver.com . [fwdaccount2] context = context2 host=fwd.pulver.com . In extensions.conf: [context1] exten = 88,1,NoOp(Testing context1) [context2] exten = 87,1,NoOp(Testing context2) What happens in my case, is that every call goes into the context defined _last_ in sip.conf. So any call to account1 will be branded context2 and fail, because extension 88 is not defined in context2. Calls to account2 will work ok. If the two definitions in sip.conf trade places, the whole thing will work the other way around. [fwdaccount2] context = context2 host=fwd.pulver.com . [fwdaccount1] context = context1 host=fwd.pulver.com . Calls to either account will be branded context1 and fail if account 2 was called. If this is how it is supposed to work, the workaround must be to let both accounts enter the same context and differentiate their behavior based on the extension dialed. Not difficult, but I thought it would be possible to let them have different contexts from the start. Thor ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
