On 9/9/07, <b class="gmail_sendername">Barton Fisher</b> <<a href="mailto:bart@icpage.com">bart@icpage.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks, OK, a bit confused.... The cards are TE410P. I really don't<br>see how the set a codec for this, other than it might default to<br>something in code like ulaw. Any clue on how to verify codec in use<br>during a call?
</blockquote><div><br>If you absolutely want to be sure, use 'pri intense debug span X' and watch for SETUP messages:<br><br>< Protocol Discriminator: Q.931 (8) len=62<br>< Call Ref: len= 2 (reference 542/0x21E) (Originator)
<br>< Message type: SETUP (5)<br>< [04 03 80 90 a2]<br>< Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Speech (0)<br>< Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16)
<br>< Ext: 1 User information layer 1: u-Law (34)<br>< [18 03 a9 83 95]<br>< Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan: 0<br>< ChanSel: Reserved
<br>< Ext: 1 Coding: 0 Number Specified Channel Type: 3<br>< Ext: 1 Channel: 21 ]<br><br>You'll see the voice characteristics in the Bearer Capability details (I have NI-2, this might be different for NI-2 or other PRI variants).
<br><br>But as others have mentioned, generally T1 PRI = uLaw, E1 PRI = aLaw.<br></div><br></div>-- <br>j.