Unauthorized international calls from my GV account
RonR:
No. The intruder would be registering his SIP client in addition to or in place of your 3CX client with OBiAPP for PC. 3CX wouldn't know anything about the intruder.
(I updated my previous post.)
infin8loop:
Quote from: RonR on May 13, 2012, 04:07:53 pm
Quote from: infin8loop on May 13, 2012, 03:39:46 pm
Could the OBiAPP for PC Properties -> Advanced -> SIP Port be changed to something other than 5060 that isn't forwarded in the router, thus making it unaccessible from outsiders?
Obihai doesn't give the user any way to configure OBiAPP for PC. It's force-fed settings from the OBiTALK Web Portal with no user accessible options.
Interesting because I was able to change the OBiAPP SIP Port to 5100 and save it and change zoiper to point to 127.0.0.1:5100. Zoiper registered successfully to ObiAPP and I can make calls.
If it's not doing what I think it's doing, then the ability to save the SIP Port setting is misleading at best.
RonR:
Quote from: infin8loop on May 13, 2012, 06:06:13 pm
Interesting because I was able to change the OBiAPP SIP Port to 5100 and save it and change zoiper to point to 127.0.0.1:5100. Zoiper registered successfully to ObiAPP and I can make calls.
If it's not doing what I think it's doing, then the ability to save the SIP Port setting is misleading at best.
No, you're correct. I was thinking about the OBiTALK number, Voice Gateway, and Speed Dials, which cannot be changed in the App. I forgot about the tab to change the ports. Sorry for the mis-information.
Ostracus:
Quote from: RonR on May 13, 2012, 05:02:16 pm
An alternative to using OBiAPP for PC and the OBiTALK Service would be to have your SIP client(s) communicate directly with your OBi using Single-Stage Dialing Through Any OBi Trunk Using SIP. No passwords are used, but you can limit SIP access to the OBi by IP address using:
Service Providers -> ITSP PRofile x -> SIP -> X_AccessList
I looked through that and for the Obi202 you have:
Quote
Voice Services -> SPx Service -> X_InboundCallRoute (SPx must be configured for SIP) (OBi202):
{(Mtsc)>(<*1:>(Msp1)),(Mtsc)>(<**1:>(Msp1)):sp1},{(Mtsc)>(<*2:>(Msp2)),(Mtsc)>(<**2:>(Msp2)):sp2},
{(Mtsc)>(<*3:>(Msp3)),(Mtsc)>(<**3:>(Msp3)):sp3},{(Mtsc)>(<*4:>(Msp4)),(Mtsc)>(<**4:>(Msp4)):sp4},
{(Mtsc)>(<*8:>(Mli)),(Mtsc)>(<**8:>(Mli)):li},{(Mtsc)>(<*9:>(Mpp)),(Mtsc)>(<**9:>(Mpp)):pp},
{(Mtsc)>**0:aa},{(Mtsc)>***:aa2},{(Mtsc)>(Mp2p):spx},{(Mtsc)>(Mpli):pli},{(Mtsc)>0:ph},{(Mtsc):},{ph}
While mine lists {ph1,ph2} which is phone one and two. Seems your example would need some modification to work.
RonR:
Quote from: Ostracus on May 13, 2012, 07:17:33 pm
While mine lists {ph1,ph2} which is phone one and two. Seems your example would need some modification to work.
ph is equivalent to ph1.
I've updated the example to instruct the user that ph1 or ph2 can be used as desired.
Thanks!
Navigation
[0] Message Index
[#] Next page
[*] Previous page