Jeff,<br><br>I am setting up a Unity Enterprise with DTMF inband integration. (Bosch Integral 33XE.) Everything works fine, except the internal greeting.<br><br>Regarding to the avanalog.avd, the integration line should be include the I (internal) and the F (Forwarded). I used the following line: Data7 = 8F#I# NOANSWER<br><br>The expected DTMF tones are received, used the integration monitor to check this.<br><br>Of course the internal greeting is enabled and recorded. <br><br>The system still plays the STANDARD greeting.<br><br>What am I doing wrong?<br><br>Jos<br><br><br><br>
Youre not doing anything wrong, but I think I know what the problem is. The I does not stand for internal it means Incoming. This is the calling party which could be an internal extension or an external calling number.
Unlike digital integrations which give us loads of details on the incoming call, analog integration generally are pretty lite on the info. As such there isnt a specific designation for a call that originated on the local PBX or one thats coming externally. Things get complicated even in digital integration land when you start talking about networked switches and the like what, really, is an internal caller? The idea behind the internal greeting is that I can impart some information such as where Im REALLY at to my coworkers that I dont want external folks hearing. If someone is in the lobby, for instance, and calls my extension, do I want them to hear that Im out visiting their competitor at the moment? Probably not
So, we got around this by making a simple rule: If the calling party number matches the DTMF_ID of a subscriber in our directory, we consider the call internal. If the calling number does not have a match, its considered external. This way were not reliant on the switch to specifically tell us its an internal vs. external call and we avoid embarrassing missteps when external people are using internal lines.
So, in your example, you have 8F#I# NOANSWER in your AVANALOG.AVD file, which is fine. The integration monitor will show internal as the call origin (it defaults to internal on the display unless its specifically over ridden which for analog integrations wont happen unless you have an ANI configuration setup for caller ID on external calls). However Im willing to bet the calling number column shows a number that doesnt correspond to the extension of a subscriber in your system.
I tried this out on my 2.4.0 120 box by setting up a subscriber for extension 301 and one for extension 302. I used the same packet definition you have and I entered 8301#302# (if you dont have fast fingers, crank of the digit delay times if you want to test this by hand) and I got the internal greeting for the user at 301. If, instead, I entered 8301#333# I get the standard greeting of 301 since there is no subscriber for 333. The integration monitor shows the same thing for both (other than the calling number is different) a little confusing, I know
If thats not the case, you have something squirrely going on somewhere and well need to take a closer look.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4