SIP 484 address incomplete

[vieri]

Hi,

The dial-now string feature you're referring to depends exclusively on the client and I would need to setup all possible patterns on each client. This is not what I'm looking for. I need the server to decide if the dialed string matches the server's dialplan and in which case, it should notify the client accordingly. That's what "484 address incomplete" is for.

I already read that the Yealink manual specifies that it supports "484 address incomplete" before posting to the forum. However, it doesn't seem to be enabled by default.

I'm attaching a screenshot (yealink_484_t19p.png) of the packets found when a Yealink SIP-T19P tries to call another SIP extension (in this case callee 4053). It's clear that the Yealink client waits for user input and sends "4053" in just one request.

   

I'm attaching another screenshot (yealink_484_gxp2000.png) of the packets found when a Grandstream GXP2000 with "early dial" enabled tries to call another SIP extension (callee 4053). In this case you can see how the client first sends out the first digit "4" and the Asterisk server replies with "address incomplete", then the client sends a "40", etc., until it finally sends "4053" and the Asterisk server accepts the call because it matches a detsination in its dialplan.

   

So how can I truely enable "484 address incomplete" in the Yealink SIP-T19P firmware?

Thanks,

Vieri