Routing li1 Calls Between obi212 and obi202 Devices
dboling:
Quote from: azrobert on September 01, 2018, 09:11:33 am
I have the same setup (routing line calls to another device) except I'm using an OBi110 and an OBi200. I tried to reproduce your problem and couldn't get a 404 error. Your devices have the same subnet. Are you running them in bridge mode? I don't own an OBi2x2 and not familiar with all the settings, so you might need to get someone else to help.
You can get it to work over the OBiTalk network until you fix this.
## OBI212 Config
Physical Interfaces>LINE Port
InboundCallRoute: ph,pp(510111111)
Replace 510111111 with the OBi number of the OBi202
## OBI202 Config
Voice Services>OBiTalk Service
InboundCallRoute: ph
This is the default, but the setup process might add code to send calls to the Auto Attendant.
I think the problem is with the OBI202. In order for the OBI212 to connect to it must have and open port to connect to. I'm not sure if it's UDP or TCP or if the OPI202 has firewall rules for each terminal. My first port scan was with fing which I don't trust. Currently I'm running a full UDP scan from the server using nmap, it's going to take a bit to complete.
[root@athome ~]# nmap -v -sU 192.168.3.61
PORT STATE SERVICE
53/udp open|filtered domain
67/udp open|filtered dhcps
10000/udp open|filtered ndmp
[root@athome ~]# nmap -v -r -sT 192.168.3.61
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
For some reason the OBI202 isn't providing a port.
azrobert:
It's UDP
ServicesProviders>ITSP Profile x SIP ProxyServerTransport: UDP
dboling:
Quote from: azrobert on September 01, 2018, 09:11:33 am
I have the same setup (routing line calls to another device) except I'm using an OBi110 and an OBi200. I tried to reproduce your problem and couldn't get a 404 error. Your devices have the same subnet. Are you running them in bridge mode? I don't own an OBi2x2 and not familiar with all the settings, so you might need to get someone else to help.
You can get it to work over the OBiTalk network until you fix this.
## OBI212 Config
Physical Interfaces>LINE Port
InboundCallRoute: ph,pp(510111111)
This works for a temp fix. I'm guessing it won't work if Internet connection is down ?
Replace 510111111 with the OBi number of the OBi202
## OBI202 Config
Voice Services>OBiTalk Service
InboundCallRoute: ph
This is the default, but the setup process might add code to send calls to the Auto Attendant.
azrobert:
Quote from: dboling on September 01, 2018, 11:41:03 am
This works for a temp fix. I'm guessing it won't work if Internet connection is down ?
It won't work when the internet is down or the OBiTalk network is having problems.
dboling:
Quote from: azrobert on September 01, 2018, 12:33:12 pm
Quote from: dboling on September 01, 2018, 11:41:03 am
This works for a temp fix. I'm guessing it won't work if Internet connection is down ?
It won't work when the internet is down or the OBiTalk network is having problems.
I don't know about you, but I'm tired with trying to get this to work correctly and need to take a break :) .
Either there's a bug in the software or OBI changed something in it's default configs. As a beta tester, maybe OBI will send you a OBI202 and OBI212 for you to test (N/C). I know on my end there is NO ports/IP's that are blocking and requests to the OBI units.
Navigation
[0] Message Index
[#] Next page
[*] Previous page