Noticed today that on incoming calls, the cdr report will show 90 infront of the destination extension in addition to a line of the destination extension without the 90.
Have not noticed this before. Going back and looking at old CDR reports, it stated happening in May. The system is set to automatically update weekly. Is this a result of an update?
Zulu devices are generated with a 90 prefix to the regular extension number, that’s what you’re seeing.
Will this interfere with ring groups or the way incoming calls are routed? We’re still in the process of getting ZULU set up. Will I have to add 90 to all extensions in the ring groups?
It shouldn’t, since your incoming routes are set in the Incoming Destination.
It depends on how you implement your Zulu calling. If you use Zulu as a secondary destination (like on Find Me/Follow Me) then you should be good to go. So, for example, if you use FMFM to send desk calls to people’s cell phones after the desk phone times out, then you don’t have to do anything. If, on the other hand, you want them both to ring, then yeah.
I don’t know how you’re planning on using Zulu, but if the model you choose is “as an alternative” to the desk phone, you probably want to avoid having your Zulu phones tied into the ring groups. In fact, I can think of several reasons why this would cause consternation within your user community (both phones on my desk are ringing, etc.) If, on the other hand, you are using Zulu as the only phone for some people, you will need to strategically add the phones that you want to include.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.