[libpri-commits] kpfleming: branch 1.4 r594 - in /branches/1.4: libpri.h pri_internal.h

SVN commits to the libpri project libpri-commits at lists.digium.com
Tue Jul 22 17:36:25 CDT 2008


Author: kpfleming
Date: Tue Jul 22 17:36:25 2008
New Revision: 594

URL: http://svn.digium.com/view/libpri?view=rev&rev=594
Log:
correct comments to match code

Modified:
    branches/1.4/libpri.h
    branches/1.4/pri_internal.h

Modified: branches/1.4/libpri.h
URL: http://svn.digium.com/view/libpri/branches/1.4/libpri.h?view=diff&rev=594&r1=593&r2=594
==============================================================================
--- branches/1.4/libpri.h (original)
+++ branches/1.4/libpri.h Tue Jul 22 17:36:25 2008
@@ -624,7 +624,7 @@
 /* Send call proceeding */
 int pri_proceeding(struct pri *pri, q931_call *c, int channel, int info);
 
-/* Enable inband progress when a RELEASE is received */
+/* Enable inband progress when a DISCONNECT is received */
 void pri_set_inbanddisconnect(struct pri *pri, unsigned int enable);
 
 /* Enslave a PRI to another, so they share the same call list

Modified: branches/1.4/pri_internal.h
URL: http://svn.digium.com/view/libpri/branches/1.4/pri_internal.h?view=diff&rev=594&r1=593&r2=594
==============================================================================
--- branches/1.4/pri_internal.h (original)
+++ branches/1.4/pri_internal.h Tue Jul 22 17:36:25 2008
@@ -65,7 +65,7 @@
 	int tei;
 	int protodisc;
 	unsigned int bri:1;
-	unsigned int acceptinbanddisconnect:1;	/* Should we allow inband progress after RELEASE? */
+	unsigned int acceptinbanddisconnect:1;	/* Should we allow inband progress after DISCONNECT? */
 	
 	/* Q.921 State */
 	int q921_state;	




More information about the libpri-commits mailing list