Page 1 of 1
How to Disable REGISTRATION of xlite
Posted:
Fri Dec 09, 2011 8:58 am
by gmcust3
How to Disable REGISTRATION of xlite over WAN , if my server is on Public(WAN) and also on Lan ?
Posted:
Fri Dec 09, 2011 11:59 am
by gmcust3
I guess Below One should work in sip file :
contactdeny=0.0.0.0/0.0.0.0
contactpermit=192.168.10.0/255.255.255.0
deny=0.0.0.0/0.0.0.0
permit=192.168.10.0/255.255.255.0
But to make it workable, I have to sip-vicidial.conf file under etc/asterisk folder.
But If I modify file, I see another line which says :
; WARNING- THIS FILE IS AUTO-GENERATED BY VICIDIAL, ANY EDITS YOU MAKE WILL BE LOST
How to implement below changes in the sip-vicidial.conf file ?
contactdeny=0.0.0.0/0.0.0.0
contactpermit=192.168.10.0/255.255.255.0
deny=0.0.0.0/0.0.0.0
permit=192.168.10.0/255.255.255.0
template
Posted:
Sun Dec 11, 2011 11:06 pm
by striker
use the template option under admin
select the SIP_generic
under template Contents enter your sip settings
lik
deny=
permit
disallow=
allow=
bla bla
and in the phone select this template for all the sip phones .
Re: How to Disable REGISTRATION of xlite
Posted:
Tue Dec 18, 2012 5:01 am
by gmcust3
- Code: Select all
in the phone select this template for all the sip phones
Where exactly ?
Re: How to Disable REGISTRATION of xlite
Posted:
Tue Dec 18, 2012 5:50 am
by DomeDan
Its under "Admin" -> "Templates"
create a new template with your settings
and for every phone in the phone-settings set that "Template ID"
Re: How to Disable REGISTRATION of xlite
Posted:
Wed Dec 19, 2012 5:48 am
by gmcust3
But my xlite registration in local IP showed 404 error.
Re: How to Disable REGISTRATION of xlite
Posted:
Fri Mar 08, 2013 1:06 am
by gmcust3
When I use
contactdeny=0.0.0.0/0.0.0.0
contactpermit=192.168.10.0/255.255.255.0
deny=0.0.0.0/0.0.0.0
permit=192.168.10.0/255.255.255.0
as template under phone entry.
From Public IP and also from Local IP it shows Registration Error.
Re: How to Disable REGISTRATION of xlite
Posted:
Fri Mar 08, 2013 2:47 am
by DomeDan
What address range do you use on your local network?
Re: How to Disable REGISTRATION of xlite
Posted:
Fri Mar 08, 2013 2:58 am
by gmcust3
192.168.0.1 to 192.168.10.200
Re: How to Disable REGISTRATION of xlite
Posted:
Fri Mar 08, 2013 3:26 am
by DomeDan
ok, then change the allow to:
192.168.0.0/255.255.0.0
that will match 192.168.X.X
Re: How to Disable REGISTRATION of xlite
Posted:
Fri Mar 08, 2013 4:42 am
by gmcust3
Tried :
contactdeny=0.0.0.0/0.0.0.0
contactpermit=192.168.0.0/255.255.255.0
deny=0.0.0.0/0.0.0.0
permit=192.168.0.0/255.255.255.0
But Not working.
Re: How to Disable REGISTRATION of xlite
Posted:
Fri Mar 08, 2013 5:05 am
by DomeDan
you didnt write it right
copy/paste this:
contactdeny=0.0.0.0/0.0.0.0
contactpermit=192.168.0.0/255.255.0.0
deny=0.0.0.0/0.0.0.0
permit=192.168.0.0/255.255.0.0
Re: How to Disable REGISTRATION of xlite
Posted:
Fri Mar 08, 2013 5:59 am
by gmcust3
Tried...
When I tried sip show peers , It NOT showing in the list.
Re: How to Disable REGISTRATION of xlite
Posted:
Fri Mar 08, 2013 6:16 am
by DomeDan
* disable the template, do a reload in asterisk
* verify that the phone can register check in the asterisk cli what is happening.
* and post it here
* enable the template, do a reload in asterisk
* verify that the phone got a ip address like 192.168.X.X
* try to let the phone register and check in the asterisk cli what is happening.
* if there is any activity in the cli then post it here
* if not then run ngrep-sip and let the phone register again
* and post the output here
* post the content of /etc/asterisk/sip-vicidial.conf for a phone in question
Re: How to Disable REGISTRATION of xlite
Posted:
Fri Mar 08, 2013 3:01 pm
by williamconley
1) did you actually use 255.255.0.0 (not 255.255.255.0)? That seems like it may have been lost in the conversation above
2) not showing in sip peers is not in any way related to permit or deny. If it is not showing then it isn't in the sip-vicidial.conf or sip-vicidial.conf has not loaded into asterisk. Find out which.
3) 2.2.1? Really? Why don't you upgrade
?
Re: How to Disable REGISTRATION of xlite
Posted:
Sat Mar 09, 2013 1:05 am
by gmcust3
Using Kernel Version 2.6.18-238.9.1.el5.goPAE (SMP)
Re: How to Disable REGISTRATION of xlite
Posted:
Tue Mar 12, 2013 12:37 am
by gmcust3
Still Not Resolved.
Re: How to Disable REGISTRATION of xlite
Posted:
Tue Mar 12, 2013 3:43 am
by DomeDan
try to work with us here, did you write 255.255.255.0 or 255.255.0.0?
Re: How to Disable REGISTRATION of xlite
Posted:
Wed Mar 13, 2013 1:36 am
by gmcust3
I tried :
contactdeny=0.0.0.0/0.0.0.0
contactpermit=192.168.0.0/255.255.0.0
deny=0.0.0.0/0.0.0.0
permit=192.168.0.0/255.255.0.0
I want my Phone to get Register from Local IP but Not from Public IP.
If I use above template, Its NOT getting registered from either IP.
Re: How to Disable REGISTRATION of xlite
Posted:
Wed Mar 13, 2013 3:54 am
by DomeDan
ok, a wise man once wrote this:
DomeDan wrote:* disable the template, do a reload in asterisk
* verify that the phone can register check in the asterisk cli what is happening.
* and post it here
* enable the template, do a reload in asterisk
* verify that the phone got a ip address like 192.168.X.X
* try to let the phone register and check in the asterisk cli what is happening.
* if there is any activity in the cli then post it here
* if not then run ngrep-sip and let the phone register again
* and post the output here
* post the content of /etc/asterisk/sip-vicidial.conf for a phone in question
try that
Re: How to Disable REGISTRATION of xlite
Posted:
Wed Mar 13, 2013 5:02 am
by gmcust3
[cc131]
username=cc131
secret=test
accountcode=cc131
callerid="station 131" <0000000000>
mailbox=131
contactdeny=0.0.0.0/0.0.0.0
contactpermit=192.168.0.0/255.255.0.0
deny=0.0.0.0/0.0.0.0
permit=192.168.0.0/255.255.0.0
Re: How to Disable REGISTRATION of xlite
Posted:
Wed Mar 13, 2013 5:41 am
by DomeDan
awesome
keep it comming!
asterisk cli and ngrep-sip when the phone tries to register is what i would like to see now
Re: How to Disable REGISTRATION of xlite
Posted:
Wed Mar 13, 2013 5:48 am
by gmcust3
30 agent dialing now... So, CLI is running like anything