Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

ISDN Telepresence (isdn link)

Hi all,

We have an ISDN Link which is hook up to our SX20.

we are using ISDN30 "PRI" and IP connection for this. The problem started 3 weeks ago that suddenly we cannot connect to any ISDN numbers that we dial from endpoint. As i had checked the settings of ISDN Link via SSH, it seems that everything is okay but yet, still having issues. IP Connection on the other hand, is perfectly working fine.

 

First TS:

- restored factory defaults on ISDN Link

- called telco to check ISDN Line (no problem) we have 2 PRI btw and i checked and used the other line as well, no go.

- updated the endpoint firmware to the latest, still no go.

 

I attached the config of the isdn link. I removed some informations like IP and ISDN number on the attached file for security purposes.

Everyone's tags (2)
9 REPLIES
New Member

Troubleshooting steps

Troubleshooting steps performed are All no go btw.

 

i want to know how to set-up this ISDN Link properly and what are the thing i am missing.

i also would like to update the firmware of ISDN link (already have the file) but i do not know how to proceed. I tried, however, this command xCommand SystemUnit SoftwareUpgrade URL: “http://ftp.tandberg.com/pub/software/endpoints/isdnlink/<filename>”  but it only gave me this error message "Warning: Software download failed: Couldn't resolve host 'ftp.tandberg.com"

 

VIP Green

At a quick glance on your

At a quick glance on your attachment, it appears you have IPv6 disabled on your device.  You need IPv6 enabled on both your endpoint and ISDNLink for them to pair and work correctly.

As for your endpoint not upgrading, the error message suggests it cannot resolve the hostname - this is because in your config on the ISDNLink you haven't provided the DNS Server address(es).  If you have your own TFTP server you can use that in place to the ftp.tandberg.com link.

I'd highly recommend updating the ISDNLink Firmware - version IL1.0.0 is very buggy and had a horrific dial string - this is much easier in version IL1.1.0+.  Keep in mind, you'll likely need to update it in the near future to address the GNU Bash vulnerability.

In the mean time, you should have at laest version IL1.1.1 which includes the fixes for the Heartbleed vulnerability, or IL1.1.2 if you're running TC7.2 on your endpoint.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
 

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne,Just curious if you

Wayne,

Just curious if you know.  If you use a switch between the codec & ISDN Link, the switch needs to be able to understand & route IPv6, right?  If you use some crappy switch that is only IPv4 they will not pair, right?

Thanks,
Justin

Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ
VIP Green

Hi Justin,All the

Hi Justin,

All the installation guides and documentation shows that you should be connecting them directly with the ethernet cable, and not going through a switch.

In general, switches are Layer 2 devices, and neither know, nor care about what's going on at Layer 3 (IPv4 or IPv6), so using a switch in between may work - I've not got any configured that way

If you've got a "dumb/crappy" switch (unmanaged), it should just pass the packets.  You're more likely to have an issue where you have a "Smart" switch which could be set to block IPv6, or needs to understand IPv6 with respect to ACLs, VLANs, etc. Of course, you'll have an issue if you're needing to route the traffic between subnets, and that's really not likely to be a supported solution.

Wayne

--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne,Thanks for the info.

Wayne,

Thanks for the info.  The only time we have seen this is when an integrator is onsite setting up the codec & Link.  Usually they are not allowed to access the customer's network to configure the Link & Codec and they never want to use serial.  So they just use a little switch they bring with them so they can insert their laptop into the mix between the codec & Link and be able to configure everything.

Thanks,
Justin

Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ
VIP Green

They should be able to set it

They should be able to set it up semi-normally - ie, endpoint -> ISDNLink -> switch > Laptop, there shouldn't be a need to insert the switch between the endpoint and ISDNLink.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
New Member

Hi  wayne, thanks for the

Hi  wayne,

 

thanks for the reply. The problem here is, the IPV6 is enabled all along, this settings you are seeing right now is only a test that i did to see if there will be any difference. i am not sure if it will make a world of difference, but i dont use iPV6 only iPV4, so is it still important to enable the iPV6?

 

what else do i need to check aside from the iPV6?

New Member

Got some developments. I

Got some developments.

 

I managed to upgrade the ISDN Link software. Still not working fine.

Everytime i try to dial an isdn number, it will just say connected but actually nothing is on the screen. We got 2 endpoints here one is working fine when calling the same isdn number but this SX20 which is connected to the ISDN Link, does not work properly.

can you guys helps me check what is wrong in reference to the new attached file. thanks

VIP Green

OK, there are a few issues I

OK, there are a few issues I can see in that config.

1) The SIP PeerUri is not an acutal URI (endpoint@yourdomain.com) - this needs to be the SIP URI of your SX20.

2) Is the SIP PeerHost the IP address of your SX20?

3) Is 172.17.8.129 the correct IPv4 Gateway Address for your IP subnet?

4) The Time synchronisation can be very important. especially with encryption, so set your NTP server to an NTP server on your network, or upstream ISP rather than the Tandberg one, and make sure your SX20 is set to the same one.

5) Set the SIP Profile URI on the ISDN Link (ie isdnlink@yourdomain.com).

Please find attached an example config I'd posted in another thread previously (although it uses a BRI rather than a PRI).

Also, what is the endpoint at the other end?  And what version of software is it using?  It could be a capset issue if there's no video.  Do you get any audio?  What do the call stats say for this supposedly "connected" session that's not working?

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
191
Views
0
Helpful
9
Replies
CreatePlease login to create content