tag:blogger.com,1999:blog-2158853543793456735.post3691831520416093017..comments2023-10-02T04:50:01.667-07:00Comments on VoIPNorm's Collaboration Blog: Update: “Busy Here” Scripting Project Phase IIChris Normanhttp://www.blogger.com/profile/07200178774058910421noreply@blogger.comBlogger15125tag:blogger.com,1999:blog-2158853543793456735.post-50471590122378046832014-11-17T07:40:51.923-08:002014-11-17T07:40:51.923-08:00Hi,
i just tried to implement the script on Lync 2...Hi,<br />i just tried to implement the script on Lync 2013, but without success. When i activate the script with a priority lower than 7, no calls are routed after activating.<br /><br />If I activate the script with a priority lower than 7, the script isn't used, i can see no log entries in the apilogger.exe<br /><br />Any Ideas?Daniel Jelinekhttps://www.blogger.com/profile/15206729015917797382noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-43856252363505548022014-06-03T04:59:20.923-07:002014-06-03T04:59:20.923-07:00Hi,
Trying to configure this script on our Lync 2...Hi,<br /><br />Trying to configure this script on our Lync 2013 environment, however it doesn't seem to work. Calls are still coming through when busy, both internal and PSTN.<br /><br />This is my first encounter with MSPL scripts, have I created the it correctly (as follows)?<br />Identity : Service:Registrar:fepool1.mydomain.com/busybusy<br />Priority : 0<br />Uri : http://www.meldingtechnology.com/busybusy<br />Name : busybusy<br />Enabled : True<br />Critical : True<br />ScriptName : C:\scripts\busybusy.am<br />Script :<br /><br />Can anyone advise whether this script should also work on Lync 2013?<br /><br />Thanks,<br />ShaunAnonymoushttps://www.blogger.com/profile/07117556986940320464noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-68283871752339225392014-04-07T08:24:30.148-07:002014-04-07T08:24:30.148-07:00Does this script work if your Lync environment has...Does this script work if your Lync environment has Enhanced Privacy mode enabled? If not, is there a work around?vitalizmhttps://www.blogger.com/profile/13856473264140685437noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-46410157662238404532013-03-12T02:47:15.017-07:002013-03-12T02:47:15.017-07:00This comment has been removed by the author.HLhttps://www.blogger.com/profile/10751025794756441233noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-35544686945090184612012-11-14T19:40:38.160-08:002012-11-14T19:40:38.160-08:00This line is returning NULL in every case tested: ...This line is returning NULL in every case tested: Where is determines the busy status of the callee.<br /><br />publication = QueryCategory(toUri, 2, "state", dbEndpoint.Instance);<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-92145933490326334592012-11-09T07:38:41.302-08:002012-11-09T07:38:41.302-08:00If you want busy also when in conference call. (We...If you want busy also when in conference call. (We did want)<br /><br />Here it is:<br /><br /> if (IndexOfString(publication, "on-the-phone") >= 0) {<br /> Log( "Debugr", false, "***BusyBusy***: endpoint in a call change to busy state" );<br /> anyEndpointBusy = true;<br /> break;<br /> }<br /> else if (IndexOfString(publication, "in-a-conference") >= 0) {<br /> Log( "Debugr", false, "***BusyBusy***: endpoint in a conference change to busy state" );<br /> anyEndpointBusy = true;<br /> break;<br /> }<br /> else {<br /> Log( "Debugr", false, "***BusyBusy***: endpoint not in call stay in free state" );<br /> }<br /><br />Meitzihttps://www.blogger.com/profile/02448002346769928330noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-18251477631209241742012-10-04T08:58:24.243-07:002012-10-04T08:58:24.243-07:00It worked!
I have perfect SIP trunk now. Thanks g...It worked!<br /><br />I have perfect SIP trunk now. Thanks guys.<br /><br />I needed to modify SIP trunk call because toUri looked like<br />"sip:08xxxx009;phone-context=DefaultProfile@mydomain.fi;user=phone"<br />(with this code does not find user and think user is always "free")<br />(xxx are for my safe)<br /><br />So i just modify it to look like<br />"sip:08xxxx009@mydomain.fi;user=phone"<br /><br />This code is not direct use for everybody because I have normalization also here:<br />if (IndexOfString (toUri, "sip:xxxx", false) > -1) { // xxxx = your first digits in your linephone<br /> toUri = Concatenate("sip:+358yyyy",SubString(toUri,10,3), "@mydomain.fi;user=phone");<br /> Log( "Debugr", false, "***BusyBusy***: SIP TRUNK fix ", toUri);<br />}Meitzihttps://www.blogger.com/profile/02448002346769928330noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-10457641630637695682012-10-04T08:24:28.608-07:002012-10-04T08:24:28.608-07:00IMPORTNT:
I think response 600 is better.
It work...IMPORTNT:<br />I think response 600 is better.<br /><br />It work on PSTN calls and in Lync it gives "user is on phone".<br /><br />So modify <br /> Respond( 600, "Busy here" );<br />And VOILA!<br /><br /><br />Also note, if you have phone normalization for incoming numbers, SIP uri will be very wrong. (not normalized number)<br />I will investigate that next...Meitzihttps://www.blogger.com/profile/02448002346769928330noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-60453583437306674752012-07-18T09:05:54.653-07:002012-07-18T09:05:54.653-07:00I am getting the same as @Andy
Lync enabled user w...I am getting the same as @Andy<br />Lync enabled user with no UM enabled - fine, busy works<br />Lynch UM enabled user strange thing happens, caller gets ringing and recipient doesn't get any call waiting or any pop up to say another call... only when the busy call is finished, an email is received telling of miss call.<br /><br />Is there a way to also mix into the pool PSTN calls, when a PSTN calls a Busy Lync user, it just drops to normal dial tone, no busy... no voicemail nothing..<br /><br />Help would be appreciated<br /><br />excellent script btwAlphaJuliethttps://www.blogger.com/profile/13691275344124553120noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-84989438737742312712012-06-06T11:03:46.907-07:002012-06-06T11:03:46.907-07:00The call should go straight to voice mail.The call should go straight to voice mail.jay brummetthttp://www.meldingtechnology.comnoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-51012318567759015802012-05-28T12:19:17.637-07:002012-05-28T12:19:17.637-07:00Hello, I was wondering if you could please assist ...Hello, I was wondering if you could please assist with a question I have? I have implemented the busybusy.am MSPL script with a high priority and calling non UM enabled users works great and I receive the expected busy tone. When I call UM enabling users this unfortunately fails, and while the Lync 2010 client does not error, the active call window just displays "Calling Lync..". <br /><br />I think my issue is the value I have used for Exchange UM SIP URI. Using the OCSUMUtil application on my front end server I have confirmed my Subscriber Access SIP URI is DefaultUM.contoso.local@contoso.local. I was wondering if you could confirm if I am using the correct field? Any help would be greatly appreciated.Andynoreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-61318856080132915362012-05-15T08:52:58.272-07:002012-05-15T08:52:58.272-07:00Hi:
Thanks for your comment. I was taking a look ...Hi:<br /><br />Thanks for your comment. I was taking a look to understand your point about the call to ProxyRequest(). I see your point. From the docs:<br />" If the request has a strict route (the "Route" header is present and populated), you must only pass the empty string as a parameter. Alternate destinations are not allowed in this case."<br /><br />On the other hand, checking at the docs for the requestFilter element (where the strictRoute attribute is set): "Set strictRoute to true if you want the application to receive all messages. Setting the strictRoute filter to false guarantees that only requests that need routing will be delivered."<br />http://msdn.microsoft.com/en-us/library/gg439282.aspx<br /><br />In this case then, it means that we are getting both strict and non strict requests. I think in this case then, what might needs to be fixed is the strictRoute attribute. Still, the script works and does not generate errors because the flow of the code will only get to the call of ProxyRequest(toVoiceMail) with non strict requests.<br /><br />Thanks for checking out the script!Angela from MeldingTechhttps://www.blogger.com/profile/14386255326153573174noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-21487098398210773682012-05-09T23:51:18.128-07:002012-05-09T23:51:18.128-07:00Good afternoon,
When reading your script, I stum...Good afternoon, <br /><br />When reading your script, I stumbled on this description of proxyRequest:<br /><br />http://msdn.microsoft.com/en-us/library/dd167433(v=office.12).aspx<br /><br />and it seems, that voice mail redirection branch will generate error, since you have strictRoute="true" in script manifest. According to ProxyRequest() description it must be called without arguments, when strictRoute is true.Унылый теоретикhttps://www.blogger.com/profile/11944908953263127778noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-44177854655556325382012-04-21T11:30:55.308-07:002012-04-21T11:30:55.308-07:00Hi Matthias,
I took a quick look at you web site ...Hi Matthias,<br /><br />I took a quick look at you web site and the tool looks great. I am sure there are a bunch of people that would be interested in your tool and also seeing it develop even further. Feel free to send me some screen shots and info and I would be happy to do a post about it. When i get time I will download the free version to try out in my lab.<br /><br />Cheers<br />ChrisChris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-88391869258063305582012-04-20T09:33:42.598-07:002012-04-20T09:33:42.598-07:00Hi,
amongst other your blog articles on the theme...Hi, <br />amongst other your blog articles on the theme MSPL have been inspiring to our team but we have noticed that the normal admin can not utilize MSPL i.e. does not even know it exists. Thus we came to the conclusion to build the tool SimpleRoute with which it is easy and safe to generate MSPL scripts without any programming skills.<br /><br />I will be happy if you could take a look at SimpleRoute and give me some feedback. The FREE-Edition of SimpleRoute is our calling card and is freely available at http://www.colima.de/en/products/simpleroute.html <br />If you like I could send you a trialversion of the PRO-Edition which offers extended functions. Because of the community being helpful to us we allow the use of the generated MSPL scripts. Thus the client benefits by saving time through the generating of valid scripts.<br /><br />I look forward to your answer (you'll find my contact details on the Presence-Widget on the website mentioned above).<br /><br />Best regards<br />MatthiasMatthias Engelmannhttps://www.blogger.com/profile/02309745279627092325noreply@blogger.com