web statisticsweb stats

Business Phone Systems

Previous Thread
Next Thread
Print Thread
Rate Thread
#203707 03/04/11 06:03 AM
Joined: Mar 2011
Posts: 6
Member
Member
Offline
Joined: Mar 2011
Posts: 6
hi again.

to keep my issues seperate i've made another topic regarding remote workers connecting to our external LIPU-X/LIPS.

I wondering if any installers have run into roadblocks with various ISPs (specifically Charter). I cannot get my current IP5022-SD with firmware IP5K4-M1G0E to connect to my LIPU. The phone will always come up with an IPU ALIVE PACKET STOP.

I've troubleshooted the heck out of this even connecting the phone striaght behind the cable modem with nothing else and still the result is the same.

I recently saw new firmware updates for the phone and IP cards. I applied the recent LIPU firmware (03_01) and to a test phone the IP5K4-M2D0C firmware. Well it looks like they've made some progress as I can get the phones to register and display their name, extension, dial-tone even but I only receive a one way talk path (they can hear me but i cannot hear them).

My next goal is to get a packet dump and see if RTP streams will clue me in as to what's going on. My thought is that Toshiba is still tinkering around to get the phones fully functional on any ISP.

I thought i would pose the situation here and see if any of you experts have any clues or tricks I can try. I'm a network engineer at heart but I'm sure there could be something i'm missing. Thanks for any sage adive you can provide!


note: i haven't tried using an MIPU yet. It's sort of an option but i would need to shuffle alot of cards around.


CIX670
Atcom VoIP Phones
VoIP Demo

Best VoIP Phones Canada


Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.

#203708 03/04/11 07:40 AM
Joined: Jan 2010
Posts: 937
Likes: 5
Moderator-Toshiba
*****
Moderator-Toshiba
*****
Joined: Jan 2010
Posts: 937
Likes: 5
can you connect the phone to the LIPU when they are both on local LAN IP addresses eg 192.168.254.xxx
You shouldnt have any problems doing this.

The one way speech is a side affect of NAT traversal when running a remote IPT handset when the LIPU r MIPU is sitting on the LAN behind a firewall.
A way around this is to get a /30 or /29 subnet and hook up the xIPU card onto the public IP address at the office and the remote IPT handsets are OK to be sitting behind an ADSL router/firewall.

Maybe if you could describe yur configuration a bit better we can help further.


Regards
Carl
#203709 03/04/11 08:36 AM
Joined: Mar 2011
Posts: 6
Member
Member
Offline
Joined: Mar 2011
Posts: 6
Quote
can you connect the phone to the LIPU when they are both on local LAN IP addresses eg 192.168.254.xxx
You shouldnt have any problems doing this.
yes. the phones work in house and are fully tested before they go out the door. infact, we even put them in our test network which has a completely different internal and external network to test against the LIPU and verify they work.


Quote
The one way speech is a side affect of NAT traversal when running a remote IPT handset when the LIPU r MIPU is sitting on the LAN behind a firewall.
A way around this is to get a /30 or /29 subnet and hook up the xIPU card onto the public IP address at the office and the remote IPT handsets are OK to be sitting behind an ADSL router/firewall.
yes that's our current configuration. the xIPU cards have external addresses and sit on a WAN VLAN. There are no devices except the provided ISP Cisco ME 3400

here's a very simplified version of our configuration.


https://docs.google.com/viewer?a=v&...lMTYzZjRl&hl=en&authkey=CLa_wZ0P


CIX670
#203710 06/09/11 09:25 AM
Joined: Mar 2011
Posts: 6
Member
Member
Offline
Joined: Mar 2011
Posts: 6
hey guys!

thought i'd come back and update this thread that i have solved the issue.

pouring through packet data the only thing i picked up with that there were bits in the PCP field. huh... 802.1Q i thought to myself.

so i went back to the phone system and there it was under program 150-07 IEEE802.1p 'enabled'

crap. that's only going to honor at layer 3 and i have no doubt that some of charters equipment will honor it and some won't (hence the spotty connectivity).

i disbaled it all together and in the future will use diffserv if i need to start QoS tagging.

i hope this helps out some other admins or atleast gives them some other clues to start looking at.


CIX670

Moderated by  Carlos#1, phonemeister 

Link Copied to Clipboard
Newest Topics
SV8100 beeping
by Jackcmann - 04/10/25 05:29 AM
Samsung xchange server
by scanjet - 04/07/25 06:37 PM
NEC IP Phones
by juno - 04/04/25 09:05 AM
NEC IP phones rebooting
by jpet621 - 04/03/25 03:03 PM
Forum Statistics
Forums84
Topics94,515
Posts639,966
Members49,848
Most Online5,661
May 23rd, 2018
Newest Members
Kevin usama, Pruitt roger, ActiveTelephones, yeloshak, ty3995
49,847 Registered Users
Top Posters(30 Days)
Toner 10
Taddeo 6
dexman 3
Who's Online Now
1 members (justbill), 174 guests, and 42 robots.
Key: Admin, Global Mod, Mod
Contact Us | Sponsored by Atcom: One of the best VoIP Phone Canada Suppliers for your business telephone system!| Terms of Service

Sundance Communications is not affiliated with any of the above manufacturers. Sundance Phone System Forums - VOIP & Cloud Phone Help
©Copyright Sundance Communications 1998 - 2025
Powered by UBB.threads™ PHP Forum Software 8.0.0