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

[wa4zlw]

Hi folks...so far the only problem I see is with BLF (or any of the soft key functionality) when used with an extension defined on the PBX as CHAN_PJSIP. I've got multiple Grandstream devices here (HT702, GXP2000, GXP2020, GXP1610, GXP2170, DP715) and all devices work when the pbx is configured with CHAN_PJSIP. I have multiple devices using the same extensions. The only problem is the lack of notifications being received from the PBX to the physical devices. On the 2170 I'm running 1.0.6.9 beta.

haven't looked at any XML stuff.

thanks leon

 

[wa4zlw]

on thing I have noticed is I have to periodially AMPORTAL RESTART to get things working again. really annoying.

 

[wa4zlw]

i've been seeing this in the ASTERISK DEBUG, wonder if this is related?

[2016-02-03 18:50:36] WARNING[25842] res_pjsip_pubsub.c: No registered publish handler for event presence
[2016-02-03 19:27:52] WARNING[25842] res_pjsip_pubsub.c: No registered publish handler for event presence
[2016-02-03 19:32:52] WARNING[29713] res_pjsip_pubsub.c: No registered publish handler for event presence
[2016-02-03 19:35:36] WARNING[29713] res_pjsip_pubsub.c: No registered publish handler for event presence
[2016-02-03 19:40:36] WARNING[29713] res_pjsip_pubsub.c: No registered publish handler for event presence
[2016-02-03 20:17:53] WARNING[29713] res_pjsip_pubsub.c: No registered publish handler for event presence
[2016-02-03 20:22:53] WARNING[29713] res_pjsip_pubsub.c: No registered publish handler for event presence
[2016-02-03 20:25:36] WARNING[29713] res_pjsip_pubsub.c: No registered publish handler for event presence
[2016-02-03 20:30:36] WARNING[29713] res_pjsip_pubsub.c: No registered publish handler for event presence
[2016-02-03 21:07:54] WARNING[3449] res_pjsip_pubsub.c: No registered publish handler for event presence

 

[wa4zlw]

waiting for grandstream to talk to me I ran some tests. I created ext 710 with CHAN_SIP. Extension works no BLF. Looking at wireshark I see Status 401 Unauthorized to a subscribe request.

ASterisk Debug -- why is res_pjsip/pjsip_distributor.c showing up when x710 is CHAN_SIP. call was originated on x701 (PJSIP) --> x710 (CHAN_SIP) ??????

[2016-02-04 11:45:07] VERBOSE[8634][C-00000005] app_dial.c: Called SIP/710
[2016-02-04 11:45:07] VERBOSE[8634][C-00000005] app_dial.c: Connected line update to PJSIP/701-00000008 prevented.
[2016-02-04 11:45:07] VERBOSE[8634][C-00000005] app_dial.c: SIP/710-00000005 is ringing
[2016-02-04 11:45:08] NOTICE[12335] res_pjsip/pjsip_distributor.c: Request from '<sip:[email protected]>' failed for '70.a.b.c:5070' (callid: [email protected]) - No matching endpoint found
[2016-02-04 11:45:08] NOTICE[29713] res_pjsip/pjsip_distributor.c: Request from '<sip:[email protected]>' failed for '70.a.b.c:5070' (callid: [email protected]) - No matching endpoint found
[2016-02-04 11:45:09] NOTICE[3449] res_pjsip/pjsip_distributor.c: Request from '<sip:[email protected]>' failed for '70.a.b.c:5070' (callid: [email protected]) - No matching endpoint found
[2016-02-04 11:45:09] NOTICE[12335] res_pjsip/pjsip_distributor.c: Request from '<sip:[email protected]>' failed for '70.a.b.:5070' (callid: [email protected]) - No matching endpoint found
[2016-02-04 11:45:10] VERBOSE[8634][C-00000005] app_dial.c: Connected line update to PJSIP/701-00000008 prevented.
[2016-02-04 11:45:10] VERBOSE[8634][C-00000005] app_dial.c: SIP/710-00000005 answered PJSIP/701-00000008
[2016-02-04 11:45:10] VERBOSE[8636][C-00000005] bridge_channel.c: Channel SIP/710-00000005 joined 'simple_bridge' basic-bridge <6b090aa6-f4a6-4271-a9f0-4f72f00395a7>
[2016-02-04 11:45:10] VERBOSE[8634][C-00000005] bridge_channel.c: Channel PJSIP/701-00000008 joined 'simple_bridge' basic-bridge <6b090aa6-f4a6-4271-a9f0-4f72f00395a7>
[2016-02-04 11:45:10] NOTICE[12335] res_pjsip/pjsip_distributor.c: Request from '<sip:[email protected]>' failed for '70.a.b.c:5070' (callid: [email protected]) - No matching endpoint found

 

[wa4zlw]

Watchguard has been helping me diagnose some of the SIP stuff. Seems there are port issues. This is from my GXP2170 on x710 using CHAN_SIP on the PBX. Same device talks PJSIP to other extensions as noted above.

ANyone got any ideas? Should I recompile Asterisk????

Created By: John Berg (2/4/2016 10:21 AM)
Possibly all the BLF information is sent in these SIP/XML packets:

1942 2016-02-04 08:12:12.948278 10.195.13.72 45.x.y.z SIP/XML 960 Request: PUBLISH sip:[email protected]:5061 |
<presence
xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
entity="sip:[email protected]:5061">

You may chase down these two concepts:

1. What is this event?

1946 2016-02-04 08:12:12.969733 45.x.y.z 10.195.13.72 SIP 483 Status: 489 Bad Event |

2. Filtering by upd.port == 5061 indicates some port issues:

1048 2016-02-04 08:11:28.035424 10.195.13.72 45.x.y.z ICMP 592 Destination unreachable (Port unreachable)

John Berg

 

[wa4zlw]

Ok sports fans...if you noticed my recent post about recompiling. I just glanced over to the phone and I now see BLF for x701 and 702 (PJSIP) but NOT x710 (SIP)

still investigating. Definitely looks like missing pieces.

Leon

 

[wa4zlw]

Ok I've updated the second of three pbxes I have access to (the third I dont have CLI access). The upgrade/recompile step fixes the BLF issue from what I can see on the two boxes I have direct control over.

But on the GXP2170 we don't get a blinking indicator during ring yet, on the older GXP2000 we do. The support guy I've been working with at Grandstream was out today so hopefully he'll be back tomorrow.

I'll go around to my other devices tomorrow and make sure they work the same.

Looks like something went fubar on the builds we had installed initially.

Leon

 

[wa4zlw]

so far BLF is working with the old phones and partially with the new ones. Waiting on Grandstream reply this morning.

Leon

 

[wa4zlw]

Update: Heard from Grandstream this afternoon. They requested a few extensions so they can test with so they can get some SYSLOGS out of the phones. Seems I found a problem with BLF on the 2170. The 20xx are working fine all under PJSIP.

More to follow once I have it.

Leon

 

[wa4zlw]

another update from Grandstream:

Your server is behaving exactly the same as ours.

You are right, the phone displays red on VPK BLF on ringing while it should be blinking but It took me a while to notice that:

When the monitored phone is ringing, the VPK is red but displays a BELL (ringing)
When the monitored extension is busy, the VPK turns red and displays a HANDSET sign in the square.

I strongly disagree with this and I will put in a feature request to make it blink instead. There may be thousands of users out there with vision issues that will have hard time noticing such as small icon

The good thing is the SIP part of it is working properly. Notice that when the vpk is red with a Bell, you can press it to pick up the call for the monitored extension ( it sends a **720)

I'll let you know when the feature is implemented
Made by: Farid Ahcene on February 10, 2016 11:49

 

[krzykat]

Good, I just ordered a couple of 2170's for testing ... hopefully you help them get the f/w all patched up.

 

[wa4zlw]

Hi there!

so far things seem to be working. now that I know what to look for I can deal with it for now and the old phones work now too.

stay tuned.

Leon

 

[wa4zlw]

Hi there! Good news. There was a new release today for the 21xx series and the buttons now light up in addition to the LCD. As soon as I hear back tomorrow if I can release the URL I will do so.

Leon

 

[wa4zlw]

Here you go folks, it's not officially released just yet but RSN:

jax.grandstream.com/fahcene/GXP2170/gxp2170fw.bin --> 2170 obviously. Others change the model # in the filename.

you can also use http from the phone by using the full FQDN and grab/upgrade it that way (ldz)

Please download and unzip and use your local server to upgrade

It has the 4 firmware files for all models 2160/30/40/70

Made by: Farid Ahcene on February 22, 2016 14:38

 

[krzykat]

jax.grandstream.com/fahcene/GXP2160/gxp2160fw.bin gets 404 You have the link for it? 2170 works though.

 

[wa4zlw]

GOod morning that was my bad - he put that one .bin out for me.

the file that has all four are:

GXP21XX_COLOR_1_0_7_&_FW.zip

that has the four images and you have to use your own server to grab them until grandstream posts them in firmware.grandstream.com

leon

 

[wa4zlw]

Thanks...the following is not really good :-(

Firmware
Firmware for all Grandstream products are improved and updated on a regular basis. Please check for the latest upgrade for your product or sign up to receive newsletter for new/beta firmware releases.

** A note to all customers **

We will no longer be hosting public facing firmware files via our HTTP/HTTPS server for official firmware. We will only host BETA firmware which devices can still remotely upgrade from using our firmware.grandstream.com/BETA path. For official firmware upgrade, please download the necessary firmware file(s) from below and host them locally to perform future upgrades.

We apologize for any inconvenience moving forward.

 

[jerrm]

There have been real issues with the past few releases. They obviously haven't had enough bandwidth or infrastructure or both to deal with however many phones hit the server in the hours immediately after a release. Too bad they didn't invest in a fix, but better they kill it than have phones stuck in a loop trying to upgrade and timing out.

 

[wa4zlw]

yeah - i dont like the fact there is no public accessible release repository and they put it on the user to setup a repository.

leon

 

[wa4zlw]

they released some new code monday (?) for the new cordless and it seems to have solved my audio issues. They said it doesnt solved some of the audio issues. A new update should be out soon.

leon