Hi Suppose, the default "Emergency" dial plan topmost in order on the dial plan screen is configured as follows: PSTN prefix = 8 Emergency number = 911
Next the default "Voicemail" dialplan lowest in order on the dial plan screen is configured as follows: Voicemail inbox prefix = 8 The call made to the emergency number dialed as 8911 reaches the mailbox of user 911. Is this correct? What can be the solution for this problem ? (other than not using the PSTN Regards Venkateshwaran T [email protected] wrote: > Send sipx-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://list.sipfoundry.org/mailman/listinfo/sipx-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sipx-dev digest..." > > ------------------------------------------------------------------------ > > [please change the subject line when replying] > ------------------------------------------------------------------------ > > Today's Topics: > > 1. sipXecs 4.2 :NOTIFY message with empty body > ([email protected]) > 2. Dial Plan--PSTN Prefix (Kumaran) > 3. Re: Dial Plan--PSTN Prefix (Todd Hodgen) > 4. Re: sipXecs 4.2 :NOTIFY message with empty body (Joegen Baclor) > 5. sipXtapi - build environment on windows (Mahudeswaran) > > > ------------------------------------------------------------------------ > > Subject: > [sipx-dev] sipXecs 4.2 :NOTIFY message with empty body > From: > <[email protected]> > Date: > Fri, 7 Jan 2011 01:00:46 +0000 > To: > <[email protected]> > > To: > <[email protected]> > > > Hi All, > > The new version of sipXtackLib (4.2) doesn't seem to support sending of > NOTIFY messages > with empty body.It treats Subscription as failure instead. > > Below is the code segment in SipSubscribeServer::handleSubscribe() > // Note that since this NOTIFY is due to a SUBSCRIBE, > // it should contain 'full' content. Hence, > // the fullState parameter of getNotifyContent is TRUE, > // and is not taken from > // eventPackageInfo->mEventSpecificFullState. > UtlString availableMediaTypes; > if (handler->getNotifyContent(resourceId, > eventTypeKey, > eventType, > *(eventPackageInfo->mpEventSpecificContentMgr), > acceptHeaderValue, > notifyRequest, > TRUE, > &availableMediaTypes)) > { > .... > } > else > { > // No content was available, so the subscription fails. > // Determine the reason and set the response code. > .... > } > > However as per RFC 3265 > If the resource has no meaningful state at the time that the SUBSCRIBE > message is processed, > this NOTIFY message MAY contain an empty or neutral body.See section 3.2.2. > for further details on NOTIFY message generation > > Is this a bug in the stack or am I missing something? > > Regards, > Gauri > > > > ------------------------------------------------------------------------ > > Subject: > [sipx-dev] Dial Plan--PSTN Prefix > From: > Kumaran <[email protected]> > Date: > Fri, 07 Jan 2011 12:21:17 +0530 > To: > [email protected] > > To: > [email protected] > > > Hi All > While working on Dial plan through unmananged gateway,I changed the > PSTN prefix as 8 from 9 and the emergency is same 911. When i Dial 911 > the call is landed on unmanaged gateway.But i tried 8911 the call is > connected IVR(voice mail inbox of 911) and played the prompt that user > extension not valid. Soo working wise its correct because 8 + Ext is > Voicemail inbox prefix.But my question is why SipXconfig is not > throwing a error message when changing PSTN prefix to 8 because prefix > 8 is already Voicemail inbox prefix. It also reflecting in linux > console as -<userPattern>8811</userPattern> > Regards > Venkateshwaran T > > > ------------------------------------------------------------------------ > > Subject: > Re: [sipx-dev] Dial Plan--PSTN Prefix > From: > "Todd Hodgen" <[email protected]> > Date: > Thu, 6 Jan 2011 23:39:07 -0800 > To: > "'sipXecs developer discussions'" <[email protected]> > > To: > "'sipXecs developer discussions'" <[email protected]> > > > In the dial plan, 8+3 digits is a different scenario than 8+10 digits, and > acceptable. Additionally, a dial plan of three digits exactly 911 would be > different as well, and acceptable. > > If you had an access code of 81 and 82 and then three digits to dial two > offsite systems, that wouldn't necessarily be a conflict with dialing 8+ 3 > digits for local voicemail. > > I would agree the system should throw an error when two dial plans are the > same. But just because 8 is used at the beginning of two dial plans doesn't > necessarily make it wrong, or unacceptable. I think if you further define > your dial plans, and make sure they are in the correct order things will > work differently. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Kumaran > Sent: Thursday, January 06, 2011 10:51 PM > To: [email protected] > Subject: [sipx-dev] Dial Plan--PSTN Prefix > > Hi All > While working on Dial plan through unmananged gateway,I > changed the PSTN prefix as 8 from 9 and the emergency is same 911. When > i Dial 911 the call is landed on unmanaged gateway.But i tried 8911 the > call is connected IVR(voice mail inbox of 911) and played the prompt > that user extension not valid. Soo working wise its correct because 8 + > Ext is Voicemail inbox prefix.But my question is why SipXconfig is not > throwing a error message when changing PSTN prefix to 8 because > prefix 8 is already Voicemail inbox prefix. It also reflecting in linux > console as -<userPattern>8811</userPattern> > Regards > Venkateshwaran T > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > > > ------------------------------------------------------------------------ > > Subject: > Re: [sipx-dev] sipXecs 4.2 :NOTIFY message with empty body > From: > Joegen Baclor <[email protected]> > Date: > Fri, 07 Jan 2011 19:58:35 +0800 > To: > sipXecs developer discussions <[email protected]> > > To: > sipXecs developer discussions <[email protected]> > > > I do not see anything wrong in the code. The handler could do anything > it likes with the notify and return TRUE even if there is currently no > state. Are you reporting a specific bug in a sipxecs event package. > MWI, RLS? > > > On Friday, 07 January, 2011 09:00 AM, [email protected] wrote: >> Hi All, >> >> The new version of sipXtackLib (4.2) doesn't seem to support sending >> of NOTIFY messages >> with empty body.It treats Subscription as failure instead. >> >> Below is the code segment in SipSubscribeServer::handleSubscribe() >> // Note that since this NOTIFY is due to a SUBSCRIBE, >> // it should contain 'full' content. Hence, >> // the fullState parameter of getNotifyContent is TRUE, >> // and is not taken from >> // eventPackageInfo->mEventSpecificFullState. >> UtlString availableMediaTypes; >> if (handler->getNotifyContent(resourceId, >> eventTypeKey, >> eventType, >> *(eventPackageInfo->mpEventSpecificContentMgr), >> acceptHeaderValue, >> notifyRequest, >> TRUE, >> &availableMediaTypes)) >> { >> .... >> } >> else >> { >> // No content was available, so the subscription fails. >> // Determine the reason and set the response code. >> .... >> } >> >> However as per RFC 3265 >> If the resource has no meaningful state at the time that the >> SUBSCRIBE message is processed, >> this NOTIFY message MAY contain an empty or neutral body.See section >> 3.2.2. for further details on NOTIFY message generation >> >> Is this a bug in the stack or am I missing something? >> >> Regards, >> Gauri >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> > > > > ------------------------------------------------------------------------ > > Subject: > [sipx-dev] sipXtapi - build environment on windows > From: > "Mahudeswaran" <[email protected]> > Date: > Fri, 7 Jan 2011 17:39:19 +0530 > To: > "sipXecs developer discussions" <[email protected]> > > To: > "sipXecs developer discussions" <[email protected]> > > > Hi, > > I need some help on setting up the sipXtapi build environment for > windows OS. And followed the instructions said in the below url, > > http://sipxtapi.sipfoundry.org/wiki/SipXtapi_Windows_Build_Environment > > The build solution completed with 32 errors and warnings, which is > attached in the err.txt file. > > Tried the steps mentioned as part of pre-requisites and etc… > > Any one experienced similar cases. > > Environment where I am building the sipXtapi is on windows7 (32bit) > and VS2005 standard edition. > > Suggestion: To whom we have to contact for any modification in the web > page. Modification related to the build instructions which makes the > user to clarify few points while reading. > > Regards > > Mahudeswaran > > ------------------------------------------------------------------------ > > _______________________________________________ > sipx-dev mailing list > [email protected] > http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
