|
Home > Archive > Voice over IP Cisco > June 2006 > Long Distance woes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Long Distance woes
|
|
| Ed Leatherman 2006-06-10, 1:11 am |
| Was wondering if anyone is familiar with how long distance carriers/service
interacts with local service...
Working with service provider at one of our branch campuses which we just
converted to a callmanager system this past week. Users can call long
distance numbers within our area code (304) just fine, but cannot call
outside of the area code. The dial pattern is the same (9.1[2-9]XX[2-9]XX
XXXX) for either case (exact same route pattern actually), I just strip the
9 and send 1 + 10 digits to the phone company. Can see this in CCM trace.
System uses 2 PRI T1's.
If users call an out of state number, they get fast busy. The local carrier
is looking at the problem now but initially they just told me it wasnt there
problem, as they just pass the digits to the long distance carrier if the
number starts with "1". It seems to me that maybe the lines are setup
incorrectly as far as what long distance provider it should use.. but I dont
know enough about the process to make a good guess.. I've not worked with
this particular local service provider before so I dont have the same
"faith" if you could call it that, as I do with the carrier we have at the
main campus which I have dealt with before.
Caller ID also does not come across, but I think this is a seperate issue
which we can hopefully address after the long distance is working.
Any ideas? I'm curious if there is anything more I can look at from my end.
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
| |
| Voll, Scott 2006-06-11, 7:11 pm |
| have you tried changing the isdn to national, or unknown or something along those lines?
Scott
________________________________
From: cisco-voip-bounces@puck.nether.net on behalf of Ed Leatherman
Sent: Fri 6/9/2006 5:16 PM
To: ciscovoip
Subject: [cisco-voip] Long Distance woes
Was wondering if anyone is familiar with how long distance carriers/service interacts with local service...
Working with service provider at one of our branch campuses which we just converted to a callmanager system this past week. Users can call long distance numbers within our area code (304) just fine, but cannot call outside of the area code. The dial pattern is the same (9.1[2-9]XX[2-9]XX XXXX) for either case (exact same route pattern actually), I just strip the 9 and send 1 + 10 digits to the phone company. Can see this in CCM trace. System uses 2 PRI T1's.
If users call an out of state number, they get fast busy. The local carrier is looking at the problem now but initially they just told me it wasnt there problem, as they just pass the digits to the long distance carrier if the number starts with "1". It seems to me that maybe the lines are setup incorrectly as far as what long distance provider it should use.. but I dont know enough about the process to make a good guess.. I've not worked with this particular local service provider before so I dont have the same "faith" if you could call it that, as I do with the carrier we have at the main campus which I have dealt with before.
Caller ID also does not come across, but I think this is a seperate issue which we can hopefully address after the long distance is working.
Any ideas? I'm curious if there is anything more I can look at from my end.
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
| |
| Hassan Salama 2006-06-11, 7:11 pm |
|
Hello,
Regarding your issue of long distance call, the number
handling could varies from country to country as this
is telecom standard.
But you may try the translation rule to modify Called
party number type to become national [a must for long
distance within a country], and stip 91 from the
begeinning of the number [i.e. send 10 digits without
1], you may give another try with stipping 9 digit
only
Thanks
--- "Voll, Scott" <Scott.Voll@wesd.org> wrote:
> have you tried changing the isdn to national, or
> unknown or something along those lines?
>
> Scott
>
> ________________________________
>
> From: cisco-voip-bounces@puck.nether.net on behalf
> of Ed Leatherman
> Sent: Fri 6/9/2006 5:16 PM
> To: ciscovoip
> Subject: [cisco-voip] Long Distance woes
>
>
> Was wondering if anyone is familiar with how long
> distance carriers/service interacts with local
> service...
>
> Working with service provider at one of our branch
> campuses which we just converted to a callmanager
> system this past week. Users can call long distance
> numbers within our area code (304) just fine, but
> cannot call outside of the area code. The dial
> pattern is the same (9.1[2-9]XX[2-9]XX XXXX) for
> either case (exact same route pattern actually), I
> just strip the 9 and send 1 + 10 digits to the phone
> company. Can see this in CCM trace. System uses 2
> PRI T1's.
>
> If users call an out of state number, they get fast
> busy. The local carrier is looking at the problem
> now but initially they just told me it wasnt there
> problem, as they just pass the digits to the long
> distance carrier if the number starts with "1". It
> seems to me that maybe the lines are setup
> incorrectly as far as what long distance provider it
> should use.. but I dont know enough about the
> process to make a good guess.. I've not worked with
> this particular local service provider before so I
> dont have the same "faith" if you could call it
> that, as I do with the carrier we have at the main
> campus which I have dealt with before.
>
> Caller ID also does not come across, but I think
> this is a seperate issue which we can hopefully
> address after the long distance is working.
>
> Any ideas? I'm curious if there is anything more I
> can look at from my end.
>
> --
> Ed Leatherman
> IP Telephony Coordinator
> West Virginia University
> Telecommunications and Network Operations
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| |
| Ed Leatherman 2006-06-12, 1:11 am |
| I'm going to try changing the numbering plan tomorrow to national and see if
that helps, thanks for the suggestion!
On 6/11/06, Hassan Salama <hsalama_us@yahoo.com> wrote:
> Hello,
>
> Regarding your issue of long distance call, the number
> handling could varies from country to country as this
> is telecom standard.
>
> But you may try the translation rule to modify Called
> party number type to become national [a must for long
> distance within a country], and stip 91 from the
> begeinning of the number [i.e. send 10 digits without
> 1], you may give another try with stipping 9 digit
> only
>
> Thanks
>
> --- "Voll, Scott" <Scott.Voll@wesd.org> wrote:
>
>
>
> ________________________________________
__________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
| |
| Ed Leatherman 2006-06-14, 7:11 pm |
| While that didnt fix my problem, I did get it setup to match the telco's
settings, which sounds like a good idea anyway 
Turns out the PRI's were setup with the wrong long distance code at the CO,
so they were sending calls to AT&T instead of Sprint. Was a good
troubleshooting exercise for me though.
On 6/11/06, Ed Leatherman <ealeatherman@gmail.com > wrote:
>
> I'm going to try changing the numbering plan tomorrow to national and see
> if that helps, thanks for the suggestion!
>
>
> On 6/11/06, Hassan Salama < hsalama_us@yahoo.com> wrote:
>
>
>
>
> --
> Ed Leatherman
> IP Telephony Coordinator
> West Virginia University
> Telecommunications and Network Operations
>
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
|
|
|
|
|