ToUserPart_str = string.sub(ruri, startTo_str+4, endTo_str-1) Local method, ruri, ver = msg:getRequestLine()ĮndTo_str = string.find(ruri, startTo_str+1) I’ve also argued heavily with myself if the To-header also should be updated, but it seems to work just fine with only updating the INVITE, so I’m happy with that for now. I will not argue that this script is perfect at the moment, but it is a start and can surely be developed further down the road. Where should I do that? It would be very easily done in the VCS, a bit more tricky on the CUCM side – but still doable. So, to manage this, I do need to provision the space using a prefix (or suffix), such as cmr-username and rewrite the invite on the way. Reachibility for the MeetingApp is way beyond the scope of this post, we are using devices and/or Jabber and will just use the spaces within CMS. That causes a conflict with the adressing of the actual user if you were using the MeetingApp. If the username should be used to provision the space – guess what, it will not synchronize that user. My preferred logic there would be to have the CMS-spaces within a specific subdomain, so – to call a user directly you would dial and to dial the space of the user you would dial to apply this logic does however introduce a few issues.
I’m personally not to happy with the idea to utilize prefix/suffix on the userpart, such as cmr-username, username.vmr – whatever name you want to use, or where you place it. I have spent serious time considering how I want to address my spaces within CMS.
0 kommentar(er)
