Researching an ISDN developer- Job offer

[mastar]

I have a requirement to develop and market using a single ISND BRI line.. Currently we're using ISDN phones (rather 2 ISDN phones). One of the phones options for serial port that deliverers the necessary data to our VB application so 2 operators can answer incoming calls using the 2 voice channels on the BRI and several call appearance configured also on this single BRI line..

This all works fine providing the telephone company can supply RND or the redirected number..( the client forwarding their calls to our service, we need this RND forwarded#) and for 5ES switches they can usually do so with no problems..

But for the DMS-100 its a 50% chance if the teleco DMS100 has all the hardware options or knows what or how to provision the options.. In this case the client ends up loosing because they purchase $1000 worth of phones and go the complete cycle ordering the line and after a considerable amount of frustration, the teleco does not provide and both the client and ourselves with the proper data for our application and we both loose business time and money.

I am aware, was told by my ex-programmer who research on Ebay and found a simple ISDN, actually an endless supply or $20 ISDN cards for a PC ($200 new) Whatever, he withheld the source, data and research thus I am, as the owner here starting over.. To find another developer that can break the ice and accomplish this feat in the near future.. or someone I can resell this item for.. either way... no problem as long as I have the technical info if you decide to quit on my project or business down the road!

Here's what I know to solve the above situation or DMS-199 problem or those switches that do not supply the RND.. That.. my clients can purchase from the phone company MADA's or multiple access directory appearances.. such as many actual phone#'s forwarding these to the ISDN... The client would supply one known MADA # to there client and their clients would still forward their calls to that specified MADA#..

This ISDN card would receive this information (the called#), a VB application will decipher it and route the call to either of several available PC of choice available... Here's is the hard part but it is possible... the Voice channel or incoming call will or needs to be converted to the sound card so the operator can pick up the call using headsets!!!!

I am not fully understanding some of this maybe to explain it fully, mostly because I am talking conceptual from listening to another person talking about this extensively already. I am not fully qualified to really know what I am taking about but the programmer really did know what he was talking about convincing me that this is realistically workable situation..

Anyone of knowledge or interested please reply rod@mastar.com and visit my website whereas it discusses our applicatio, how long I been in the business and what I fully offer, ISDN/DID messaging software..

 

[ISDNman]

1) Are you in the USA/Canda or Europe?

Since you are talking 5ESS and DMS-100 I'll assume in the USA.

I hate to admit it, but I do not know what you mean by "RND" nor is this acronym in Newton's Telecom Dictionary (Nor is RDN).

I would guess it is really RDN = Redirecting Direcotry Number?

I assume calls coming in DO include the Called Party Number as well as the Calling party Number.

If I understand your applications the callers call a number, the number is redicrected to your BRI. You need the number originally dialed, not the number of the BRI.

I assume you cannot use the actual BRI numbers because your customers have many different lines being forwarded and the redirected number allows your software to customize how agents respond.

The problem with USA BRI in general is that it supports infinity minus one features and any feature may or may not be tarrifed and ordering can be a mess too.

Looking at the National ISDN-1 specs I do not see provisions for a redirecting address in a call setup message.

I do see this mentioned in the DMS docs. I do not see it in the 5ESS docs.

I believe this exists in Europ ISDN but did not check.

So I have lots of questions

Is the problem on the forwarding end or at the destination end?

When this does work do you get a "redirecting number" information element in the incoming BRI call setups?

Are you have seen this work with both switches? If so what was the protocol in each case (e.g. for 5ESS NI-1, NI-2, or Custom Multipoint for DMS NI-1, NI-2 or Custom)?

If you HAVE seen this on NI-2 or NI-2 onb both switches then what you need to do is write up a better ISDN provisioning sheet for your product.

Sorry not to be of more asistance/

 

[mastar]

FIRST OF ALL THANKS FOR YOUR REPLY... its much appreciated There maybe only a few techs out there in ISDN world that know what I am doing.. something very specific, even the telco don't get it... THEY THINK... ISDN MODEMS, Internet when we talk..

HEY SAY daaaaaa 'Why would you want to have the RND # received anyways? WELL i happened to be in a nitch specialized business... I have 3 competitors $15K/35K$ systems each doing what I am doing

We are 3% of the market.. most Answering Services use DID or direct Inward Dialed teleco lines and DID hardware!!! costing gobs of money, and gobs of monthly telco charges.. selling 20K$ to 80K$ systems. ISDN is perfect for any service and is cost effective... IT WORKS BEST being digal vs/ analog voice quality, patching etc..


Answering your questions
--------------------------

Sorry, I am in the USA, i know ISDN is different outside.
In my msg... I do say RND mean "The redirected number" such as... " A doctors office forwards there calls after hours to a answering service.. Then a caller patience calls the doctors office.

Caller ID is the patience, RND is the doctors number
We need the doctors# to give the proper answering service answer phrase for the client

The problem is at the phone switch not sending the RND.. the call comes through fine but we can not answer it properly

And when it does work on CERTIN DMS100's we do get the RND. Always it appears or works when using 5ESS... and if the client or doctors office town, city or particlar switch is using a DMS100 configured properly we always get the RND there too but some towns or cities using the DMS100.. they just can't figure out or understand how to configure their own switch or if the switch has the correct hardware to do so for us and their client (OUR CLIENT)



>>>If so what was the protocol in each case (e.g. for 5ESS NI-1, NI-2, or Custom Multipoint for DMS NI-1, NI-2 or Custom)?

This is were I AM WEAK AT UNDERSTANDING? i do not know the termology here your asking... or what to ask the teleco they are configured as



>>>>>>If you HAVE seen this on NI-2 or NI-2 onb both switches then what you need to do is write up a better ISDN provisioning sheet for your product.


This is were I AM WEAK AT UNDERSTANDING?
Our product is very simple... the ISDN phones we only support from the company called "TONE COMMANDER" has a serial port underneath we grab reading the data...

Basically we recieve data such as..
PARTY, 01,01 4081234444

PARTY, 01,02 4081234444

PARTY, 01,03 4081234444


The last one of the 3 samples 3rd parameter the ' 03 '
...meaning the RND or this phone# is the redirected number..

From certain DMS100 we do not get 03... but maybe it be 01


ANYONE OUT THERE IN

http://WWW world

that can help... We can teach the tele how to... so what we are considering is designing a ISDN PC CARD option that don't card about RND..

Our client will order 100 MADN# muliple appearance directory numbers forwarded to the primary SPID#.. Then assign there clients one of these 100 numbers.. The client will forward to one of the MADN#.... This we can handle... but its a development project and a high ticket option we can sell our clients if there town or citiy or switch does not work!!!!

CAN ANY ONE FIGURE THIS OUT???

 

[ISDNman]

Trying to deal wityh variations at your client's clients end (e.g. at the end where the Dr's Offices are located) is, in the long run, futile.

Get multiple DN's on your clients BRI's seems like a perfectly good approach, at least in theory.

I spoke to a freind at SBC and he said you should be able to get a fair number of DNs on each BRI. He could not say for certain, but it seems likely the number you can get will depend on what switch the BRI is on (e.g. DMS, 5ESS or EWSD). Additionally, this may very soemwhat depending on local tarrifs.

You will need to contact various ISND providers to determine: 1) How many DN's they can provide 2) How best to order a line with more than the typical 2 DN's.

Tone COmmander may be able to help you.

You then will need to provide a "Guide to ordering ISDN" for your customers that will guide them through the process. Soemthing like the "Ordering ISDN BRI..." ordering guide here:

http://www.telos-systems.com/support/csb.htm

It seems that some carriers are beginning to cut back on BRI support. Therefore another option would be to use PRI (PRI support is still very strong with the Telcos). On a PRI you can get any number of DN's you wish.

In both these cases the Dr would forward his/her calls to a specifically assigned DN or the BRI (or PRI) and your software would look up client's name and answering script using that number versus the redirecting number

Best of luck.