Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"D" letter on PCM links

Status
Not open for further replies.

cuneyt2020

Technical User
Mar 9, 2004
147
TR
Hi all,
PBx is BC12 SP6 with 15 lim system. 1 week ago i realized that lots of channel on GJUL GJUG connections are used for D data channel...
I don't know the reason why it happens. Is there something wrong with configuration... In which cases "D" occurs on PCM links... Approximately half of the channels are "V" and half of them "D"
Here is print out for some of lims

[tt]
<gjtsp:lim=14,func=con;
GROUP JUNCTOR LINE TIME SLOT STATUS
64 CHANNELS INITIATED
SOURCE DESTINATION TRAFFIC CONNECTION TYPE TSCL
EQU EQU
14-1-00-1 7-1-00-19 BUSY OK D LBDV C321
14-1-00-2 1-0-00-28 BUSY OK V LBDV C321
14-1-00-5 8-0-00-24 BUSY OK V LBDV C321
14-1-00-6 9-0-00-11 BUSY OK D LBDV C321
14-1-00-8 15-0-00-8 BUSY OK V LBDV C321
14-1-00-13 15-0-00-21 BUSY OK D LBDV C321
14-1-00-14 1-1-00-18 BUSY OK V LBDV C321
14-1-00-17 BOOKED OK V LBDV C321
14-1-00-18 3-1-00-24 BUSY OK D LBDV C321
14-1-00-20 11-1-00-10 BUSY OK D LBDV C321
14-1-00-22 9-0-10-24 BUSY OK V LBDV C321
14-1-00-23 10-0-10-22 BUSY OK V LBDV C321
14-1-00-24 10-0-10-9 BUSY OK V LBDV C321
14-1-00-25 15-0-00-31 BUSY OK D LBDV C321
14-1-00-26 12-1-00-15 BUSY OK D LBDV C321
14-1-00-27 15-0-00-26 BUSY OK D LBDV C321
14-1-00-28 3-1-00-8 BUSY OK D LBDV C321
14-1-00-29 9-0-00-18 BUSY OK D LBDV C321
14-1-00-30 9-0-10-29 BUSY OK V LBDV C321


[/tt]

 
Yes i traced the channels marked with "D" letter with lscop command and saw that it's a voice call. But why isn't it marked with "V"?
Or in another saying , when does V happen and when does D happen on PCM link?
 
V = voice traffic
D = data traffic (like s0 calls or fax G4 calls)

--------------------------------------
What You See Is What You Get
 
Hi whos'rdady, whern i checked this traffic , i saw that these are the calls, retrieved from AS5350 gateway and the route number is route 68(SLP60).. I mean, branch office routers send the calls to AS5350 GW and GW sends it to Md110 through route68 PRI connection
I don't think these are fax calls ...Because there are lots of calls at the same time ,also we don't use ISDN extension or tlu79

RODAP and ROCAP of route 68 is,

[tt]
<rocap:ROU=68;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
68 0110000000000010 4 2000030001 0 30 128 00010115 111110000031 111101

END

<roDap:ROU=68;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
68 SL60 H'00000300 H'00000000 H'04310000 NO

END
[/tt]

Actually what i want to learn is, if there is a faulty config on md side? So that md thinks that this is a data connection or everything is ok??
 
Hi,
It could be calls from the analoge PSTN. A normal analoge PSTN call a ISDN number here the public set the BC value as 3.1 Khz. and in the MD this will be as a data call.
You can use numner conversion to change this kind off call to be voice.
 
anyway, it is normal traffic an no faulty config is involved....

--------------------------------------
What You See Is What You Get
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top