[Home]

Summary:ASTERISK-03952: [request] Outbound Calling Name by FACILITY IE
Reporter:wsandiford (wsandiford)Labels:
Date Opened:2005-04-18 16:11:09Date Closed:2005-05-11 22:39:22
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) calltrace.txt
( 1) calltrace2.txt
( 2) calltrace3.txt
( 3) cisco-debug-isdn-q931.txt
( 4) cisco-debug-isdn-q931-detail.txt
( 5) cname_1.txt
( 6) pri_cpe_cnam.diff
Description:Currently, it is possible to receive calling name by Facility IE but not possible to send it out by Facility IE.  This is required to send proper calling name out to either legacy PBXs or to carriers.
Comments:By: Paul Cadach (pcadach) 2005-04-20 04:18:32

Could you answer to next questions:
1) Which switchtype you uses?
2) Is Asterisk network or CPE side on PRI link where transmission of Caller name is required?
3) Is any documentation of caller name transmission from CPE side is available?

edited on: 04-20-05 04:19

edited on: 04-20-05 06:28
By: wsandiford (wsandiford) 2005-04-20 09:00:46

1) switchtype=national
2) signalling=pri_cpe (for my situation, but theoretically it could be network)
3) I am sure that there is, but I don't have it.  It is probably simliar to the inbound transmission of Caller Name by Facility IE.  A patch/fix was made by mattf for that about a month or so ago along with some MWI fixes he did.  Here is the link to that bugfix.

http://bugs.digium.com/bug_view_page.php?bug_id=0003554

edited on: 04-20-05 09:07
By: Matthew Fredrickson (mattf) 2005-04-20 10:54:53

If you can get a spec for it or a trace of it happening, we might be able to do something with that.  Otherwise, we can't really do anything.
By: Matthew Fredrickson (mattf) 2005-04-20 10:56:14

Oh, the patch/fix didn't get it working (as far as we could tell).  It was just a guess to see if adding the same type of message to the CPE side outgoing call SETUP worked.
By: lesnet (lesnet) 2005-04-20 18:51:09

I used to be able to send caller name (via 0x1C Facility message).  This stopped working some months ago after numerous CVS updates.  I'm unable to find the old working source code.

I've attached an incoming pri debug on the facility message that is received.

I spoke with my carrier who performed a trap on my outbound call.  They said setting the DISPLAY 0x28 is not valid for setting caller name.

Example Incoming Facility Message: Callername = THE FYXX ESPRES
< [1c 1d 9f 8b 01 00 a1 17 02 01 01 02 01 00 80 0f 54 48 45 20 46 59 58 58 20 45 53 50 52 45 53]
< Facility (len=31, codeset=0) [ 0x9f, 0x8b, 0x01, 0x00, 0xa1, 0x17, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0f, 'THE', 0x20, 'FYXX', 0x20, 'ESPRES' ]

The outbound callername must also be contained inside the facility message.

FYI: A facility message with no callername set is as follows;
< [1c 15 9f 8b 01 00 a1 0f 02 01 01 06 07 2a 86 48 ce 15 00 04 0a 01 00]
< Facility (len=23, codeset=0) [ 0x9f, 0x8b, 0x01, 0x00, 0xa1, 0x0f, 0x02, 0x01, 0x01, 0x06, 0x07, 0x2a, 0x86, 'H', 0xce, 0x15, 0x00, 0x04, 0x0a, 0x01, 0x00 ]



Hope these comments help a little.
By: wsandiford (wsandiford) 2005-04-20 21:38:32

I've attached 2 files that show examples of outbound Calling Name being correctly sent by Facility IE on a cisco gateway that I have.

The first file is a standard q931 debug of a test call and the second file is a detailed q931 debug.  In both cases the calling name was Peter Pan

I hope this helps.

Oh, I don't know if I need to mention this or not but neither call was answered.

edited on: 04-20-05 21:40
By: Matthew Fredrickson (mattf) 2005-04-21 14:19:01

Hrm... that's interesting.  It looks like it's basically sent in the same way as it is sent from the PRI_NET side.  Try applying this patch to your libpri and tell me if it works for you.
By: lesnet (lesnet) 2005-04-21 14:47:20

I just applied this patch.

The FACILITY IE Message is being sent, but it does not appear to contain the callername

   -- Executing SetCIDName("Zap/1-1", "LES NET 1996") in new stack

< [1c 0e 9f 8b 01 00 a1 08 02 01 01 02 01 00 84 00]
By: Matthew Fredrickson (mattf) 2005-04-21 15:06:02

I got an email from you, does it work or does it not?
By: wsandiford (wsandiford) 2005-04-21 15:15:32

I applied the patch, make clean, make install and restarted asterisk and it doesn't appear to be working.  (trace attached)
By: Matthew Fredrickson (mattf) 2005-04-21 15:38:07

That's weird.  Are you sure that you did everything correctly?  make clean; make install on libpri.  Also verify that your calleridname variable is actually set.
By: Matthew Fredrickson (mattf) 2005-04-21 15:38:48

You might even want to recompile asterisk and chan_zap as well.
By: wsandiford (wsandiford) 2005-04-21 16:26:16

I'm pretty sure its set, because I am seeing it in the Progress Message.

I will will try it again
By: wsandiford (wsandiford) 2005-04-21 17:01:54

Still not working.

did a make clean; make install; on zaptel, libpri (patched), and asterisk, then rebooted the whole system.

Still appears to be trying to send via the Progress message.  CIDName is definately set.

Uploaded calltrace2.txt with most recent attempt.  Most likely same contents.  I don't see a 1c facility message at all in my traces.
By: Matthew Fredrickson (mattf) 2005-04-21 17:09:02

try updating now and see if it works now.  I'd forgotten to change the message that it was sent in to the SETUP message instead of FACILITY
By: wsandiford (wsandiford) 2005-04-21 21:31:42

Updated from CVS as per mattf's instructions and it worked!!!!

Uploaded calltrace3.txt to show the successful trace.

Thanks Matt!!!!
By: Matthew Fredrickson (mattf) 2005-04-22 01:43:46

Fixed in head
By: Russell Bryant (russell) 2005-05-11 22:39:21

mattf says that this is not applicable to 1.0