ENABLE anonymous calls on Obi110

<< < (2/3) > >>

giqcass:
Quote from: drgeoff on May 16, 2014, 04:52:44 am

FYI the AnonymousCallEnable settings are only relevant to calls from your OBi.

I'm not sure if anonymous incoming calls show up in the Obi's call log or not.  Worth a quick look.

I'm reasonably sure they do appear in the events sent to the syslog server if you have one set up.


Call history is worth a check however you are incorrect about *77 and *87.  Those are for inbound anonymous blocking.  *81, *82, *67, and *68 are for outbound anonymous calling features.  I know because I accidentally set the incoming anonymous blocking before when I accidentally dialed *77.

drgeoff:
If the "incorrect about *77 and *87" was intended for me, I respectfully point out that I made no reference to those.

redzep:
Thanks to everyone for trying to help me solve this. My call log is full of my attempts to get through, a typical one looks like this:

Call 28   05/14/2014    16:00:00   

Terminal ID           SP1           PHONE1
Peer Name           asterisk   
Peer Number   asterisk   
Direction           Inbound   Inbound
16:00:00           Ringing   
16:00:04                      Call Connected
16:00:08           End Call   

Quote from: giqcass on May 15, 2014, 09:30:16 pm

Did you change the inbound call route on the Obi?  Anonymous calls can be blocked there as well.


I don't believe I touched that. Where would that be? Here are the instructions I followed for F9:

Login to your Obi, and go to Service Providers > ITSP Profile A > SIP, and set:
ProxyServer: incoming.future-nine.com
RegistrarServer: incoming.future-nine.com
UserAgentDomain: sip.future-nine.com

Then go to Service Providers > ITSP Profile > General, and set:
Name: your name (or any name)
Digit Map:
(*xx.|911|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|[2-9]xxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

Then go to Voice Services > SP Service, and set:
X_KeepAliveEnable: yes
X_KeepAliveExpires: 60
AuthUserName: see username in the SIP INFO screen
AuthPassword: see secret field in the SIP INFO screen

drgeoff:
Quote from: redzep on May 16, 2014, 04:52:02 pm


Quote from: giqcass on May 15, 2014, 09:30:16 pm

Did you change the inbound call route on the Obi?  Anonymous calls can be blocked there as well.


I don't believe I touched that. Where would that be?

Voice Services/SP1 Service/X_InboundCallRoute.  Default is 'ph' (without the quote marks).

But looks to me that your call history is showing that the phone was rung for 4 seconds, then it was picked up and after another 4 seconds the call was terminated. What sort of phone is connected to the OBi?

redzep:
Thanks for sticking with me on this.

so I noticed that the X_InboundCallRoute is different for SP1 & SP2

SP1: ph
SP2: {>*********:ph}

where the asterisks represent one of my F9 account numbers

is that right? could that be why the Obi is rejecting anon calls on SP1?

Navigation

[0] Message Index

[#] Next page

[*] Previous page