[asterisk-bugs] [LibSS7 0012484]: [patch] generic name support

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12484 
====================================================================== 
Reported By:                ptimmins
Assigned To:                mattf
====================================================================== 
Project:                    LibSS7
Issue ID:                   12484
Category:                   New/Feature
Reproducibility:            N/A
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0-beta7.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-20-2008 23:45 CDT
Last Modified:              04-21-2008 11:13 CDT
====================================================================== 
Summary:                    [patch] generic name support
Description: 
I have added support to libss7-trunk and made changes in chan_zap to fully
implement generic name support.

to send generic name, have a dialplan rule similar to:
exten => s,n,Set(_SS7_JIP=yourjip)
exten => s,n,Set(_SS7_GENERIC_NAME=${CALLERID(name)})
exten => s,n,Dial(Zap/g1/[callednumber])

If you receive a call with a generic name in the generic name field, it
populates the proper internal asterisk variables to display name in the
same way any other channel type would (ISDN PRI/SIP/etc)
====================================================================== 

---------------------------------------------------------------------- 
 ptimmins - 04-21-08 11:13  
---------------------------------------------------------------------- 
In the US it's quite uncommon. Generally caller id is retrieved via a TCAP
transaction against a caller id with name database. (using global title
translation, transtype 5). This however can sometimes be used in cap and
grow scenarios where one switch does the cnam dip, and then passes off some
of the customer traffic to an adjacent switch because the original one ran
out of capacity to add new subscribers, or can't handle a new subscriber
type (such as voip :) ). It's also handy if you are using asterisk as a
gateway to provide carrier voip to customers as there is no other way to
both use SS7 and have working caller id with name service. :)

In Canada, it's incredibly common, Canadian switches send caller id this
way almost exclusively. In fact, many switch manufacturers refer to using
the generic name field to transport caller id with name data as "Canadian
CNAM".


I vote for keeping it seperate, as if a switch sees generic name in the
IAM, it won't do a CNAM dip over TCAP and may have mismatching or invalid
caller id with name as a result. Since this IAM could cross network
boundaries, you usually don't want to set it, at least in the US, as it can
cause an annoyance where there is a mismatch between what you send and what
is in the CNAM database. It could be useful to make it a variable you can
override as well as a settable option in zaptel.conf, however, as this
behavior could be desirable in certain situations. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-21-08 11:13  ptimmins       Note Added: 0085756                          
======================================================================