I’ve a customer with an old videoconference device Tandberg 800 with 3 BRI access that have the following problem:
When i make a video call to another end-point by ISDN , the video call establish but then is always intermittent , one moment I’ve video and audio for 5 seg , after that the video disappear and after 30 seg returns again , when I’ve no audio it appears that I’ve isdn problems because appears on the screen the message “re-establishing call … please wait” . I tried to isolate the problem , by disconnect one by one isdn access but without any good result. Sometimes I’ve audio but no video but the other side I’ve audio and video.
Can someone help me on this ? Did anybody have a similar problem with any codec with isdn that have this behavior ? “re-establishing call … please wait”
Strange that you can establish the call, but not maintain the connection.
If the call can be established and you can send and receive video / audio... then lots of things are correct... wiring, protocol, spids, etc, etc You are 90% of the way there
I would say that high error rate or timing issues are the most common causes for dropped calls
I read you original post... so the call does not drop, you just lose audio/video sync? is that correct
Are your BRIs direct from your LEC/phone company or are they from a PBX or Adtran MUX?
Do you have the same problem for calls to other ISDN units or just the one system you are testing with?
I have attached a PDF of an old Tandberg document that describes various diagnostics including ISDN trace..... I believe these are Tandberg Classic erra docs... not the newer MXP series. When I did a ISDN trace, it spit it out in hex and I had to use the TISDN.exe file to make it readable ASCII text (I changed the file ext to .txt so it can be attached.... need to rename to .exe
I would keep it as basic as possible... e.g. 128k non-bonded call, get that to work then build to up to a 384K bonded call.... just my .02
Yes , the call never fall , just lose audio and video. I try more endpoint with the same beahviour. I sent in attach one trace off the call , i will read waht you sent me and try to "understant" this hexadecimal trace with isdntrace on and syslog on.
I can see " H221I-0 connect initial. Start FAW1search " is when i have video and after more or less 5 seg i see in trace "H221I-0 disconnect init " and loose video again and have the message "re-estabilishing call..." on the screen of my LCD.
Thank you very much for the tool tisdn , now i can understand better my trace , i see the SETUP , SETUP ACKNOWLEDGE , ALERTING , CONNECT and CONNECT ACKNOWLEDGE but for all channels that i have , i think that will be just one setup , not 6 (one for each channel - i have 3 lines 64k x 2 = 384k ). It appears that my bearer cap is correct (data) : Bearer cap: 88 90 and ITU-T, Unrestricted digital information, 64k circuit
In my setups i sent different calling numbers because my 3 access have different numbers.
But even like this , i cant understand the problem , i cant see any messages during the time i have "re-estabilishing call" , during this time just have this type of messages:
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...