Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: VOIP

Long Distance woes

 

 

Cisco voip RSS feed   Index | Next | Previous | View Threaded


ealeatherman at gmail

Jun 9, 2006, 5:16 PM

Post #1 of 5 (709 views)
Permalink
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


Scott.Voll at wesd

Jun 11, 2006, 1:53 PM

Post #2 of 5 (694 views)
Permalink
Re: Long Distance woes [In reply to]

have you tried changing the isdn to national, or unknown or something along those lines?

Scott

________________________________

From: cisco-voip-bounces [at] puck 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


hsalama_us at yahoo

Jun 11, 2006, 4:39 PM

Post #3 of 5 (702 views)
Permalink
Re: Long Distance woes [In reply to]

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 [at] wesd> wrote:

> have you tried changing the isdn to national, or
> unknown or something along those lines?
>
> Scott
>
> ________________________________
>
> From: cisco-voip-bounces [at] puck 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 [at] puck
> 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
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


ealeatherman at gmail

Jun 11, 2006, 6:03 PM

Post #4 of 5 (691 views)
Permalink
Re: Long Distance woes [In reply to]

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 [at] yahoo> 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 [at] wesd> wrote:
>
> > have you tried changing the isdn to national, or
> > unknown or something along those lines?
> >
> > Scott
> >
> > ________________________________
> >
> > From: cisco-voip-bounces [at] puck 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 [at] puck
> > 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
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>



--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations


ealeatherman at gmail

Jun 14, 2006, 12:14 PM

Post #5 of 5 (687 views)
Permalink
Re: Long Distance woes [In reply to]

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 [at] gmail > 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 [at] yahoo> 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 [at] wesd> wrote:
> >
> > > have you tried changing the isdn to national, or
> > > unknown or something along those lines?
> > >
> > > Scott
> > >
> > > ________________________________
> > >
> > > From: cisco-voip-bounces [at] puck 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 [at] puck
> > > 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
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip [at] puck
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
>
>
>
> --
> Ed Leatherman
> IP Telephony Coordinator
> West Virginia University
> Telecommunications and Network Operations
>



--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations

Cisco voip RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.