Hook up POTS to Obi2182 via Obi212?
drgeoff:
Quote from: myobinameisinuse9987 on April 23, 2021, 10:48:32 am
Thank you for the definitive answers ;)
I have another challenge, if you wish.
I'm using the InboundCallRoute now. In my plan, I have to change for 5 locations to ring on incoming 212, including the local ph port on the 212.
You said it was limited to 4.
It made me wonder if I can take one of the 1062 phones that rings from the 212 InboundCallRoute and somehow make it ring that 5th device? Daisy chain, if you will.
Yes, I know that if that device is offline, the chain will break. But I'm dealing with a hybrid of analog and VoIP, customer choice and 2yr landline contract.
I can easily do 5 ring locations from Anveo with any VoIP lines, but these analogs...
Thanks!
The limit of four is in the first of the Notes at the bottom of page 193 of https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf. I have never verified this so you might want to try five - perhaps the newer 2xx series OBis are not as processor bound as the 1x0 devices were. If five does not work I see no reason why the daisy chain method would not.
Note that you probably need to up the "MaxSessions" from the default 2 in the 212's Obitalk Service, Calling Features.
myobinameisinuse9987:
Quote from: drgeoff on April 23, 2021, 12:36:57 pm
The limit of four is in the first of the Notes at the bottom of page 193 of https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf. I have never verified this so you might want to try five - perhaps the newer 2xx series OBis are not as processor bound as the 1x0 devices were. If five does not work I see no reason why the daisy chain method would not.
Note that you probably need to up the "MaxSessions" from the default 2 in the 212's Obitalk Service, Calling Features.
I'll take a look at that section in the AdminGuide, thanks for the link. I didn't realize the Notes sections were for "reading" LOL. This is the guide where I found the 'PP' syntax in previous posts.
What would you recommend for MaxSessions? I haven't come across any criteria yet, or how to figure it out. Will this be affected by OUTBOUND calls from the 1062's that I plan to allow to dial out on the 212 ?
As I understand it, setup Trunk on 212 Li interface, then pass from 1062 to the 212. From what I understand, this is to require password to prevent unauthorized usage of Line interface on 212 (presumably from an errant Transfer from a user?)
I saw the suggestions early in this thread but haven't tried and tested it yet. I plan to test tonight/tomorrow with a 212 and 2182 I have here.
Fyi- YES, you can use FXS port of OBi202 as FXO line in on OBi212, although any calls passing there come up RESTRICTED. Perhaps due to GV being on that line?
Again, thank you for all the help.
(BTW, nice syntax help in that section of the guide, too)
drgeoff:
If you will be forking to four other OBis using the OBiTALK service then I would set MaxSessions to 4. This is only relevant to calls coming into the 212's LINE port (and ringing its PHONE port and being forked to four other OBis. Regarding outgoing calls on the 212's LINE port there can only be one at a time!
Some protection would be a good idea to prevent any other OBi on the planet coming in over the OBiTALK network to the 212 and calling out on the POTS line. See page 19 of the tutorial I mentioned above.
Yes the LINE and PHONE ports conform quite well to FXO and FXS standards so no surprise that you can connect them together though I cannot immediately think why RESTRICTED would come up.
azrobert:
There is a hack you can use for more than 4 destinations. You need an open SP to do this easily. Your inbound route will send the call to 3 destinations. The 4th will be looped out say SP4 and back into SP4. The SP4 inbound route will send the call to the 4th and 5th destinations.
Setup dummy trunk:
Service Providers -> ITSP Profile D -> SIP -> ProxyServer: 127.0.0.1
Service Providers -> ITSP Profile D -> SIP -> X_SpoofCallerID: Checked
Voice Services -> SP4 Service -> AuthUserName: anything
Voice Services -> SP4 Service -> X_RegisterEnable: unchecked
Voice Services -> SP4 Service -> X_ServProvProfile: D
Inbound route:
dest1,dest2,dest3,sp4(0@127.0.0.1:5063)
5063 is the X_UserAgentPort
5063 is the default, but might get changed to 5083 with GV setup
SP4 inbound route
dest4,dest5
myobinameisinuse9987:
Quote from: azrobert on April 23, 2021, 03:58:06 pm
There is a hack you can use for more than 4 destinations. You need an open SP to do this easily. Your inbound route will send the call to 3 destinations. The 4th will be looped out say SP4 and back into SP4. The SP4 inbound route will send the call to the 4th and 5th destinations.
Setup dummy trunk:
Service Providers -> ITSP Profile D -> SIP -> ProxyServer: 127.0.0.1
Service Providers -> ITSP Profile D -> SIP -> X_SpoofCallerID: Checked
Voice Services -> SP4 Service -> AuthUserName: anything
Voice Services -> SP4 Service -> X_RegisterEnable: unchecked
Voice Services -> SP4 Service -> X_ServProvProfile: D
Inbound route:
dest1,dest2,dest3,sp4(0@127.0.0.1:5063)
5063 is the X_UserAgentPort
5063 is the default, but might get changed to 5083 with GV setup
SP4 inbound route
dest4,dest5
That is very logical to forward it directly within the 212 itself. I'm guessing the SP4 also allows 4 InboundCallRoute locations, making it 7 locations?
Any delays expected? Do I need to increase MaxSessions or anything else for the extra SP4 processing?
Thank you!
With the help you guys are giving, this system is really coming along.
Navigation
[0] Message Index
[#] Next page
[*] Previous page