Backstory:
We purchased this unit in November or so. We upgraded IPO to 9.1.5 with the cards being recognized without any issues (FXO/FXS all there). However, we were trying to do a SIP configuration through a voice gateway for SIP carrier services. After a lot of testing, we decided to...
Nevermind. Found the answer. Taken from the SV9100's manual. Good enough for me!
Note that the GCD-CP10 blade must always have a static IP address. This
address is set in Program 10-12-01 : GCD-CP10 Network Setup – IP Address
(default: 192.168.0.10).
Hey guys. Got a weird question here. Customer is requesting the PBX and VM's IP to grab an IP from their DHCP server through MAC filtering instead of statically assigning the IPs of these two interfaces. I don't remember ever seeing an option for this. Can someone tell me if this is possible or not?
Found an older thread where it states SIP prefix/analog prefix/PRI prefix is used in the same way so I'm going to assume that what I have in the first post is correct
After some digging, I was able to find some definitions from the help menu for SIP prefixes
However, the definition under analog lines for prefixes is somewhat different. I wonder if functionality is the same. If anything, I'd have to do a live test to confirm...
Hey guys. I'm looking to add prefixes to one of our PBX's for redialing through call history. Usually on the POTS line on IPO, we would just put "91" (9 being the access code to dial outwards) and call it a day. However, under SIP lines, there are three different prefixes ("Prefix", "National...
Looks like we're still having echoing issues with both options set to off. Impedance test when not checked on automatic still puts us at 600 (duh, US default). Other than that I don't see why its still echoing. I got a few traces of echoing and we'll send that towards Avaya and see what they...
Hey guys. Hoping that some of you may have seen this problem before. We've deployed quite a number of IPO 500s now (all 9.0 and up, mostly using 9608 handsets). All our customers who are using SIP or PRI seem to have no issues what so ever but a lot of our customers have issues with POTs...
I'm trying to configure these phone sets to work off of one rj45 jack.
I have the following:
Assuming vlan 11 for data and vlan 17 for voice
Using astericks + freepbx
HP Switch with vlan 11 untagged (native) and vlan 17 tagged
windows dhcp server for both voice and data
I am looking for a...
Right and that is how i have configured it.
ICR goes straight to that group when the particular number is dialed. So far, under the configuration with fallback, it SHOULD work in such that when out of hours, calls go directly to VM.
No overflow just bare configuration as I have stated and...
Wait... but thats what I intended to set it for...
When out of time profile (entered night service), it should go directly to VM and not ring any phone... VM is enabled for this particular group.
But you're saying I have to manually set a button to night service on/off?
From the f1 help...
IPO 500v2 r9.0
From what the f1 help notes say, fallback is suppose to operate within the time profile you created when it is in service. However, once it becomes out of hours, instead of hitting the destination, it automatically operates in night service mode where if I do not select anything...
?
Is that not how most pbxs work? Two dhcp servers one for voice/data in general with the voice as tagged and data as untagged so that if you plug a PC in without behind the phone purposes, it will natively grab the data segment for flexibility?
In my case, I have two DHCP servers one for data...
Our latest looks like the following (added the vlan test):
set interface ethernet0/3 dhcp server option custom 242 string "MCIPADD=192.168.42.1,MCPORT=1719,HTTPSRVR=192.168.42.1,L2Q=1,L2QVLAN=100,VLANTEST=0"
Phones still don't grab a dhcp address from the voice dhcp server located on the pbx...
I set this over GUI but this what it looks like under CLI all in one line
set interface ethernet0/3 dhcp server option custom 242 string "MCIPADD=192.168.42.1,MCPORT=1719,HTTPSRVR=192.168.42.1,L2Q=1,L2QVLAN=100"
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.