I cannot help you with the .conf files on the * as I am brand new to the * and in the process of compiling the software now.
I do know this.. You have to make sure the the generic name IE (information element ) is being populated in the outbound ISDN setup message to Allegiance. If you have a protocol analyzer you could check this , or maybe Allegiance an check this for you. At any rate, they should get this parameter inbound from you ISDN and then pass this parameter to the PSTN (most likely via ISUP). I would get with Allegiance and make sure they are setup to pass CNAM to the PSTN with you. Or you can tell them what ANI/CPN you are sending and they probably store with an SS7 provider , and they can update the SCP for the desired name that you want for any ANI. There might be a cost for this... This last option is the cleanest way to do it. I currently do this for customer's that have PRI PBX's and sit on my switch with a T-1 Kyle On Wed, 2004-04-07 at 12:30, Ryan Thrash wrote: > Wow... talk about a detailed response; thanks! > > In our situation, we've got a T-1 voice PRI from Allegiance Telcom. For > the benefit of those of us who aren't as in the know as you are (and > who have no affiliation with a CLEC), is there a way to be able to > control what gets sent out as our name portion of the Caller ID (even > if it means changing what's recorded at Allegiance)? We somehow manage > to do so with the number part. > > In other words, type real slow and mention specific conf files if > possible. This is pretty new stuff for me... Thanks again! > > -- > Ryan > > On Apr 6, 2004, at 7:59 PM, Kyle Thomas wrote: > > > > > SCP=Service control point (database that houses name to number) > > SCP DIP = Query to an SCP via the SS7 network > > ISUP = SS7 signaling for call setup and teardown (equivalent of > > invite,ringing,ok,bye) > > IAM = Initial address message (equal to the SIP invite ) > > LNP= Local number portability (uses the SS7 network as a backbone). > > This > > let's people keep thier phone number and switch service providers. > > > > There is nothing quick about "quick caller id". The far end Telco will > > override the name infomration sent to the PSTN and perform thier dips > > regardless, overwriting the info you are trying sending out. We are a > > CLEC so, > > therefore we store, therefore it works.. > > > > On Tue, 6 Apr 2004, Andrew Kohlsmith wrote: > > > >>> The terminating telco is doing an SCP dip to thier local SCP's and > >>> the > >>> database probably does not have that name mapped to this number. > >> > >>> First thing to do is make sure the generic name ISUP optional > >>> paramter is > >>> set in the outgoing IAM / ISDN setup from your GW. > >> > >>> You could also store with an SS7 provider , if these are ported > >>> numbers > >>> you are sending out make sure that the CNAM field in the LNP line > >>> record > >>> is set to the point code alias of the provider you are storing with. > >>> The > >>> terminating switch will first do an LNP dip to see what CNAM alias to > >>> launch the CNAM dip to. If that is not found , will default to the > >>> local > >>> SCP thus not finding your record. > >> > >> Ok, and now for the rest of us... > >> > >> SCP? SCP dip? ISUP? IAM? LNP? > >> > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- Kyle Thomas Director of Engineering Monmouth Telephone 732-704-1000 x 130 _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
