[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:53 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)
====================================================================== 

---------------------------------------------------------------------- 
 mattf - 04-21-08 11:53  
---------------------------------------------------------------------- 
I made a couple of modifications to your libss7 portion of the patch to
make it (from an API perspective) a little more robust.  It will break your
chan_zap though, but I think the changes to fix it should be pretty easy. 
I'll upload it so you can try it out to make sure it doesn't break
anything.

Let me know when you've got a diff of the chan_zap portion, and we'll work
on that then. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-21-08 11:53  mattf          Note Added: 0085760                          
======================================================================