Business Phone Systems

Previous Thread
Next Thread
Print Thread
Rate Thread
Joined: Sep 2009
Posts: 151
Member
OP Offline
Member
Joined: Sep 2009
Posts: 151
Has anyone done this? I am trying to. The Summit can call the MBX extensions with no problem, but when I try to dial a summit extension from the MBX I get that line is busy? I have followed the tech bulletin precisely. I have been told that it is a port forwarding problem, but the IT guys are assuring me there is no port forwarding in the setup we are using because they are essentially on the same network. Any help or suggestions would be greatly appreciated.


Scotty Woods
Installation Technician
N.E.T. Systems
Blytheville, Arkansas
Atcom VoIP Demo
VoIP Demo
Joined: Jan 2008
Posts: 3,821
Retired Moderator
****
Offline
Retired Moderator
****
Joined: Jan 2008
Posts: 3,821
Can you ping the Summit from the Mbx site...if not then the Mbx cannot reach the Summit. If you can and there is no ip port forwarding going on then a setting is off somewhere, could be in either system.


www.myrandomviews
"Old phone guys never die, they just get locked in some closet with an old phone system and forgotten about"

Retired, taking photographs and hoping to fly one of my many kites.
Joined: Sep 2009
Posts: 151
Member
OP Offline
Member
Joined: Sep 2009
Posts: 151
I can ping the Summit. Its weird, the message that says that line is busy sounds like its coming from the Summit. If I take the IP address out of CPN in the MBX I get a message that is a different voice.


Scotty Woods
Installation Technician
N.E.T. Systems
Blytheville, Arkansas
Joined: Jan 2008
Posts: 3,821
Retired Moderator
****
Offline
Retired Moderator
****
Joined: Jan 2008
Posts: 3,821
Well, lets start with the Summit basic for inbound
Set the voip trunks to DID/DNIS and put in their own group. Make sure all extensions on the Summit have access to this group.
Set Net numbering index 1 for the stations ie 1*** on the Summit (no ip address)
Set Net numbering index 2 for the stations on the MBX ie 2***

Last edited by Derrick; 04/20/16 09:53 PM.

www.myrandomviews
"Old phone guys never die, they just get locked in some closet with an old phone system and forgotten about"

Retired, taking photographs and hoping to fly one of my many kites.
Joined: Sep 2009
Posts: 151
Member
OP Offline
Member
Joined: Sep 2009
Posts: 151
I have submitted the databases to Toni for further evaluation.


Scotty Woods
Installation Technician
N.E.T. Systems
Blytheville, Arkansas
Joined: Jan 2008
Posts: 3,821
Retired Moderator
****
Offline
Retired Moderator
****
Joined: Jan 2008
Posts: 3,821
What tech bulletin did you use. I only know about the mbx-mbx one and the mbx-sbx. I have not seen one for mbx-summit?


www.myrandomviews
"Old phone guys never die, they just get locked in some closet with an old phone system and forgotten about"

Retired, taking photographs and hoping to fly one of my many kites.
Joined: Sep 2009
Posts: 151
Member
OP Offline
Member
Joined: Sep 2009
Posts: 151
There isn't one. I used the MBX to MBX for the MBX setup and Summit to Summit for the Summit set up. I have had Darren with Hoosier look at it, Toni from Vertical look at it and the IT people look at it. No one can figure it out. The systems can ping each other and I can talk Summit to MBX, but when I try to call from MBX to Summit I get a message saying that line is busy.


Scotty Woods
Installation Technician
N.E.T. Systems
Blytheville, Arkansas
Joined: Sep 2009
Posts: 151
Member
OP Offline
Member
Joined: Sep 2009
Posts: 151
Ok, I still can not get this to work.
Site A is a MBX (192.168.1.25)
Site B is a Summit (192.168.112.200)
I can call from B to A with no problems
When I dial 2150 from site A, I get a message, that line is busy.
If I dial 805 (VOIP Lines 17 thru 20 are in group 5) I get dial tone, then when I dial 2150, it sits there for 5 seconds then gives ma a busy tone.
The stations have access to group 5.
I have the NET Attributes in the MBX as follows
Index 1
Numbering Plan Type NET
Numbering Plan Code 1999
CPN 1 Blank
Index 2
Numbering Plan Type NET
Numbering Plan Code 2XXX
Outgoing Co Group 5
CPN Info 1 192.168.112.200
HELP!!!


Scotty Woods
Installation Technician
N.E.T. Systems
Blytheville, Arkansas
Joined: Jan 2008
Posts: 3,821
Retired Moderator
****
Offline
Retired Moderator
****
Joined: Jan 2008
Posts: 3,821
If the message is coming from the Summit then it is not an IP problem it is a routing or trunk config problem, at least I think it is. However it could also be software version problem with the MBX. I have seen where it will not talk to an SBX or Summit without an upgrade. If that were the case I would upgrade it to a Summit 800. First thing though is to recheck the did/isdn trunking setup for both sites.

Last edited by Derrick; 06/21/16 03:56 PM.

www.myrandomviews
"Old phone guys never die, they just get locked in some closet with an old phone system and forgotten about"

Retired, taking photographs and hoping to fly one of my many kites.

Moderated by  EV607797, MnDave, nfcphoneman 

Link Copied to Clipboard
Forum Statistics
Forums84
Topics93,824
Posts636,751
Members49,644
Most Online5,661
May 23rd, 2018
Popular Topics(Views)
Today's Birthdays
beegeezer, Matthaus
Newest Members
PhoneGuy827, julesm, Helen.D, AlAl, mike hurford
49,643 Registered Users
Top Posters(30 Days)
pvj 11
ramo 11
Toner 7
dans 5
Who's Online Now
2 members (KoolBreeze, Coral Tech), 37 guests, and 44 robots.
Key: Admin, Global Mod, Mod
Contact Us | Sponsored by Atcom: Business Phone Systems | Terms of Service

Sundance Communications is not affiliated with any of the above manufacturers.
©Copyright Sundance Communications 1998-2023
Powered by UBB.threads™ PHP Forum Software 7.7.5