On 02/05/2005 at 22:49 Olle E. Johansson wrote: >> Then surely it would map correctly, and thus be ok with HANGUPCAUSE.. >adding >> SIPHANGUPCAUSE means you have to know that it was a SIP call - most of >the time >> no one cares what type of call it was and using HANGUPCAUSE means you >can use generic >> routines. >> >Right, but there's been quite a lot of questions about SIP error/hangup >codes from a lot of users, so I see no harm in implementing a function >to read it as well as correcting the SIP support for HANGUPCAUSE. >
ahh ok, so you're adding a specific SIPHANGUPCAUSE along with mapping the HANGUPCAUSE so that if some people want to look at what happened in the SIP world then can... My mistake, I thought you weren't doing both, but were just going to add the SIP extension.. Andy _______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
