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 scanned all 65K+ ports on the OBI202 and found port 5083 to be open/filtered.
The wiki located at https://en.wikipedia.org/wiki/List_of_SIP_response_codes list the SIP error codes and for a 404 error code it says:
404 Not Found
The server has definitive information that the user does not exist at the domain specified in the Request-URI. This status is also returned if the domain in the Request-URI does not match any of the domains handled by the recipient of the request.[1]:§21.4.5
What does the 0 represent in the config sp4(0@192.168.3.61:5083) ?
azrobert:
The zero is data that is passed to the OBi202. This is a requirement of the SIP URI syntax. Calls will pass data and CallerID. You can test for these in the SP4 X_InboundCallRoute.
Format of an inbound route rule:
{ CallerID > data : dest}
> is a separator
If only testing CallerID, separator is not required.
Examples:
{>0:ph}
Data = 0 and any CallerID will be sent to ph
{8005551212>800:ph}
Only CallerID 8005551212 and data 800 sent to ph
{8005551212:ph}
Only CallerID 8005551212 with any data sent to ph
ph or {ph}
All calls sent to ph
dboling:
Quote from: azrobert on September 04, 2018, 09:16:25 am
The zero is data that is passed to the OBi202. This is a requirement of the SIP URI syntax. Calls will pass data and CallerID. You can test for these in the SP4 X_InboundCallRoute.
Format of an inbound route rule:
{ CallerID > data : dest}
> is a separator
If only testing CallerID, separator is not required.
Examples:
{>0:ph}
Data = 0 and any CallerID will be sent to ph
{8005551212>800:ph}
Only CallerID 8005551212 and data 800 sent to ph
{8005551212:ph}
Only CallerID 8005551212 with any data sent to ph
ph or {ph}
All calls sent to ph
sp4(0@192.168.3.61:5083)
OK, I thought the 0 in this line was like user@192.168.3.61:5083 .
The verizon PSTN(LI) port on the 212 does not have caller ID. The line only has dial tone and 911.
Does the line not having callerID make a difference ?
I also do have a WIFI repeater between the OBI202 and the OBI212, when traffic is sent to the servers WIFI via the repeater, it uses the repeaters MAC address.
I've also enabled syslog for better diagnostics .
azrobert:
Is it possible for a test to put both devices on the same router? If you can't because of the Line connection, you can define a speed dial with the same rule to test.
sp4(0@192.168.3.61:5083)
I assume you are running the devices in Bridge mode because they have the same subnet. Is this correct?
dboling:
Quote from: azrobert on September 04, 2018, 01:08:37 pm
Is it possible for a test to put both devices on the same router? If you can't because of the Line connection, you can define a speed dial with the same rule to test.
sp4(0@192.168.3.61:5083)
I assume you are running the devices in Bridge mode because they have the same subnet. Is this correct?
They are both on the same subnet.
wlan0 Link encap:Ethernet HWaddr F8:D1:11:6E:78:38
inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::fad1:11ff:fe6e:7838/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:119458670 errors:0 dropped:0 overruns:0 frame:0
TX packets:150943485 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:94065641101 (87.6 GiB) TX bytes:96751918482 (90.1 GiB)
I tested it a few dozen times today. I ran a tcpdump on wlan0 looking for the OBI212 to try and contact the OBI202 on port 5083. However there was no network traffic coming from the OBI212 on port 5083. I also unpluged the TP-link cpe210 (wireless relay) so both the OBI212 and OBI202 would be connected directly to the same access point, I still had the results.
There must be a bug in the firmware. Is there anyway to get OBI to check this out ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page