[asterisk-bugs] [LibPRI 0010321]: ISO Path Replacement (ANF-PR ) - InvoceID mismatch

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10321 
====================================================================== 
Reported By:                worta
Assigned To:                mattf
====================================================================== 
Project:                    LibPRI
Issue ID:                   10321
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.9  
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 438 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-27-2007 07:49 CDT
Last Modified:              08-31-2007 16:41 CDT
====================================================================== 
Summary:                    ISO Path Replacement (ANF-PR ) - InvoceID mismatch
Description: 
We're using libpri (438) with ANF-PR to connect our HiPath 4000 to Asterisk
1.4.9/ zaptel 1.4.4

Asterisk: pri_cpe, qsig 
HiPath4k: master, ecmav2

Path Replacement does not work because of a mismatched InvokeID, which
makes it unable for the HiPath to identify related calls. 

Call Flow is: HiPath(ext. 3892) => Asterisk => HiPath(ext. 5962)



====================================================================== 

---------------------------------------------------------------------- 
 mattf - 08-31-07 16:41  
---------------------------------------------------------------------- 
Also, in regards to the possibility that it's a problem relating to the
invoke ID, from my reading (Q.932 and other specs) the invoke identifier
value itself is never declared to have to start counting with a certain
value, just as long as it is chosen in a way that would not confuse it with
other invoke ids that could be still pending or unacknowledged.  The value
of 11 is not used anywhere else in that trace, so from my understanding of
the specs it would seem that that is a perfectly valid value for an invoke
identifier. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-31-07 16:41  mattf          Note Added: 0069806                          
======================================================================