NO JOY System recordings *77 not working google voice obi110

[acesdeals]

I have had my pbx working for a while on RPI, i wanted to change my IVR recording so i typed in my extension and then typed *77 on my phone and i get a busy signal
There are no obvious issues aside from this, as we can send and receive calls without issue
I tried changing the extension from *77 to *36 with the same issue

 

[rossiv]

My guess is that the dial plan is wrong on the Obi. Can you post that please?

 

[acesdeals]

https://docs.google.com/file/d/0B6eebxfKjicEVnNwcUhyeWZiTDQ/edit?usp=drivesdk

Is that the right piece of information

 

[visionlogic]

On the Obi look at the "Star Codes". The Obi defaults to designating *77 to "Block Anonymous Calls". You must change the setting from its default. I changed it to *44, then went into my IncrediPi and changed the Feature Code for Save Recording to *44. Works fine. There may be a better, more efficient way of doing it, but that's what I did.

 

[acesdeals]

From looking at your post it seems you changed the block to *44 and then also changed the recordings to *44. I would think you want them to be different.
I just changed it now. I will post back the results.

 

[visionlogic]

From looking at your post it seems you changed the block to *44 and then also changed the recordings to *44. I would think you want them to be different.
I just changed it now. I will post back the results.

I could have possibly handled it differently. But since *44 means nothing to the Obi star codes defaults, it apparently gets passed to the IncrediPi without issue. And I have no need for the Obi to block any calls with *77.

 

[acesdeals]

Still not working, get busy signal as soon as i type in *44

I atttached 3 screenshots to show the information that i have

https://docs.google.com/file/d/0B6eebxfKjicEY2ItOE12dWhaN2c/edit?usp=drivesdk

https://docs.google.com/file/d/0B6eebxfKjicESS1DdDYzemUxRzA/edit?usp=drivesdk

https://docs.google.com/file/d/0B6eebxfKjicEeDlOQ3paNUQ2WFE/edit?usp=drivesdk

 

[visionlogic]

Still not working, get busy signal as soon as i type in *44

I atttached 3 screenshots to show the information that i have

https://docs.google.com/file/d/0B6eebxfKjicEY2ItOE12dWhaN2c/edit?usp=drivesdk

https://docs.google.com/file/d/0B6eebxfKjicESS1DdDYzemUxRzA/edit?usp=drivesdk

https://docs.google.com/file/d/0B6eebxfKjicEeDlOQ3paNUQ2WFE/edit?usp=drivesdk

In the Obi web gui try this: go to Service Providers > ITSP Profile A > General > DigitMap and add within the string this > "|*44|" (without the quotes, of course).

 

[acesdeals]

no change, same issue
it seems with other feature codes i try some work and others give the busy signal

 

[visionlogic]

no change, same issue
it seems with other feature codes i try some work and others give the busy signal

In my prior post I was assuming that you are using ITSP Profile A as the Service Provider profile containing your RPI server address settings, and that you have set the Voice Services > SP1 Service to use that Profile. Is that indeed the case?

 

[acesdeals]

this is how i have it set
https://docs.google.com/file/d/0B6eebxfKjicEZjQwdWQ4TjZtajQ/edit?usp=drivesdk

https://docs.google.com/file/d/0B6eebxfKjicEbUFsSFRadUpjdXM/edit?usp=drivesdk

 

[visionlogic]

this is how i have it set
https://docs.google.com/file/d/0B6eebxfKjicEZjQwdWQ4TjZtajQ/edit?usp=drivesdk

https://docs.google.com/file/d/0B6eebxfKjicEbUFsSFRadUpjdXM/edit?usp=drivesdk

Your 2nd screen capture does not show the top of the the SP1 Service page. Can't tell what you've enabled.

 

[acesdeals]

yes i sent both screenshots to cover the full page
https://docs.google.com/file/d/0B6eebxfKjicEZjQwdWQ4TjZtajQ/edit?usp=drivesdk

 

[visionlogic]

yes i sent both screenshots to cover the full page
https://docs.google.com/file/d/0B6eebxfKjicEZjQwdWQ4TjZtajQ/edit?usp=drivesdk

Sorry, didn't see that. All looks good... same as my settings. Don't know what's up. You may want to return to the Obi Star Codes, turn off all the defaults, wipe all the entries there clean, save and reboot. That way the Obi should not intercept and process any * code. They should all pass to your RPI. Just my 2 cents.

 

[acesdeals]

i did that, all clear and saved then rebooted
still get busy signal

i dont think its obi related, i think its something on the pi since it was working before than just stopped

 

[acesdeals]

went through all settings and still no go

willing to pay somebody to get this issue fixed via paypal