Hello Everybody ..(sorry for my english)
Im having a problem with a cisco AS5400 and my isdn provider.
I can't recognize a payphone call.I mean that I can recognize the OLI (origination line information)
to know the origination line type.
I have configured the GTD as cisco describes here http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftgtdisd.htm.
this is my conf .. I have a T3 ,so i configured 28 T1 and 28 serial interfaces.
I only need to receive calls so i don't use voice ports to outgoing calls.
controller T3 6/0
clock source line
t1 1-28 controller
controller T1 6/0:1
pri-group timeslots 1-24
trunk-group NY timeslots 1-24
no ip address
isdn switch-type primary-ni
isdn incoming-voice modem
no isdn incoming alerting add-PI
no cdp enable
isdn ie oli 37
I debuged the isdn to analize an incoming packet when a call is from a payphone.
This is the packet:
6w0d: ISDN Se6/0:26:23 Q931: RX <- SETUP pd = 8 callref = 0x0144
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9838A
Exclusive, Channel 10
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x2183, '2019439707'
Called Party Number i = 0xA1, '8004010562'
Transit Net Select i = 0xA1, '340'
Locking Shift to Codeset 6
Codeset 6 IE 0x37 i = 0x04, 'r'
6w0d: ISDN Se6/0:26:23 Q931d: L3IF_rx_L2_pak: received data
Here i can see de OLI (origination line information) in the last four bytes of the isdn packet:
In my configuration I used "isdn ie oli 37" so the cisco can recognice the oli and try to parse it:
so ,we have
"37" oli ie identificator.
"02" size of the oli info (2 bytes)
0472 oli info. where 72 means the origination line type. payphone must be in this case but
"72" isn't in the cisco doc that I posted above.
In the cisco doc they tell that payphone is:
27payphone using coin control signaling
so 0x72 .. must be 0x27 .. the byte is reversed.
I think thats my problem ,but i didn't find anything to reverse the byte again to obtain an 0x27..
somebody know how to fix it?.