Always get busy signal when doing *67

[tritch]

Brandon is the man.....I'm sure he can get to the bottom of your issue.


BTW, I'm using the SPA2102 with this dial plan I created below. I always use 10 digit dialing like my cell phone, so I never created any 11 digit plans.

(0[3-9][0-9]S0|[49]11S0|[2-9]xx[2-9]xxxxxxS0|123S0|*xx[2-9]xx[2-9]xxxxxxS0|011[2-9]x.S3)

Just make sure you have *xx[2-9]xx[2-9]xxxxxxS0 or *xx1[2-9]xx[2-9]xxxxxxS0 somewhere in your dial plan. Only having *xx or *xxS0 may cause the ATA to send the code before sending the rest of the numbers following *67 code.

I did some experimenting with my dial plan using your 3 examples above:

1) If I dial *67 followed by a 10 digit phone number, the call works and blocks CID as expected.

2) If I dial *30, the phone acts dead for about 3 seconds and I get a busy signal, however it does activate the "Block caller ID for all calls" feature. I confirmed this by testing a call and looking to see if it turned this feature on in vPanel (Go to the Features option in vPanel and see if the option shows "Caller ID Blocked: Do not send any caller ID info" to verify it worked)

3) If I dial *31, the phone acts dead for about 3 seconds and I get a short automated response that says "Thank you" and hangs up. Again, I confirmed the option re-enabled caller ID as expected by doing a test call and checking vPanel which now shows "Caller ID Blocked: Send my caller ID info" enabled.

[LouisWilen]

Let me toss in another piece of information that might be related. I've set the Vertical Service Activation Codes as follows. What I don't understand is how they relate to what is actually sent in the request-uri. Can you give me a bit of explanation?

(Click on the image below to see the screen shot)
Untitled.jpg