Transfer Failed on 38G Phones with FreePBX
-
@JaredBusch Thanks.
@NerdyDad said in Qubes OS - Using Xen to Secure Linux:
Installed Qubes and is running. I like the concept but I kind of at the point of "Okay, what now?". I attempted to install the Brave browser and keep getting blocked. My best guess right now is outside firewall because we're not a Linux house at all. Attempted to do a Yum update and discovered that yum has been deprecated and is now going to DNF. WTF?
Yeah that happened a couple years back. Everything is about pretty now.
-
I don't know how that reply ended up here...
-
Just for future reference, its seems the issues with the 38G was with PJSIP. Switching to CHAN_SIP fixed the issue. Of course even the latest firmware is almost two years old.
Searching around I found a guy who figured it out on the asterisk forums. Ran a simple iptables command to drop 503 responses and it fixed it. Not sure if responsive firewall or a reboot would overwrite it though.
iptables -I OUTPUT -m string --string "SIP/2.0 503 Service Unavailable" --algo bm --to 65535 -j DROP
Here is the post...
https://community.asterisk.org/t/transfer-recalls-via-refer-notify-events/69764
-
@bigbear OK that's interesting that PJ sip was causing a problem I know there are minor differences and some of the header information but it was designed to work with sip devices that don't know what PJSip is.
-
I'm attempting to switch back to CHAN_SIP for my 38G Yealink due to some other odd behaviors.
I use the "switch driver" option under advanced in extensions. I enter new credentials and change to port 5160 on the Yealink. I get Registration Failed. Asterisk Log kicks out this...
[2017-03-30 09:09:57] NOTICE[2130] chan_sip.c: Registration from '"Test" sip:[email protected]:5160' failed for 'x.x.x.x:16144' - Wrong password
[2017-03-30 09:09:58] NOTICE[2130] chan_sip.c: Registration from '"Test" sip:[email protected]:5160' failed for 'x.x.x.x:16144' - Wrong passwordI copied the sip secret again, and even defaulted the phone and reconfigured it manually and still get the same error on the phone and in asterisk.
Do I have to delete the extension and recreate it entirely?
-
@bigbear said in Transfer Failed on 38G Phones with FreePBX:
I'm attempting to switch back to CHAN_SIP for my 38G Yealink due to some other odd behaviors.
I use the "switch driver" option under advanced in extensions. I enter new credentials and change to port 5160 on the Yealink. I get Registration Failed. Asterisk Log kicks out this...
[2017-03-30 09:09:57] NOTICE[2130] chan_sip.c: Registration from '"Test" sip:[email protected]:5160' failed for 'x.x.x.x:16144' - Wrong password
[2017-03-30 09:09:58] NOTICE[2130] chan_sip.c: Registration from '"Test" sip:[email protected]:5160' failed for 'x.x.x.x:16144' - Wrong passwordI copied the sip secret again, and even defaulted the phone and reconfigured it manually and still get the same error on the phone and in asterisk.
Do I have to delete the extension and recreate it entirely?
I have switched extensions back-and-forth many times between the two channel types with no issues so you should not have to delete your extension.
-
@bigbear log into that extension with A soft phone to make sure that everything actually does work on chan_sip,
Illuminate was going to be flaky phone from equation for troubleshooting
-
Good thought. It did still fail from both soft phones.
Deleteing extension and recreated as CHAN_SIP, still fails.
I get nothing related to the registration attempt in that phone.
Now working from a different phone. I must not have CHAN_SIP allowed through responsive firewall. But this site is "Local" using the updated firewall terminology and the responsive firewall is enabled for CHAN_SIP.
-
@JaredBusch Do you use 5160 for CHAN_SIP on the phone when you switch to chan_sip?
I am going to go dig out a Yealink 48G.
-
@bigbear said in Transfer Failed on 38G Phones with FreePBX:
Good thought. It did still fail from both soft phones.
Deleteing extension and recreated as CHAN_SIP, still fails.
I get nothing related to the registration attempt in that phone.
Now working from a different phone. I must not have CHAN_SIP allowed through responsive firewall. But this site is "Local" using the updated firewall terminology and the responsive firewall is enabled for CHAN_SIP.
Change to trusted. And then make sure the IP is not already in the blacklist
-
@bigbear said in Transfer Failed on 38G Phones with FreePBX:
@JaredBusch Do you use 5160 for CHAN_SIP on the phone when you switch to chan_sip?
I am going to go dig out a Yealink 48G.
Why if a soft phone does not work using a phone is just more of a f***ing headache stick with the soft phone until you have something registering
-
@JaredBusch said in Transfer Failed on 38G Phones with FreePBX:
@bigbear said in Transfer Failed on 38G Phones with FreePBX:
Good thought. It did still fail from both soft phones.
Deleteing extension and recreated as CHAN_SIP, still fails.
I get nothing related to the registration attempt in that phone.
Now working from a different phone. I must not have CHAN_SIP allowed through responsive firewall. But this site is "Local" using the updated firewall terminology and the responsive firewall is enabled for CHAN_SIP.
Change to trusted. And then make sure the IP is not already in the blacklist
Though its not the correct config I had it in trusted from the other week when I messing around.
I know I am missing some setting on my installation because the asterisk log isnt even showing the attempt to connect.
In the firewall I have responsive firewall enabled but also SIP (chan_sip_ set to local). Its a default installation so its shows port 5160 UDP for chan_sip, configured the phone the same port 5160.
-
@bigbear said in Transfer Failed on 38G Phones with FreePBX:
@JaredBusch said in Transfer Failed on 38G Phones with FreePBX:
@bigbear said in Transfer Failed on 38G Phones with FreePBX:
Good thought. It did still fail from both soft phones.
Deleteing extension and recreated as CHAN_SIP, still fails.
I get nothing related to the registration attempt in that phone.
Now working from a different phone. I must not have CHAN_SIP allowed through responsive firewall. But this site is "Local" using the updated firewall terminology and the responsive firewall is enabled for CHAN_SIP.
Change to trusted. And then make sure the IP is not already in the blacklist
Though its not the correct config I had it in trusted from the other week when I messing around.
I know I am missing some setting on my installation because the asterisk log isnt even showing the attempt to connect.
In the firewall I have responsive firewall enabled but also SIP (chan_sip_ set to local). Its a default installation so its shows port 5160 UDP for chan_sip, configured the phone the same port 5160.
SO yeah either ht efirewall or some other network if Asterisk is not seeing it.
