Welcome, Unregistered.

Welcome to VTC talk Forums.
Remember Me?
Blue Jeans Network
Extends high quality video communications beyond the traditional boundaries of specialized conference rooms, allowing employees throughout an enterprise to interact more effectively with each other, and with their customers, partners, and suppliers.
www.bluejeans.com
 
 
Thread Tools Display Modes
Old 04-14-2016   #1
PubRadio
Rookie Member
 
Join Date: Apr 2016
Posts: 2
PubRadio - Has only 10 Tech Points
Default Telos Zephyr

Hello, Noob here
We are a Public Radio station with several Telos Zephyr ISDN CODECs. Our ISDN provider is X/O. The problem: Often outside callers cannot call in to our units. If they are local, it's usually not a problem and we can always connect to them by calling out. X/O says it might have something to do with the call "not being registered as a data call".
Is there some way to get around this? Should we have callers dial our entire SPID?
Most of the incoming calls are other Public Radio stations around the country wanting to conduct a live interview with a local party. Any suggestions?
Thanks
PubRadio is offline  
Old 04-16-2016   #2
Joe Vallender
VTC Professional
 
Joe Vallender's Avatar
 
Join Date: May 2004
Location: Chicago, IL, USA
Posts: 465
Joe Vallender - Has over 50 Tech Points Joe Vallender - Has over 50 Tech Points
Default

You would have to have someone who can duplicate the issue open a ticket with their local ISDN provider to trap their call and see how it is coming, a SW64/56 data call or voice. If it is coming from the originator as a data call to the local ISDN provider then they would have to trace how they are routing it to the destination, whether they are sending it over data trunks or voice trunks. It could be the call is traversing voice trunks somewhere along the path either from the local ISDN provider to the long distance provider, across the long distance providers network of switches or the handoff from the long distance provider to the terminating local ISDN provider (yours). Are all the failing calls from the same long distance provider? Support for SW64/56K ISDN calls has been reduced/phasing out by long distance providers so that may be affecting certain originating callers routing of long distance ISDN data calls. They may be able to receive them (from you over your long distance carrier network) but cannot originate them.

Last edited by Joe Vallender; 04-16-2016 at 08:39 AM. Reason: additional info
Joe Vallender is offline  
Old 04-18-2016   #3
PubRadio
Rookie Member
 
Join Date: Apr 2016
Posts: 2
PubRadio - Has only 10 Tech Points
Default

Thanks, Joe
We've seen problems with both AT&T and Verizon
Jerry

Quote:
Originally Posted by Joe Vallender View Post
You would have to have someone who can duplicate the issue open a ticket with their local ISDN provider to trap their call and see how it is coming, a SW64/56 data call or voice. If it is coming from the originator as a data call to the local ISDN provider then they would have to trace how they are routing it to the destination, whether they are sending it over data trunks or voice trunks. It could be the call is traversing voice trunks somewhere along the path either from the local ISDN provider to the long distance provider, across the long distance providers network of switches or the handoff from the long distance provider to the terminating local ISDN provider (yours). Are all the failing calls from the same long distance provider? Support for SW64/56K ISDN calls has been reduced/phasing out by long distance providers so that may be affecting certain originating callers routing of long distance ISDN data calls. They may be able to receive them (from you over your long distance carrier network) but cannot originate them.
PubRadio is offline  
Old 04-18-2016   #4
Joe Vallender
VTC Professional
 
Joe Vallender's Avatar
 
Join Date: May 2004
Location: Chicago, IL, USA
Posts: 465
Joe Vallender - Has over 50 Tech Points Joe Vallender - Has over 50 Tech Points
Default

If the issue is experienced over multiple LD carriers then the problem could be going into those carrier networks from the originating source or at the handoff from the carriers at the local tandem office to the terminating local serving office. From my experience with troubleshooting these issues, the originating end has to initiate the trouble report with their local service provider insisting coordination with the LD carrier tracing the failing calls. Replicating the failed calls is critical to troubleshooting and coordination with all the carriers/providers involved along the call path is necessary. Chances are there are switch routing tables that are used along the path in routing the calls from xxx-yyy-zzzz to zzz-yyy-xxxx that are pointing to trunk groups that are wrong and/or not supporting SW56/64K data calls. If your LD carrier for outgoing good calls is one of those that fail to terminate calls to you, then you might be able to open a support ticket with them to trace how they would handle the data call coming in from the originating number to your terminating number. Another question would be is if ALL AT&T or Verizon calls terminating to your number fail or only certain ones. If only certain ones, then the originating end may be where the issue lies.
Joe Vallender is offline  
 

Bookmarks


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Register

Username
Password
Email
Close
3.8.4
Copyright 2017 VTCtalk.com
Copyright (c) 2004 - 2012, Crependo. All Rights Reserved