SL 2100 sip trunk problem

I connected SL1100 via SIP trunking, probably work for a 2100 - I have a document that you can follow its most likely f-route or something like that you're having issues with.

SL Networking

Hang on here, the OP hasn't said there are Sip trunk connections between the two systems or any other connection for that matter (other than ethernet). Why is the OP just assuming the two systems can route between each other just because of an ethernet connection? How are the two systems actually connected from a voice point of view and has any Froute programming been done?

daddybadger said:

I connected SL1100 via SIP trunking, probably work for a 2100 - I have a document that you can follow its most likely f-route or something like that you're having issues with.

SL Networking

Click to expand...

Thanks for the reply, the sip trunk was working and after a power cut, it began with the problem, on Main sl 2100 i have the operator, dialing 0, and also the extension numbering plan with 3xxx, in the other sl 2100 extensión numerbing plan on 4xxx and dialing 0 for operador, but when i dial On this second sl2100 3xxx or 0 i get the busy tone

OzzieGeorge said:

Hang on here, the OP hasn't said there are Sip trunk connections between the two systems or any other connection for that matter (other than ethernet). Why is the OP just assuming the two systems can route between each other just because of an ethernet connection? How are the two systems actually connected from a voice point of view and has any Froute programming been done?

Click to expand...

Thanks for the reply, I'm viewing the backup of both systems, on the main SL 2100
Looking via quick install
Quick Install/Trunks/SIP Trunks/Profile 1/Interconnect IP without registration/Interconnect Remote Destinations
Sys nº: 0001
System Interconnection: Enable
Ip Address: 192.168.5.100
Call Control Port: 1720
Dial Number: 4
Keep Alive Mode For SIP: Option Keep Alive Mode
Domain Name:
Host Name:
User ID: 100
Domain Assignment: IP Address
SIP Carrier Choice: Carrier B
Register Sub Mode: disabled

User ID is the same number of the op extension number (MLT Phone)


44-02 001
Dial 4 F-Route table

44-05-01 F-Route table
1 = with group 2 (line 4 trough 7 SIP Lines)

10-36-00
Enable , User ID 100, Auth ID and pass empty


On the Second 2100

Quick Install/Trunks/SIP Trunks/Profile/Interconnect IP without Registration/Interconnect Remote Destinations.
Sys nº: 0001
System Interconnection: Enable
Ip Address: 192.168.5.100
Call Control Port: 1720
Dial Number: 4
Keep Alive Mode For SIP: Option Keep Alive Mode
Domain Name:
Host Name:
User ID: 100
Domain Assignment: IP Address
SIP Carrier Choice: Carrier B
Register Sub Mode: disabled

On Repots- Feature activation
5001 IP Terminal
Qty: 1
Status: on
Expires: unlimited

5103 VoIP Channel
Qty: 0
Status: off
Expires: unlimited

5111 IP Terminal
Qty: 1
Status: on
Expires: unlimited

5201 Mobile Extension (the don't use that feature)
Qty: 4
Status: on
Expires: unlimited

OzzieGeorge said:

Well the first issue I see is that they both have the same IP address!

Click to expand...

Looking at the config via PCPro
i see different ip address configured under Quick Install/Trunks/SIP Trunks/Profile/Interconnect IP without Registration/Interconnect Remote Destinations.
I will upload screenshots of that config

Again in system 2, both systems are set to the same IP!

OzzieGeorge said:

Again in system 2, both systems are set to the same IP!

Click to expand...

So in the second sl 2100 i should change the ip address on the second row? i ask because in the screenshot i see with two different routes poiting to the ip address of the main sl 2100

You haven't said where either of these systems is located.

Are they in the same building on the same flat network?

Are they in separate buildings? If they are in separate buildings is there some kind of VPN tunnel connecting them to each other? Additionally if they are in different buildings what is the network lay out in each building?

We don't have enough information to tell you what you need to do. I would not make any changes to IP Addresses at this point.