CME SIP Call Pickup - SIP/2.0 484 Address Incomplete

[douglasfir]

Hi,

I configured SIP phones with CME and I have inbound and outbound calls working fine. Also call pickup works fine when only local phones are involved.

But when the call comes in via SIP trunk and I try to pick it up within the same pickup group, I get busy tone. The ringing to initial destination stays, but I am not able to pick the call.

I did some debug ccsip messages and what I can see is:

SIP/2.0 484 Address Incomplete

At the same time, call transfer works fine for external inbound calls too.

Did anyone have similar problem? I can also provide more details from the trace, I just didn't want to bother from the start :)

Thanks in advance!

Regards, Dragan

[Nadeem Ahmed · Accepted solution]

please post the show run and along with traces/debug

make one test call run below debugs

debug ccsip messages

debug ccsip event/error

debug voice ccapi inout.

Br,

Nadeem Ahmed

PS: Please rate all useful post.

[douglasfir]

Hi Nadeem,

I made some traces yesterday before writing at forum, but I hope they can be useful. If not, I can make new ones in a day or two.

The first log is related to unsuccessful pickup when the call is coming via SIP trunk.

The second log is for the internal call and successful pickup.

The third file is running config.

I will try to provide more logs as soon as possible! I also have debug voice dialpeer if it means something...

Thanks!

Regards, Dragan

[Arnoldo]

Hello draganmarkovic,

You could fix this error?
Regards,
Arnoldo

[douglasfir]

Sorry Ahmed,

I clicked as correct answer by mistake, but thank you for response. I've attached some traces in previous response, I hope they can provide some clue.

By the way, what can't be seen from "show run" is TCL script that I use to edit SIP header a bit, because provider sends a leading number in INVITE line and the exact number to be called in TO field, for instance:

INVITE sip:381116350100@10.1.13.250:5060 SIP/2.0

To: "381116350109 381116350109"<sip:381116350109@ims.telecommprovider.com>;cscf

Here is also TCL script in attachment.

Thanks!

Regards, Dragan

[Rajan]

Hi Dragon,

In the Invite received from the phone in which the pickup option is pressed, able to see the below in the headers:

*Dec 15 12:50:32.913: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:service-uri-pickup@192.168.50.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.50.15:5060;branch=z9hG4bK599d6973
From: "Small Conference" <sip:107@192.168.50.1>;tag=f0b2e577f7d800500120c8cb-1205e511
To: <sip:service-uri-pickup@192.168.50.1>
Call-ID: f0b2e577-f7d8001e-0a054c7d-61c18aa7@192.168.50.15
Max-Forwards: 70
Date: Tue, 15 Dec 2015 12:50:32 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CP7821/10.3.1

This (sip:107@192.168.50.1)is fine in case of internal calls. But guess this kind of representation"sip:381116350107@ims.telecommprovider.com" is expected as per the error "484 Address Incomplete". Probably others can confirm whether this is needed or not.

HTH

Rajan

[douglasfir]

Hi Rajan,

Thanks for the answer. I was suspecting on that one too, however what here confuses me is that there is no message sent to provider in this case..it seems to be sent directly from CME.

I've attached a diagram from TranslatorX (ims.telecommprovider.com and 192.168.50.1 are two interfaces of CME).

Regards, Dragan

[Vivek Batra]

Hi,

I tried to simulate the same and initially found the same issue what you are getting. Following configuration then worked for me for direct pickup;

telephony-service

    service directed-pickup gpickup

    call-park system application

voice register dn <tag>

    pickup-group <group_number> (configure this in both voice register dn)

 Enter create cnf-file and create profile and restart the phones, and see if it works for you.

- Vivek

[douglasfir]

Hi Vivek,

Thanks for the answer! I will definitely try it tomorrow. I don't have a remote access to the customer, so I must go onsite.

Regards, Dragan

[douglasfir]

Hi Vivek,

I checked the running config and it turned out that I already had these lines configured before...but today I asked provider to make Request-URI and TO line point to the same destination number and not Request-URI showing trunk group value.

Then I was able to remove TCL script from inbound dial peer and use regular translation profile. At that moment call pick up suddenly started to work :)

Regards, Dragan