Two separate lines on an Obi302 from one SIP provider
bcjackson:
As an experiment, I put in number routing info like: xxx.xxx.xxx.24:5061 and xxx.xxx.xxx.24:5062 in the NexVortex portal for my two numbers respectively.
I then went into the OBi and configured theX_UserAgentPort values of 5061 in SP1 and 5062 in SP2, then tested. I wondered also about the X_KeepAliveServerPort values. They are both still at the default of 5060.
Testing with this trial config. shows outbound calls on phone port 1, and inbound calls to the first number work as desired. Now, however calls involving the second number don't work at all. When I call the second number from my cell, the cellphone reports busy. When I try an outbound call from phone port 2, the call never completes.
drgeoff:
You can also separate calls to your two numbers coming in on SP1 to the two phones by a modification to the SP1 InboundCallRoute. Page 193 of https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf
SP1 InboundCallRoute {>1111111111:ph},{>2222222222:ph2}
substituting the 1111111111 and 2222222222 with the numbers that your ITSP is sending with the calls.
bcjackson:
> SP1 InboundCallRoute {>1111111111:ph},{>2222222222:ph2}
This is looking promising! I created the entry just like above in the form of xxxyyyzzzz, 10 digits as area code, prefix, & suffix. It did not work. It occurred to me then to just put a 1 in front of both of those so the strings as they are now 11 digits each. That seems to get it.
If I had to guess, NexVortex is sending over 11 digits to look at, and things would not match and route unless I had the 1 in front to make those configured strings also 11 digits. Still testing to look for other mis-operations.
Navigation
[0] Message Index
[*] Previous page