Self-Provisioning IVR working with BAT in CUCM 15 SU2........HOW!!????

[Ronald075]

Hello,

I have configured self-provisioning IVR, and I want it to work with BAT, exactly the same as it works now in combination with UCCX.
I do NOT use LDAP!
Only autoreg and make the line and device templates.

[Maren Mahoney · Accepted solution]

One requirement for the SPIVR process is that the user has a Primary Extension configured on the End User page. This tells CUCM what number to associate with the phone that is being self-provisioned.

Generally, a Primary Extension is configured after you associate a device with a user and select the DN on that device that should be the user's Primary. Of course, with SPIVR the point is that there is no device yet so an administrator can't select a Primary Extension.

When you do LDAP integration and use a Feature Group Template (with a User Profile in it), CUCM will create a DN for the user when they are synced from LDAP and will populate the Primary Extension automatically even though there is no device yet.

My attempts to get BAT to populate the Primary Extension field when the user does not have a device associated have failed, although I seem to remember posts saying others have managed to get this to work. (I'd have to see it to believe it though, with what I know about how CUCM works.)

One idea that occurred to me but I never tried:

1. Build all of the DNs for users, which you can do using BAT.
2. Then build one physical phone and associate ALL of the DNs with it.
3. Then use BAT to set that device as a Controlled Device for all end-user accounts.
4. Setting the Primary Extension from the list of DNs on that phone may be able to be done as part of the same BAT job, or may have to be a second BAT job.

That would allow you to populate the Primary Extension, and as long as you have the User Profile fully configured with Line and Device templates the SPIVR *should* work.

I wish I had a lab to test this in so I could tell you for sure. If you give this a try I'd love to know how it goes.

Maren

[Ronald075]

Hello Maren Mahoney,

My problem has not been resolved yet.
We now use TAPS via UCCX without a user or prim extension.
I want the same in combination with Self-prov.
I see that I have to create a user with Pirmary extensions for each BAT file, which is not desirable.

Regards,

Ronald 

[Nithin Eluvathingal]

If you are not using LDAP, you need to doa  work around for the self-provisioning IVR to work when importing users in bulk. This workaround is not documented anywhere. I have used this option with many customers who do not use LDAP and instead add users manually using BAT.

Primary extensions are mandatory for self-provisioning to work. When adding users in bulk, if you include this information, the primary extensions will not be populated. This works fine with LDAP syncing.

To populate the primary extension as per the bulk document:

1. First, create the extension range on the CUCM using the Directory Number option under Call Routing.
2. Then, import the users, and you should see the primary extensions. Self-provisioning can then be used.

[Roger Kallberg]

Why are you posting your text within a code block?

[Maren Mahoney]

TAPS and SPIVR are different, and one difference is that a Primary Extension is required to make the SPIVR work. There is no workaround for that requirement.

However, as @Nithin Eluvathingal and I mentioned you can create the directory numbers via BAT and then create or update your users with those extensions as Primary Extensions via BAT. You should then be able to use the SPIVR.

Maren

[Ronald075 · Accepted solution]

Thanks you for the input ..... I have tested it all and can simply set any existing number on the relevant device with option 2 in the ivr menu.

Regards:

Ronald

[Roger Kallberg]

If @Maren Mahoney gave you the solution why have you selected your own post as the solution to your question?

That's not very nice.