Patton SN 4552 crashes if 3CX config file is loaded

Status
Not open for further replies.

voiper

Forum User
Joined
Mar 24, 2008
Messages
38
Reaction score
1
Hi Folks,

do we nowadays need a railway set to be busy in a rainy afternoon? Nooo- that's ancient, lol... You only need

3CX Phone System (Version 5.1.4128.0)

Patton SN4552/2BIS/EUI
Hardware Version 2.1
Software Version R4.2 2008-01-17 SIP

and updated Templates.

To get more than busy just run template for "Patton SN4552" in 3CX, import the generated file in the SN4552 and restart. That's it! The Patton 4552 will be death forever, only the "Power" and "WAN" LED will glow. Also the "LAN" LED is dark. Nice effect :shock: So what to do? Only a reset to factory defaults will make that modern railway set alive again, of course without the new configuration.

For the experienced train drivers here's my config file, proudly made by 3CX 8) : Any help highly appreciated, lol....

Best regards,

Voiper

---- snip -----

#########################################################
#
# For SN-4552 1-port BRI
#
# Author: Kevin Attard Compagno
# Date: 2008-02-20
# Contact: [email protected]
#
#########################################################

webserver port 80 language en

system

ic voice 0
low-bitrate-codec g729

system
clock-source 0 0

profile ppp default

profile call-progress-tone defaultDialtone
flush-play-list
play 1 1000 425 0

profile call-progress-tone defaultAlertingtone
flush-play-list
play 1 1000 425 -7
pause 2 4000

profile call-progress-tone defaultBusytone
flush-play-list
play 1 480 425 -7
pause 2 480

profile call-progress-tone defaultReleasetone
flush-play-list
play 1 240 425 -7
pause 2 240

profile call-progress-tone defaultCongestiontone
flush-play-list
play 1 240 425 -7
pause 2 240

profile tone-set default

profile voip default
codec 1 g711alaw64k rx-length 20 tx-length 20
codec 2 g711ulaw64k rx-length 20 tx-length 20
fax transmission 1 relay t38-udp

profile pstn default

profile sip default
no autonomous-transitioning

profile aaa default
method 1 local
method 2 none

context ip router

interface IF_IP_LAN
ipaddress 192.168.100.200 255.255.255.0
tcp adjust-mss rx mtu
tcp adjust-mss tx mtu

context cs switch

mapping-table calling-pi to calling-e164 MP_REM_CLIR
map restricted to ""

routing-table called-e164 RT_ISDN_TO_SIP_0
route T2 dest-interface IF_SIP_0 MP_REM_CLIR

interface isdn IF_ISDN_0
route call dest-table RT_ISDN_TO_SIP_0

interface sip IF_SIP_0
bind gateway GW_SIP_0
service default
route default dest-interface IF_ISDN_0
remote-party-id called-party
address-translation outgoing-call request-uri user-part fix 10001 host-part to-header target-param none
address-translation incoming-call called-e164 request-uri

context cs switch
no shutdown

gateway sip GW_SIP_0
call-signaling-port 5060
bind interface IF_IP_LAN router

service default
domain 192.168.100.250
defaultserver manual 192.168.100.250 loose-router
registration-lifetime 300
registration manual 192.168.100.250
user 10001 authenticate name 10001 password 10001 default register

gateway sip GW_SIP_0
no shutdown

port ethernet 0 0
medium auto
encapsulation ip
bind interface IF_IP_LAN router
no shutdown

port bri 0 0
clock auto
encapsulation q921

q921
protocol pmp
uni-side auto
encapsulation q931

q931
protocol dss1
uni-side user
encapsulation cc-isdn
bind interface IF_ISDN_0 switch

port bri 0 0
no shutdown

---- snap -----
 
Hello,

It actually happened the same to me.

The SN4552 actually came with this software Smartware 4.2 Build Series 2007-09-19 (H323) 10/10/2007 which is not SIP supported so we decided to load this one Smartware 4.2 Build Series 2008-01-17 (SIP) 2/7/2008 which I think is the latest of version 4.2.

This one, as you say, should be supported by 3CX but it is not as when it is loaded it goes crazy and we lose the LAN ports. The power light and VoIP are up but not the LAN lights.

Anyway we tried to load this version Smartware 4.2 Build Series 2007-09-19 (SIP) 10/10/2007 which is the factory default. The first time it did not even try to do it. It just did not do anything. The second time it did it but did not finish. We did lose the LAN port in the middle of the process and have not recovered them since.

There is no way to get it working. We have reset it many times but we cannot now connect it thru the computer and the LAN port will not come up.

This is a conversation that I had with one of ours partners. We finally decided to send it back and get a new one.

This may help you. You may want to try to downgrade the firmware to the mentioned version (bold)

Cheers
Axel
 
The same problem.
Only the incoming calls runing.
Not the outgoing.

20:21:22.218 Call::Terminate [CM503008]: Call(99): Call is terminated
20:21:12.406 CallLeg::onFailure [CM503003]: Call(99): Call to sip:[email protected]:5060 has failed; Cause: 408 Request Timeout; internal
20:20:40.031 CallCtrl::onSelectRouteReq [CM503004]: Call(99): Calling: PSTNline:10001@[Dev:sip:[email protected]:5060]
20:20:40.015 CallCtrl::onSelectRouteReq [CM503004]: Call(99): Calling: PSTNline:10000@[Dev:sip:[email protected]:5060]
20:20:40.000 CallCtrl::onIncomingCall [CM503001]: Call(99): Incoming call from Ext.22 to [sip:[email protected]]
 
Hi,

Well, we finally got a new Patton device. Exactly the same model. We loaded the factory settings for SIP Smartware 4.2 Build Series 2007-09-19 (SIP), as it came with this one Smartware 4.2 Build Series 2007-09-19 (H323). After that it was absolutely fine. But the problem came after we loaded the 3CX configuration on the Patton. It crashed again and the LAN port would not come up. We now cannot access the device thru the LAN port.

Can anyone from 3CX give us a solution, plase? We are getting quite desperate with the situation.

Many Thanks
Axel
 
Hi,

we have this problem too. After inserting the configuration file from 3CX the patton is dead. The LAN-Ports switch off after the device is restarted. Only a hard reset which erase the configuration and replace it with the factory defaults can bring the patton back to live. The funny thing comes now: Our Patton do his job with a configuration file of an old version of 3cx. But this one is for another Patton (I don't remember the type...). And this one only works with an old firmware of the patton 4552. If you try a newer one, a dead patton is the answer. I have tried to compare the two configuration files to find the error but I'am to stupid to find that. After successfull configuration with the old config file, we updated the firmware of the patton to the newest one and saved the config file. Maybe I can insert this one here later (maybe next day), that someone who know his job can compare the files which work with these which doesn't work. Maybe someone want to try this file on his system...

Greetings Torsten
 
If you install the config of 3cx the lan dead, but the wan works great with incoming calls. Wath´s up with de outgoing?.
 
Hi there

I'm researching this - and hopefully will come up with the answers.

Regards

Kevin
 
Hello again,

sorry for the late answer. Yesterday I didn't come up to the server, today it works. Here is our actual config file, which hopefully works on other systems, too. Its from a patton 4552 with firmware R4.2.
Code:
#----------------------------------------------------------------#
#                                                                #
# SN4552/2BIS/EUI                                                #
# R4.2 2008-01-17 SIP                                           #
# 1970-01-01T00:18:47                                            #
# Generated configuration file                                   #
#                                                                #
#----------------------------------------------------------------#

cli version 3.20
webserver port 80 language en

system

  ic voice 0
    low-bitrate-codec g729

profile ppp default

profile tone-set default

profile voip default
  codec 1 g711alaw64k rx-length 20 tx-length 20
  codec 2 g711ulaw64k rx-length 20 tx-length 20

profile pstn default

profile sip default

profile aaa default
  method 1 local
  method 2 none

context ip router

  interface eth0
    ipaddress dhcp
    tcp adjust-mss rx mtu
    tcp adjust-mss tx mtu

  interface eth1
    ipaddress 192.168.2.2 255.255.255.0
    tcp adjust-mss rx mtu
    tcp adjust-mss tx mtu

context cs switch

  interface isdn isdnif0
    route call dest-interface sipif0

  interface isdn isdnif1
    route call dest-interface sipif1

  interface sip sipif0
    bind gateway sipgw0
    service default
    route call dest-interface isdnif0
    remote-party-id called-party
    address-translation outgoing-call request-uri user-part fix 10003 host-part to-header target-param none
    address-translation incoming-call called-e164 request-uri

  interface sip sipif1
    bind gateway sipgw1
    service default
    route call dest-interface isdnif1
    remote-party-id called-party
    address-translation outgoing-call request-uri user-part fix 10004 host-part to-header target-param none
    address-translation incoming-call called-e164 request-uri

context cs switch
  no shutdown

gateway sip sipgw0
  bind interface eth1 router

  service default
    domain 192.168.2.9
    defaultserver manual 192.168.2.9 loose-router
    registration manual 192.168.2.9
    user 10003 authenticate password ySyWxUvSc/c= encrypted default register

gateway sip sipgw0
  no shutdown

gateway sip sipgw1
  call-signaling-port 5062
  bind interface eth1 router

  service default
    domain 192.168.2.9
    defaultserver manual 192.168.2.9 loose-router
    registration manual 192.168.2.9
    user 10004 authenticate password 9CS6/5Fhrd0= encrypted default register

gateway sip sipgw1
  no shutdown

port ethernet 0 0
  encapsulation ip
  bind interface eth0 router
  no shutdown

port ethernet 0 1
  encapsulation ip
  bind interface eth1 router
  no shutdown

port bri 0 0
  clock auto
  encapsulation q921

  q921
    protocol pmp
    uni-side auto
    encapsulation q931

    q931
      protocol dss1
      uni-side user
      encapsulation cc-isdn
      bind interface isdnif0 switch

port bri 0 0
  no shutdown

port bri 0 1
  clock auto
  encapsulation q921

  q921
    protocol pmp
    uni-side auto
    encapsulation q931

    q931
      protocol dss1
      uni-side net
      encapsulation cc-isdn
      bind interface isdnif1 switch

port bri 0 1
  no shutdown


You have to change the IP adresses of the router and the phone system. I think you should copy both of the service default parts

Code:
service default
    domain 192.168.2.9
    defaultserver manual 192.168.2.9 loose-router
    registration manual 192.168.2.9
    user 10004 authenticate password 9CS6/5Fhrd0= encrypted default register

from your with 3cx generated config file and paste it into this one. Maybe in the following part you have to change the user twice (for each channel):

Code:
address-translation outgoing-call request-uri user-part fix 10004 host-part to-header target-param none

Good luck!!!

Regards
Torsten
 
To copy and paste your configuration please tell witch parameters I need to change in my config file.

3cx IP
PATTON ip
Extension
Pasword extension.
Port confir in 3cx when configure the patton 5060 or 5062?
Thanks.

NicoNutter
 
Hi there

I have attached a corrected version of the template file to handle the SN-4552 device.

Please copy over the file currently in:

c:\program files\3cx phonesystem\data\http\templates\gateway

This should correctly set up a factory-reset SN-4552.

Note that the device must be running one of these firmware versions:
3.21
4.1
4.2

I would appreciate feedback on this issue.

Thanks and Regards

Kevin
 
Hi there,

Thanks for this Kevin.

I would test it but after we loaded the 3CX config on the second Patton 4552 we lost it again. We have tried to reset it with no luck. The LAN port will not come up anymore. We decided to send it back and got a Patton 4554 instead. We are now a little afraid of loading the 3CX config.

Would the other template work just fine? Or our device would become disabled like the other two first? What do you reckon?

Cheers
Axel
 
Hi Axel

The SN-4554 is a different device, and has no LAN ports.

This is confirmed by numerous users as working out of the box (meaning the template).

Regards

Kevin
 
Hi there,

We have loaded the template on the Patton 4554 and it is working beautifully. Thank you very much for your help.

Cheers
Axel
 
Kevin, with your file the same. The generate file now are like:
#########################################################
#
# For SN-4552 1-port BRI
#
# Author: Kevin Attard Compagno
# Date: 2008-02-20
# Contact: [email protected]
#
#########################################################

webserver port 80 language en

system

ic voice 0
low-bitrate-codec g729

system
clock-source 0 0

profile ppp default

profile call-progress-tone defaultDialtone
flush-play-list
play 1 1000 425 -6

profile call-progress-tone defaultAlertingtone
flush-play-list
play 1 1500 425 -13
pause 2 3000

profile call-progress-tone defaultBusytone
flush-play-list
play 1 200 425 -7
pause 2 200

profile call-progress-tone defaultReleasetone
flush-play-list
play 1 200 425 -7
pause 2 200
play 3 200 425 -7
pause 4 200
play 5 200 425 -7
pause 6 600

profile call-progress-tone defaultCongestiontone
flush-play-list
play 1 200 425 -7
pause 2 200
play 3 200 425 -7
pause 4 200
play 5 200 425 -7
pause 6 600

profile tone-set default

profile voip default
codec 1 g711alaw64k rx-length 20 tx-length 20
codec 2 g711ulaw64k rx-length 20 tx-length 20
fax transmission 1 relay t38-udp

profile pstn default

profile sip default
no autonomous-transitioning

profile aaa default
method 1 local
method 2 none

context ip router

interface IF_IP_LAN
ipaddress 10.0.0.4 255.255.255.0
tcp adjust-mss rx mtu
tcp adjust-mss tx mtu

context cs switch

mapping-table calling-pi to calling-e164 MP_REM_CLIR
map restricted to ""

routing-table called-e164 RT_ISDN_TO_SIP_0
route T2 dest-interface IF_SIP_0 MP_REM_CLIR

interface isdn IF_ISDN_0
route call dest-table RT_ISDN_TO_SIP_0

interface sip IF_SIP_0
bind gateway GW_SIP_0
service default
route default dest-interface IF_ISDN_0
remote-party-id called-party
address-translation outgoing-call request-uri user-part fix 10000 host-part to-header target-param none
address-translation incoming-call called-e164 request-uri

context cs switch
no shutdown

gateway sip GW_SIP_0
call-signaling-port 5060
bind interface IF_IP_LAN router

service default
domain 10.0.0.5
defaultserver manual 10.0.0.5 loose-router
registration-lifetime 300
registration manual 10.0.0.5
user 10000 authenticate name 10000 password 10000 default register

gateway sip GW_SIP_0
no shutdown

port ethernet 0 0
medium auto
encapsulation ip
bind interface IF_IP_LAN router
no shutdown

port bri 0 0
clock auto
encapsulation q921

q921
protocol pp
uni-side auto
encapsulation q931

q931
protocol dss1
uni-side user
encapsulation cc-isdn
bind interface IF_ISDN_0 switch

port bri 0 0
no shutdown

The imput its OK and the output the same error.
The lan only runing on the eth0 wan port. The lan eth1 not link.
Please I need to run the patton 4552 in two clients. Its urgent.
Thanks.
NicoNutter
 
Hi Niconutter,

It might be worth for you to get one Patton 4554, it is working fine for us, we did not have any problem at all loading the 3CX config on it. I know that this device has got 2 BRI ports but if it does the job it my be worth for you.

The only issue we have is the only can have one incoming simultaneous call. With the outgoing calls we do not have any problem as the system can habdle 2 call at the same time.

Cheers
Axel
 
Thanks, but in Spain the 4554 patton don’t have stock. I can’t wait two weeks for the 4554.
I buy 3 patton 4552 to 3 clients and I have problems in all of them.
I buy the 4552 because 3cx recommended… I don’t understand the problem now.
Please, I need some help. Only ok the incoming calls.
 
Hi Niconutter,

I am also going to Spain, actually I am Spanish and going to start the business there very soon. Maybe we can keep contact by email or phone and talk about the 3CX things. I am going to base my company in VoIP most of all. It might be nice to share our experiences.

What do you say?

I would recommend you to contact someone to help you to manually configure the Patton 4552 without loading the 3CX template as it crashes the device.

Cheers
Axel
 
Hi niconutter

The config you have attached indicates it has been generated with the old template.

To complete the procedure these are the steps necessary:

  • 1. Replace the file as described in my previous post: http://www.3cx.com/forums/patton-sn-4552-crashes-if-3cx-config-file-is-loaded-4734.html#p22545
    2. Delete all lines and gateway entries in the 3CX Management Console that refer to the SmartNode 4552
    3. If you cannot connect to the Patton, it may be necessary to "Factory Reset" the device
    4. Start the gateway procedure again as normal:
    • a. Create the gateway in the 3CX Management Console
      b. Generate the config file at the end of the creation process
      c. Import the generated file into the Patton using the Patton's Web interface

Regards

Kevin
 
Hi there

You can simplify the procedure to update the 4552 template to the new (working) version by using the 3CX Management Console to handle all the updates itself. This is how you can do it:

  • 1. Log in to the 3CX Management Console
    2. Click on the "General -> Versions/Updates" link in the left-hand-side menu
    3. Scroll down to the "VOIP Gateway Templates"
    4. Select the entry called "Patton SN-4552 1-port ISDN/BRI"
    5. Click on the "Download Selected" button at the end of the section
    6. Delete all lines and gateway entries in the 3CX Management Console that refer to the SmartNode 4552
    7. If you cannot connect to the Patton, it may be necessary to "Factory Reset" the device
    8. Start the gateway procedure again as normal:
    • a. Create the gateway in the 3CX Management Console
      b. Generate the config file at the end of the creation process
      c. Import the generated file into the Patton using the Patton's Web interface

Regards

Kevin
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,893
Messages
589,598
Members
164,761
Latest member
SaschaA_