Hello all,
I have tries several PRI/ISDN protocols to talk to a Samsung PBX (Model IDCS 100).
I think NT1 is the only one we can use to simulate the network (CO) but that one doesn't work at all.
The only one that works half way is NE1 but the PBX seems not to recognize the DNIS. ANI is fine, the call is connected, audio is fine, hangup but no DNIS so after I send the call there is a 9 seconds delay before accepted and since there is no DNIS, my call is sent to a general group and not to the correct one.
Should the NE1 prm file be modified to deliver the correct DNIS and how; or must I use NT1 and try to find the correct PRI/ISDN parameters ?
Anybody with experience connecting to a Samsung ?
I have been fighting these issue for 4 days already and the customer is about to call it off. Any help is greatly appreciated.
Thanks,
C. Bieberach
Hello,
NT1 is a network simulator for T1 PRI protocols, so it won't help in your case. ne1.prm doesn't have provision for DNIS, it is set by the application; the DNIS, by default, is the same as you provide in gc_MakeCall as a called number. It appears in Called Number IE in the SETUP message; if your PBX needs this number in some other IE, it also can be configured at the application level. If you have an example of good call in terms of PRI trace, I will probably be able to help you to code this part . It assumes that you have an access to the source code of the application; there is no external config option to acieve this.
Thank you Leonid,
If NT1 is a network simulator, insn't that what I need ? I have to simulate the phone company in this case. The PBX is NI2. Maybe I am not providing the clock.
With NE1 I get connected to the PBX ok. Sound is ok, DTMF is ok but I do not deliver the DNIS therefor the PBX sends me to a default Group and not to the one I indicate on my DNIS, obviuosly because the PBX is not getting my DNIS. So after 9 seconds of the line seizure, I get the message "call accepted" and sent to a default group.
This is a copy of a call. This program is written in VOS6:
120116 122347.0 ISDN board 1 has 24 time-slots120116 122347.0 ISDN board 2 has 24 time-slots120116 122347.2 @D Dev 98 dtiB2 Evt 0x82e Report D-channel status to the user 120116 122351.0 isdnout:0201[0] @D dt_getxmitslot(99, 0x85dc90)=0, slot=52120116 122351.0 isdnout:0219[0] @D dx_getxmitslot(2, 0x85dc90)=0, slot=0120116 122351.0 isdnout:0224[0] @D dx_clrdigbuf(2)=0120116 122351.0 isdnout:0238[0] @D dx_getxmitslot(2, 0x85dc90)=0, slot=0120116 122351.0 isdnout:0238[0] @D dt_listen(99, 0x85dc90)=0, slot=0120116 122351.0 isdnout:0238[0] @D dt_getxmitslot(99, 0x85dc90)=0, slot=52120116 122351.0 isdnout:0238[0] @D dx_listen(2, 0x85dc90)=0, slot=52120116 122351.0 isdnout:0259[0] @D cc_MakeCall(99, 0x8607f0, 6320, 0xd6f978, 0, 32768)=0120116 122351.1 @D Dev 99 dtiB2T1 Evt 0x827 Call state changed to proceeding 120116 122401.3 @D Dev 99 dtiB2T1 Evt 0x821 Connection request accepted 120116 122409.6 @D Dev 99 dtiB2T1 Evt 0x822 Destination answered the request 120116 122412.6 @D Dev 2 dxxxB1C1 Evt 0x81 Play Completed Data 0x41 Terminating digit 120116 122412.6 @D Dev 2 dxxxB1C1 Evt 0x83 Get Digits Completed Data 0x1 Max Digits 120116 122412.6 isdnout:0485[0] @D dx_clrdigbuf(2)=0120116 122415.5 isdnout:04cc[0] @D cc_DropCall(0x80000001, 16, 0x8000)=0120116 122415.7 @D Dev 99 dtiB2T1 Evt 0x805 xx_DropCall is completed 120116 122415.7 @D cc_ReleaseCall(0x80000001)=0
Should I send a message right after "Call state changed to proceeding" ? Is yes, what is the cc_ command ?
Thank you very much Leonid for your help.
Carlos Bieberach
Leonid,
I have attached a log file using NT1, next I will send NE1.
I beleive it is a binary log file created from cc_ functions. I do not know how to read these log files. Let me know if this type of log file are of any use.
Carlos
Attached is the NE1 log file.
Thanks a lot again,
Carlos,
If the PBX runs NI2, you need to use NT1 on your side. In the Dialogic/bin folder you can find pritrace.exe, this utility decodes the binary traces and places it in a *.res file in a readable format; please run it on trace_nt1.log and send me the output. I'd do it myself, but it looks like I don't have the right version of that utility for your setup. Or just send me the pritrace.exe, I will decode the files then.
Can't get this pritrace.exe tool to work correctly.
Attached is the pritrace.exe I am using.
Hello Leonid,
Finally I was able to open the res file. I had to rename it .txt since this web site doesn't allow me to upload .res file. Here is the text and also an attached copy.
At this point, since the technitian of the PBX can not help because he doesn't know anything about PRI, protocols, etc., I am shutting in the dark using isdiag.exe, very frustrating. I am sure we all have been there more than once.
Hope you can see something in this log file. I think more than one attemp shows in this text.
Thanks again,
Trace Start Time : 1/21/2012, 15:41:43.875PRI UNKNOWN PROTOCOL
CORRUPT DATA ENCOUNTERED:65 TIME STAMP: 1/21/2012, 15:41:43.875RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x45 Receive Ready
TIME STAMP: 1/21/2012, 15:41:43.875 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x65 Receive Ready
TIME STAMP: 1/21/2012, 15:41:49.875RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x45 Receive Ready
TIME STAMP: 1/21/2012, 15:41:49.875 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x65 Receive Ready
TIME STAMP: 1/21/2012, 15:41:55.875RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x45 Receive Ready
CORRUPT DATA ENCOUNTERED: 50
CORRUPT DATA ENCOUNTERED:05 2F 4A 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02
TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x65 Receive Ready
TIME STAMP: 1/21/2012, 15:42:1.875RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x45 Receive Ready
TIME STAMP: 1/21/2012, 15:42:1.875 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x44 0x64 Information Dest=0 CR=0x0013 SETUP(0x05) 1: BEARER CAPABILITY(0x04) 2: IE Length(0x02) 3: 1------- Extension Bit -00----- Coding Standard ---00000 Info. Transfer Cap. -00----- Transfer Mode ---10000 Info. Transfer Rate 1: CHANNEL ID(0x18) 2: IE Length(0x04) 3: 1------- Extension Bit -1------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. *Unknown IE: 0x80 *Unknown IE: 0x83 *Unknown IE: 0x81 1: NETWORK SPEC. FAC.(0x20) 2: IE Length(0x02) 3: 0x00 Length Of Network ID *Unknown IE: 0xe3 2: IE Length(0x09) 3: 0------- Extension Bit -010---- Type Of Number ----0001 Numbering Plan ID €9933000 Number Digit(s) 1: CALLING PARTY SUBAD(0x6d) 2: IE Length(0x05) -000---- Type of Subaddress 2: IE Length(0x05) 3: 1------- Extension Bit -000---- Type of Number ----0000 Numbering plan ID 6320 Number Digit(s) 1: CALLED PARTY SUBADD(0x71) 2: IE Length(0x05) 3: 1------- Extension Bit -000---- Type of Subaddress 0x50 Subaddress Info. 0x34 Subaddress Info. 0x35 Subaddress Info. 0x36 Subaddress Info.
TIME STAMP: 1/21/2012, 15:42:4.219RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x46 Receive Ready
TIME STAMP: 1/21/2012, 15:42:4.227RECEIVEResponse=0 SAPI=0x00TEI=0x000x64 0x46 InformationOrig=1 CR=0x8013STATUS(0x7d) 1: CAUSE(0x08) 2: IE Length(0x03) 4: 1------- Extension Bit 5: 0x20 Diagnostic 1: CALL STATE(0x14) 2: IE Length(0x01)
TIME STAMP: 1/21/2012, 15:42:4.227 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x01 0x66 Receive Ready
TIME STAMP: 1/21/2012, 15:42:4.227 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x46 0x66 Information Dest=0 CR=0x0013 RELEASE(0x4d) 1: CAUSE(0x08) 2: IE Length(0x02) 4: 1------- Extension Bit
TIME STAMP: 1/21/2012, 15:42:4.235RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x48 Receive Ready
TIME STAMP: 1/21/2012, 15:42:4.235RECEIVEResponse=0 SAPI=0x00TEI=0x000x66 0x48 InformationOrig=1 CR=0x8013CALL PROCEEDING(0x02) 1: CHANNEL ID(0x18) 2: IE Length(0x03) 3: 1------- Extension Bit -0------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. *Unknown IE: 0x83 *Unknown IE: 0x81
TIME STAMP: 1/21/2012, 15:42:4.235 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x01 0x68 Receive Ready
TIME STAMP: 1/21/2012, 15:42:4.235RECEIVEResponse=0 SAPI=0x00TEI=0x000x68 0x48 InformationOrig=1 CR=0x8013RELEASE COMPLETE(0x5a) 1: CAUSE(0x08) 2: IE Length(0x02) 4: 1------- Extension Bit
TIME STAMP: 1/21/2012, 15:42:4.235 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x01 0x6a Receive Ready
TIME STAMP: 1/21/2012, 15:42:4.235 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x6b Receive Ready
TIME STAMP: 1/21/2012, 15:42:10.235RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x49 Receive Ready
TIME STAMP: 1/21/2012, 15:42:10.235 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x48 0x6a Information Dest=0 CR=0x0014 SETUP(0x05) 1: BEARER CAPABILITY(0x04) 2: IE Length(0x02) 3: 1------- Extension Bit -00----- Coding Standard ---00000 Info. Transfer Cap. -00----- Transfer Mode ---10000 Info. Transfer Rate 1: CHANNEL ID(0x18) 2: IE Length(0x04) 3: 1------- Extension Bit -1------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. *Unknown IE: 0x80 *Unknown IE: 0x83 *Unknown IE: 0x81 1: NETWORK SPEC. FAC.(0x20) 2: IE Length(0x02) 3: 0x00 Length Of Network ID *Unknown IE: 0xe3 2: IE Length(0x09) 3: 0------- Extension Bit -010---- Type Of Number ----0001 Numbering Plan ID €9933000 Number Digit(s) 1: CALLING PARTY SUBAD(0x6d) 2: IE Length(0x05) -000---- Type of Subaddress 2: IE Length(0x05) 3: 1------- Extension Bit -000---- Type of Number ----0001 Numbering plan ID 6320 Number Digit(s) 1: CALLED PARTY SUBADD(0x71) 2: IE Length(0x05) 3: 1------- Extension Bit -000---- Type of Subaddress 0x50 Subaddress Info. 0x34 Subaddress Info. 0x35 Subaddress Info. 0x36 Subaddress Info.
TIME STAMP: 1/21/2012, 15:42:11.899RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x4a Receive Ready
TIME STAMP: 1/21/2012, 15:42:11.907RECEIVEResponse=0 SAPI=0x00TEI=0x000x6a 0x4a InformationOrig=1 CR=0x8014STATUS(0x7d) 1: CAUSE(0x08) 2: IE Length(0x03) 4: 1------- Extension Bit 5: 0x20 Diagnostic 1: CALL STATE(0x14) 2: IE Length(0x01)
TIME STAMP: 1/21/2012, 15:42:11.907 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x01 0x6c Receive Ready
TIME STAMP: 1/21/2012, 15:42:11.907 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x4a 0x6c Information Dest=0 CR=0x0014 RELEASE(0x4d) 1: CAUSE(0x08) 2: IE Length(0x02) 4: 1------- Extension Bit
TIME STAMP: 1/21/2012, 15:42:11.915RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x4c Receive Ready
TIME STAMP: 1/21/2012, 15:42:11.915RECEIVEResponse=0 SAPI=0x00TEI=0x000x6c 0x4c InformationOrig=1 CR=0x8014CALL PROCEEDING(0x02) 1: CHANNEL ID(0x18) 2: IE Length(0x03) 3: 1------- Extension Bit -0------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. *Unknown IE: 0x83 *Unknown IE: 0x81
TIME STAMP: 1/21/2012, 15:42:11.915 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x01 0x6e Receive Ready
TIME STAMP: 1/21/2012, 15:42:11.915RECEIVEResponse=0 SAPI=0x00TEI=0x000x6e 0x4c InformationOrig=1 CR=0x8014RELEASE COMPLETE(0x5a) 1: CAUSE(0x08) 2: IE Length(0x02) 4: 1------- Extension Bit
TIME STAMP: 1/21/2012, 15:42:11.923 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x01 0x70 Receive Ready
TIME STAMP: 1/21/2012, 15:42:11.923 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x71 Receive Ready
TIME STAMP: 1/21/2012, 15:42:17.923RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x4d Receive Ready
TIME STAMP: 1/21/2012, 15:42:17.923 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x4c 0x70 Information Dest=0 CR=0x0015 SETUP(0x05) 1: BEARER CAPABILITY(0x04) 2: IE Length(0x02) 3: 1------- Extension Bit -00----- Coding Standard ---00000 Info. Transfer Cap. -00----- Transfer Mode ---10000 Info. Transfer Rate 1: CHANNEL ID(0x18) 2: IE Length(0x04) 3: 1------- Extension Bit -1------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. *Unknown IE: 0x80 *Unknown IE: 0x83 *Unknown IE: 0x81 1: NETWORK SPEC. FAC.(0x20) 2: IE Length(0x02) 3: 0x00 Length Of Network ID *Unknown IE: 0xe3 2: IE Length(0x09) 3: 0------- Extension Bit -010---- Type Of Number ----0001 Numbering Plan ID €9933000 Number Digit(s) 1: CALLING PARTY SUBAD(0x6d) 2: IE Length(0x05) -000---- Type of Subaddress 2: IE Length(0x05) 3: 1------- Extension Bit -000---- Type of Number ----0001 Numbering plan ID 6320 Number Digit(s) 1: CALLED PARTY SUBADD(0x71) 2: IE Length(0x05) 3: 1------- Extension Bit -000---- Type of Subaddress 0x50 Subaddress Info. 0x34 Subaddress Info. 0x35 Subaddress Info. 0x36 Subaddress Info.
TIME STAMP: 1/21/2012, 15:42:21.395RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x4e Receive Ready
TIME STAMP: 1/21/2012, 15:42:21.395RECEIVEResponse=0 SAPI=0x00TEI=0x000x70 0x4e InformationOrig=1 CR=0x8015STATUS(0x7d) 1: CAUSE(0x08) 2: IE Length(0x03) 4: 1------- Extension Bit 5: 0x20 Diagnostic 1: CALL STATE(0x14) 2: IE Length(0x01)
TIME STAMP: 1/21/2012, 15:42:21.403 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x01 0x72 Receive Ready
TIME STAMP: 1/21/2012, 15:42:21.403 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x4e 0x72 Information Dest=0 CR=0x0015 RELEASE(0x4d) 1: CAUSE(0x08) 2: IE Length(0x02) 4: 1------- Extension Bit
TIME STAMP: 1/21/2012, 15:42:21.403RECEIVECommand=1 SAPI=0x00TEI=0x000x01 0x50 Receive Ready
TIME STAMP: 1/21/2012, 15:42:21.403RECEIVEResponse=0 SAPI=0x00TEI=0x000x72 0x50 InformationOrig=1 CR=0x8015CALL PROCEEDING(0x02) 1: CHANNEL ID(0x18) 2: IE Length(0x03) 3: 1------- Extension Bit -0------ Interface ID Present --1----- Interface Type ---0---- Spare ----1--- Preferred/Exclusive -----0-- D-Channel Indicator ------01 Info. Channel Sel. *Unknown IE: 0x83 *Unknown IE: 0x81
TIME STAMP: 1/21/2012, 15:42:21.411 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x01 0x74 Receive Ready
TIME STAMP: 1/21/2012, 15:42:21.411RECEIVEResponse=0 SAPI=0x00TEI=0x000x74 0x50 InformationOrig=1 CR=0x8015RELEASE COMPLETE(0x5a) 1: CAUSE(0x08) 2: IE Length(0x02) 4: 1------- Extension Bit
TIME STAMP: 1/21/2012, 15:42:21.411 TRANSMIT Command=0 SAPI=0x00 TEI=0x00 0x01 0x76 Receive Ready
TIME STAMP: 1/21/2012, 15:42:21.411
At this point, since the technitian of the PBX can not help because he doesn't know anything about PRI, protocols, etc., I am shootting in the dark using isdiag.exe, very frustrating. I am sure we all have been there more than once.
Call are going thru now between my dilaogic server and the Samsung PBX.
Only one problem left: Looks like no DNIS is being delivered (just like in NE1) but the calls goes trhu immediately.
What would be the ISDN parameter in charge of delivering the DNIS ?
This attached file is att.txt
This is an incoming call. Can you tell me what dialing plan or protocol parameter is AT&T using to deliver the DNIS ?
The Number Plan and Number type are same in both cases. I see some problem with Network Facility IE (0x20) and Calling/Called subaddresses, perhaprs, this is what confuses the PBX. If you use ISDIAG to make test calls, please disable subaddresses and set Network Facility to 0xff, so it is not sent.
Or you can try gc_basic_call_demo.exe, which is a part of of Demo folder in the Dialogic system release; this demo doesn't send these IE's. The demo comes with a config file where you'll need to uncomment and modify one line, like this:
############################################################################################### For ISDN Protocols# Board #1dtiB1T1 ISDN Out NONE 93006200 <or your number is here, L.Pp> 0## Board #2#dtiB2T1 ISDN Out NONE 1234567 0##############################################################################################
Then run the demo, and see if it works better.
No luck Leonid. The PBX tech will take a laptop this afternoon with some tools to analyze it further.
Will send you another log file.
Any other ideas by the mean time ?
I have attached a snap shot of the PRI configuration of the Samsung PBX.
What is the file that I have to modify to match these on the snap shot ?
Half of them I have already in my software but some, I guess those by default, I don't know where to find.
