BUG Asterisk 13 SIP/PJSIP and soft keys/BLF Grandstream Endpoints

[wa4zlw]

As one of grandstreams beta testers on the 2170 and the 1610 and having several 20xx's as well i finally had to open a reseller ticket #20160121123800 to sort things out since everything seemed to work properly on asterisk 11.

It's been like pulling teeth to get responses from them and when they do respond it is a few days later and they ignore the comments and questions I raised.

I did upgrade the 2170 to the latest codeset .8 (.9 is beta) which is what they requested. I also provided some SYSLOG info.

What I have asked for is how they have configured their endpoints and pbx so I can duplicate it here. They are claiming their UCM runs asterisk 13 and everything with the endpoints works.

As soon as I have more info, I will pass along.

Leon

 

[wa4zlw]

I finally heard back from Grandstream support after two emails requesting escalation. SO far the same technician is working it and he has requested some test extensions. I told them we need a static IP to allow them past the firewall and then I will create a few test extensions with PJSIP.

As I get more details I will document them here.

Leon

 

[TirsoJRP]

I finally heard back from Grandstream support after two emails requesting escalation. SO far the same technician is working it and he has requested some test extensions. I told them we need a static IP to allow them past the firewall and then I will create a few test extensions with PJSIP.

As I get more details I will document them here.

Leon

Use chan_sip on the extensions you need BLF

 

[wa4zlw]

that wont work in our case. I'm testing with Grandstream.

 

[TirsoJRP]

Are trying to use BLF with Grandstream phones and IncrediblePBX 13? Because I had the same issue and after changing the extension to chan_sip the BLF keys lit like a christmas tree

 

[wa4zlw]

Hi there!

Yes. Just got off the phone with Grandstream. they have this working under PJSIP using Asterisk 13/FB 12 on their UCM appliance. they are going to setup a test extension for me as well.

It seems whats currently happening is we send out the request but the pbx never sends a NOTIFY back so the device can't flick the lites.

SIP is not an option after I've recrafted three pbxes with simpler simliar configurations using minimal extensions

thanks leon

 

[wa4zlw]

info form grandstream on what they are seeing talking to incredible:

39
Leon,

I set up two buttons as BLF for 701 and 702 Then I called Both of them from 720

When I configured the button I see that the Phone sends a SUBSCRIBE and gets a 200 Ok ( all good)

When I call the 701 and 702 EXT, you server sends no NOTIFYs

See the attached trace

Made by: Farid Ahcene on February 02, 2016 13:10

 

[jerrm]

Have you tried a non-IPBX build. I can see finger-pointing starting to happen. Does the same thing happen with FreePBX distro with A13/PJSIP, or AsteriskNow with A13/PJSIP? Might be nice to have confirmation positive it is or is not IPBX specific.

 

[wa4zlw]

Agreed,

I'm waiting to get connected up to the grandstream UCM which has *13/FP 12 I believe. I haven't tried anything else.

Leon

 

[hecatae]

Agreed,

I'm waiting to get connected up to the grandstream UCM which has *13/FP 12 I believe. I haven't tried anything else.

Leon

could you ask them to share their modifications of *13 upstream?

 

[jerrm]

could you ask them to share their modifications of *13 upstream?

Their possible mods is why I'd recommend testing a non-Grandstream, non-IPBX build as well.

If it works with UCM: They will try to say it's an IPBX issue (but what did Grandstream under the covers do with UCM?).

If it works with FPBX Distro and AsteriskNow and UCM: It may really be IPBX, and it may be time to start digging into build options and such.

I need Grandstream and PJSIP too, but it's a back-burner issue at the moment. I'll try and get a test FPBX distro setup and report.

 

[wa4zlw]

agreed but right now I am trying to duplicate environments so we can make sure we are testing the same things the same ways.

right now i can not register to the UCM PBX. I know he upgraded to *13 today and he says still works but he disappeared for the day it seems. :-(

I'll see if I can find out if they've made any *13 mods.

Leon

 

[wa4zlw]

Reply from Grandstream support this morning:

Leon,

I assure that I have a variety of Grandstream phones connected to multiple Asterisk13 PBX and one of them is the screen shot I send you ( the local one)

I cannot disclose any info about our PBX but you guys just need to figure out why the Asterisk is not sending NOTIFY messages to end points.

I bet you can try any other phone and you will always have the same results.

I would suggest you get some help from the Asterisk Community . http://stackoverflow.com/questions/20427967/asterisk-configuration-for-getting-notify-to-the-blf

For the PUBLIC server you can just paste the path 96.31.248.37/public/firmware/gxp2170/GXP2170_1.0.6.8 but trust me this won't help with the issue you are having

Made by: Farid Ahcene on February 03, 2016 10:37

 

[wa4zlw]

FYI for some unknown reason going to the public 96 server gets a 403 Forbidden since yesterday.

I'm still trying to sort out why I can not connect to his pbx.

As a reseller I will holler at grandstream sales once we can duplicate things.

Leon

 

[wa4zlw]

this shows it up as well that nothing is registered for notifies:

Subscribe/Notify

                               

    -= Registered Asterisk Dial Plan Hints =-
720@ext-local       : PJSIP/720&Custom:DND  State:Unavailable     Presence:                Watchers  0
*8570@park-hints    : park:71@parkedcalls&  State:Idle            Presence:not_set         Watchers  0
1000@demo           : SIP/1000              State:Unavailable     Presence:not_set         Watchers  0
*8453669@ext-local  : ccss:SIP/2233435945@  State:Unavailable     Presence:not_set         Watchers  0
1001@demo           : SIP/1001              State:Unavailable     Presence:not_set         Watchers  0
*76720@ext-dnd-hints: Custom:DEVDND720      State:Idle            Presence:not_set         Watchers  0
702@ext-local       : PJSIP/702&Custom:DND  State:Idle            Presence:                Watchers  0
701@ext-local       : PJSIP/701&Custom:DND  State:Idle            Presence:                Watchers  0
*76702@ext-dnd-hints: Custom:DEVDND702      State:Idle            Presence:not_set         Watchers  0
*76701@ext-dnd-hints: Custom:DEVDND701      State:Idle            Presence:not_set         Watchers  0
72@park-hints       : park:72@parkedcalls   State:Idle            Presence:not_set         Watchers  0
73@park-hints       : park:73@parkedcalls   State:Idle            Presence:not_set         Watchers  0
71@park-hints       : park:71@parkedcalls   State:Idle            Presence:not_set         Watchers  0
76@park-hints       : park:76@parkedcalls   State:Idle            Presence:not_set         Watchers  0
77@park-hints       : park:77@parkedcalls   State:Idle            Presence:not_set         Watchers  0
74@park-hints       : park:74@parkedcalls   State:Idle            Presence:not_set         Watchers  0
75@park-hints       : park:75@parkedcalls   State:Idle            Presence:not_set         Watchers  0
78@park-hints       : park:78@parkedcalls   State:Idle            Presence:not_set         Watchers  0
53669@ext-local     : SIP/2233435945@sip2s  State:Idle            Presence:                Watchers  0
2663@ext-meetme     : confbridge:2663       State:Unavailable     Presence:not_set         Watchers  0
*84720@ext-local    : ccss:PJSIP/720        State:Unavailable     Presence:not_set         Watchers  0
1234@default        : SIP/1234              State:Unavailable     Presence:not_set         Watchers  0
*84702@ext-local    : ccss:PJSIP/702        State:Unavailable     Presence:not_set         Watchers  0
*84701@ext-local    : ccss:PJSIP/701        State:Unavailable     Presence:not_set         Watchers  0
*87@ext-meetme      : confbridge:2663       State:Unavailable     Presence:not_set         Watchers  0
*85@park-hints      : park:71@parkedcalls&  State:Idle            Presence:not_set         Watchers  0
----------------
- 26 hints registered

 

[wa4zlw]

just got off the phone wi th Grandstream and it seems there is a problem since we're getting an unreachable - reply from watchguard last evening:

Created By: John Berg (2/3/2016 7:22 AM)
Hi Leon,

ICMP messages by default try and contain part of the message that wasn't delivered. This is interesting.

--- No notifys.pcap

4 2016-02-02 10:02:50.267086000 192.168.22.124 192.168.22.108 ICMP 194 Destination unreachable (Port unreachable)
Syslog message: USER.DEBUG: Feb 2 14:33:12 GXV3275: [00:0B:82:5E:66:C8][1.0.3.62] SIPStack::cb_nist_kill_transaction: Kill NIST transaction 139984\n

Usually 401 Unauthorized will happen once and then the client will send it MD5 response. That is not happening here.

9 2016-02-02 10:02:50.579050000 192.168.22.166 192.168.22.115 SIP 658 Status: 401 Unauthorized |
157 2016-02-02 10:02:54.634386000 199.19.193.9 192.168.22.107 SIP 371 Status: 404 Not found |
294 2016-02-02 10:02:55.672474000 199.19.193.9 192.168.22.107 SIP 370 Status: 404 Not found |
304 2016-02-02 10:02:55.864181000 45.55.154.2 192.168.22.128 SIP 553 Status: 401 Unauthorized |
395 2016-02-02 10:02:57.716863000 199.19.193.9 192.168.22.107 SIP 370 Status: 404 Not found |
414 2016-02-02 10:02:57.933915000 45.55.154.2 192.168.22.128 SIP 550 Status: 401 Unauthorized |

--- BackWoods-XTM520-20160202-2030.pcap

842 2016-02-02 17:32:24.211191 10.195.13.72 45.55.154.2 ICMP 492 Destination unreachable (Port unreachable)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)

Getting one side believing the port is open and the other side not. There are quite a few of these for port 5060.

Regards,

John Berg

 

[wa4zlw]

Hi Sports Fans!

WOrked on this late this afternoon with Grandstream to no avail. Looks like we're not seeing notifies.

He set me up on an Asterisk 1.8 server and it worked as expected since PJSIP is not supported on 1.8.

So this definitely looks like a weirdness with PJSIP and *11/13. Moving back to SIP is not an option for us.

They're gone for the day and will hit this again tomorrow morning.

Leon

 

[wa4zlw]

Oh Grandstream restricted access to their public firmware server I was told to use and now get a 503 error. the only way is to use a full URL with the filename but that doesnt even work from the phone. Will hopefully get more on this tomorrow

 

[jerrm]

GXP2160's with 1.05.29 firmware appear to be working with PJSIP for me using a fresh IPBX iso install.

They do not work with an RPi2 test build. They get a call or two and appear to work, then asterisk stops responding to them altogether, requiring a restart. Likely an issue with that unit, but SIP works fine with it.

 

[krzykat]

Keep the info coming please. I find this interaction with you and Grandstream interesting. Is their XML implementation any better on their newer phones?
I'd love to do some of the scripts that Ward created on the T46 for the GXP-2170.