Re: [cisco-voip] sip 404 not found for incoming calls

2020-04-30 Thread Anthony Holloway
While it's important to rest your SIP trunks, else they become cranky, it's
also important to reset them, sometimes more than once, to be sure it's
properly initialized with all of the current settings, etc.

I have wasted enough time in the past, just to see that it works after a
reset, that I now simply reset the trunk before spending anytime
troubleshooting.

Granted, this only applies to certain troubleshooting scenarios, like, if I
had an existing/working SIP Trunk, and my call center script isn't working
correctly, I'm not going to just go reset the SIP trunk.

However, if I am integrating a new IP Faxing Server into the environment,
and it has never worked before, then I will reset it.

Knowing when to reset is a bit of an art, because editing a CSS partition
order/member for your SIP Trunk does not require a reset, but editing the
SIP profile does.  Both are indirectly changing the SIP Trunk
functionality, so in a way, should be the same, but they're not.

On Thu, Apr 30, 2020 at 8:17 AM NateCCIE  wrote:

> Have you been resting the trunk in cucm after each of your changes?
>
> Sent from my iPhone
>
> On Apr 30, 2020, at 7:08 AM, naresh rathore  wrote:
>
> 
> hi
>
>
> Pls find the attached ccsip messages and cube config. i will send voice
> ccapi inout config tomorrow. outgoing call works fine but cucm respond with
> 404 message during incoming call attempt
>
>
> Regards
>
>
>
> --
> *From:* Ryan Huff 
> *Sent:* Thursday, April 30, 2020 10:50 PM
> *To:* naresh rathore 
> *Cc:* Amit Kumar ; cisco-voip@puck.nether.net <
> cisco-voip@puck.nether.net>
> *Subject:* Re: [cisco-voip] sip 404 not found for incoming calls
>
> Naresh,
>
> Any chance you could send a ccsip messages and a voice ccapi inout debug
> from a failed inbound call?
>
> Sent from my iPhone
>
> On Apr 30, 2020, at 06:28, naresh rathore  wrote:
>
> 
> hi
>
>
> I tried both, via translation pattern or directly pointing a particular
> number to phone but still the same result.
>
> Regards
>
>
> --
> *From:* Amit Kumar 
> *Sent:* Thursday, April 30, 2020 6:41 PM
> *To:* naresh rathore 
> *Cc:* James B ; cisco-voip@puck.nether.net <
> cisco-voip@puck.nether.net>
> *Subject:* Re: [cisco-voip] sip 404 not found for incoming calls
>
> Are you having a dn, exact to called number, of you are doing some
> translation, then make sure route pattern incoming css shoold have access
> to xlate pt. Nd xlate css shoud have access to phones pt.
>
> On Thu, Apr 30, 2020, 2:02 PM naresh rathore  wrote:
>
> hi,
>
>
> Thanks for the reply.
>
>
> pls see following snapshot and attached gateway config. outgoing dialpeer
> (200,201) is currently matching correctly to cucm (for incoming call)
>
>
>
>
>
>
>
> Regards
>
> Naray
> --
> *From:* James B 
> *Sent:* Thursday, April 30, 2020 5:39 PM
> *To:* naresh rathore ; cisco-voip@puck.nether.net <
> cisco-voip@puck.nether.net>
> *Subject:* RE: [cisco-voip] sip 404 not found for incoming calls
>
>
> Hello,
>
>
>
> Can you send your gateway configuration and a screenshot of your CUCM
> trunk configuration? That’d give us more to go off of.
>
>
>
> Thanks,
>
>
>
> James
>
>
>
>
>
>
>
> *From: *naresh rathore 
> *Sent: *30 April 2020 08:36
> *To: *cisco-voip@puck.nether.net
> *Subject: *[cisco-voip] sip 404 not found for incoming calls
>
>
>
> hi,
>
>
>
>
>
>
>
> i have cucm version 12.0. outgoing call is working without any issue. but
> incoming call is failing. the call request is received by cucm but its
> responding with 404 not found. i checked CSS and also pointed call directly
> to ip phone using significant digits and incoming css but still the same
> issue. also sip uri have called number. not sure why 404 not found msg is
> sent by cucm to cube.
>
>
>
>
>
> Regards
>
>
>
> Naray
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C01617e1596284dca88b408d7ecf129b1%7C84df9e7fe9f640afb435%7C1%7C0%7C637238392830409694&sdata=hxzkpvvwAxXyygB9nHWJ9muvREigqaBddZmALmRdycw%3D&reserved=0>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F

Re: [cisco-voip] sip 404 not found for incoming calls

2020-04-30 Thread Ryan Huff
Thanks.

The 404 is sourced from the gi1/0/1 interface IP address. If CUCM initiated the 
404 I would expect CUCM’s IP address to be the source of the 404.

It seems like this is config as “sip on a stick” (a router with a single 
interface used for inbound and outbound SIP traffic). A little more 
challenging, not impossible, but more challenging.

It would be outstanding if you could make the gi0/0/0 interface an “outside” 
interface in a different network, then bind the dial peers appropriately... 
again, not material to the issue outhand.

Once you have the inout debuts, please send it ove.

Sent from my iPhone

On Apr 30, 2020, at 09:06, naresh rathore  wrote:


hi


Pls find the attached ccsip messages and cube config. i will send voice ccapi 
inout config tomorrow. outgoing call works fine but cucm respond with 404 
message during incoming call attempt


Regards




From: Ryan Huff 
Sent: Thursday, April 30, 2020 10:50 PM
To: naresh rathore 
Cc: Amit Kumar ; cisco-voip@puck.nether.net 

Subject: Re: [cisco-voip] sip 404 not found for incoming calls

Naresh,

Any chance you could send a ccsip messages and a voice ccapi inout debug from a 
failed inbound call?

Sent from my iPhone

On Apr 30, 2020, at 06:28, naresh rathore  wrote:


hi


I tried both, via translation pattern or directly pointing a particular number 
to phone but still the same result.

Regards



From: Amit Kumar 
Sent: Thursday, April 30, 2020 6:41 PM
To: naresh rathore 
Cc: James B ; cisco-voip@puck.nether.net 

Subject: Re: [cisco-voip] sip 404 not found for incoming calls

Are you having a dn, exact to called number, of you are doing some translation, 
then make sure route pattern incoming css shoold have access to xlate pt. Nd 
xlate css shoud have access to phones pt.

On Thu, Apr 30, 2020, 2:02 PM naresh rathore 
mailto:nare...@hotmail.com>> wrote:
hi,


Thanks for the reply.


pls see following snapshot and attached gateway config. outgoing dialpeer 
(200,201) is currently matching correctly to cucm (for incoming call)

[cid:9c8082fb-a47a-4859-8d73-bd22200523c5]
[cid:f721c217-c6cf-4fd5-bbc6-10962f7f7269]
[cid:2300f744-b399-4d90-ab4b-133bb37a3611]
[cid:a2643290-7308-42d9-b6bc-699c2df07a6f]


Regards

Naray

From: James B mailto:james.buchan...@gmail.com>>
Sent: Thursday, April 30, 2020 5:39 PM
To: naresh rathore mailto:nare...@hotmail.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> 
mailto:cisco-voip@puck.nether.net>>
Subject: RE: [cisco-voip] sip 404 not found for incoming calls


Hello,



Can you send your gateway configuration and a screenshot of your CUCM trunk 
configuration? That’d give us more to go off of.



Thanks,



James







From: naresh rathore<mailto:nare...@hotmail.com>
Sent: 30 April 2020 08:36
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] sip 404 not found for incoming calls



hi,







i have cucm version 12.0. outgoing call is working without any issue. but 
incoming call is failing. the call request is received by cucm but its 
responding with 404 not found. i checked CSS and also pointed call directly to 
ip phone using significant digits and incoming css but still the same issue. 
also sip uri have called number. not sure why 404 not found msg is sent by cucm 
to cube.





Regards



Naray



___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C6523e72539454f133b1408d7ed073f58%7C84df9e7fe9f640afb435%7C1%7C0%7C637238487707512961&sdata=AGbxo4YndgaFtcJPGOkk1c71IwqeCBpLXtFJ1adJ0NM%3D&reserved=0>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C01617e1596284dca88b408d7ecf129b1%7C84df9e7fe9f640afb435%7C1%7C0%7C637238392830439677&sdata=%2BBocnzBxzrQDeGY8H4FLLCSBtxWvNCm8i%2FY8km%2F3t7o%3D&reserved=0


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] sip 404 not found for incoming calls

2020-04-30 Thread NateCCIE
Have you been resting the trunk in cucm after each of your changes?

Sent from my iPhone

> On Apr 30, 2020, at 7:08 AM, naresh rathore  wrote:
> 
> 
> hi
> 
> 
> Pls find the attached ccsip messages and cube config. i will send voice ccapi 
> inout config tomorrow. outgoing call works fine but cucm respond with 404 
> message during incoming call attempt
> 
> 
> Regards
> 
> 
> 
> From: Ryan Huff 
> Sent: Thursday, April 30, 2020 10:50 PM
> To: naresh rathore 
> Cc: Amit Kumar ; cisco-voip@puck.nether.net 
> 
> Subject: Re: [cisco-voip] sip 404 not found for incoming calls
>  
> Naresh,
> 
> Any chance you could send a ccsip messages and a voice ccapi inout debug from 
> a failed inbound call?
> 
> Sent from my iPhone
> 
>>> On Apr 30, 2020, at 06:28, naresh rathore  wrote:
>>> 
>> 
>> hi
>> 
>> 
>> I tried both, via translation pattern or directly pointing a particular 
>> number to phone but still the same result.
>> 
>> Regards
>> 
>> 
>> From: Amit Kumar 
>> Sent: Thursday, April 30, 2020 6:41 PM
>> To: naresh rathore 
>> Cc: James B ; cisco-voip@puck.nether.net 
>> 
>> Subject: Re: [cisco-voip] sip 404 not found for incoming calls
>>  
>> Are you having a dn, exact to called number, of you are doing some 
>> translation, then make sure route pattern incoming css shoold have access to 
>> xlate pt. Nd xlate css shoud have access to phones pt. 
>> 
>> On Thu, Apr 30, 2020, 2:02 PM naresh rathore  wrote:
>> hi,
>> 
>> 
>> Thanks for the reply. 
>> 
>> 
>> pls see following snapshot and attached gateway config. outgoing dialpeer 
>> (200,201) is currently matching correctly to cucm (for incoming call)
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Regards
>> 
>> Naray
>> From: James B 
>> Sent: Thursday, April 30, 2020 5:39 PM
>> To: naresh rathore ; cisco-voip@puck.nether.net 
>> 
>> Subject: RE: [cisco-voip] sip 404 not found for incoming calls
>>  
>> Hello,
>>  
>> Can you send your gateway configuration and a screenshot of your CUCM trunk 
>> configuration? That’d give us more to go off of.
>>  
>> Thanks,
>>  
>> James
>>  
>>  
>>  
>> From: naresh rathore
>> Sent: 30 April 2020 08:36
>> To: cisco-voip@puck.nether.net
>> Subject: [cisco-voip] sip 404 not found for incoming calls
>>  
>> hi,
>>  
>>  
>>  
>> i have cucm version 12.0. outgoing call is working without any issue. but 
>> incoming call is failing. the call request is received by cucm but its 
>> responding with 404 not found. i checked CSS and also pointed call directly 
>> to ip phone using significant digits and incoming css but still the same 
>> issue. also sip uri have called number. not sure why 404 not found msg is 
>> sent by cucm to cube.
>>  
>>  
>> Regards
>>  
>> Naray
>>  
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C01617e1596284dca88b408d7ecf129b1%7C84df9e7fe9f640afb435%7C1%7C0%7C637238392830439677&sdata=%2BBocnzBxzrQDeGY8H4FLLCSBtxWvNCm8i%2FY8km%2F3t7o%3D&reserved=0
> 
> 
> 
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] sip 404 not found for incoming calls

2020-04-30 Thread Ryan Huff
Naresh,

Any chance you could send a ccsip messages and a voice ccapi inout debug from a 
failed inbound call?

Sent from my iPhone

On Apr 30, 2020, at 06:28, naresh rathore  wrote:


hi


I tried both, via translation pattern or directly pointing a particular number 
to phone but still the same result.

Regards



From: Amit Kumar 
Sent: Thursday, April 30, 2020 6:41 PM
To: naresh rathore 
Cc: James B ; cisco-voip@puck.nether.net 

Subject: Re: [cisco-voip] sip 404 not found for incoming calls

Are you having a dn, exact to called number, of you are doing some translation, 
then make sure route pattern incoming css shoold have access to xlate pt. Nd 
xlate css shoud have access to phones pt.

On Thu, Apr 30, 2020, 2:02 PM naresh rathore 
mailto:nare...@hotmail.com>> wrote:
hi,


Thanks for the reply.


pls see following snapshot and attached gateway config. outgoing dialpeer 
(200,201) is currently matching correctly to cucm (for incoming call)

[cid:9c8082fb-a47a-4859-8d73-bd22200523c5]
[cid:f721c217-c6cf-4fd5-bbc6-10962f7f7269]
[cid:2300f744-b399-4d90-ab4b-133bb37a3611]
[cid:a2643290-7308-42d9-b6bc-699c2df07a6f]


Regards

Naray

From: James B mailto:james.buchan...@gmail.com>>
Sent: Thursday, April 30, 2020 5:39 PM
To: naresh rathore mailto:nare...@hotmail.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> 
mailto:cisco-voip@puck.nether.net>>
Subject: RE: [cisco-voip] sip 404 not found for incoming calls


Hello,



Can you send your gateway configuration and a screenshot of your CUCM trunk 
configuration? That’d give us more to go off of.



Thanks,



James







From: naresh rathore<mailto:nare...@hotmail.com>
Sent: 30 April 2020 08:36
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] sip 404 not found for incoming calls



hi,







i have cucm version 12.0. outgoing call is working without any issue. but 
incoming call is failing. the call request is received by cucm but its 
responding with 404 not found. i checked CSS and also pointed call directly to 
ip phone using significant digits and incoming css but still the same issue. 
also sip uri have called number. not sure why 404 not found msg is sent by cucm 
to cube.





Regards



Naray



___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C01617e1596284dca88b408d7ecf129b1%7C84df9e7fe9f640afb435%7C1%7C0%7C637238392830409694&sdata=hxzkpvvwAxXyygB9nHWJ9muvREigqaBddZmALmRdycw%3D&reserved=0>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C01617e1596284dca88b408d7ecf129b1%7C84df9e7fe9f640afb435%7C1%7C0%7C637238392830439677&sdata=%2BBocnzBxzrQDeGY8H4FLLCSBtxWvNCm8i%2FY8km%2F3t7o%3D&reserved=0
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] sip 404 not found for incoming calls

2020-04-30 Thread Pawlowski, Adam
What does the dialed number analyzer tool tell you?

Is there some digit manipulation going on ? You're not somehow using this 
trunk/port for registrations ? Messaging inbound is using a domain or address 
the UCM is going to respond to ?

Adam

From: cisco-voip  On Behalf Of naresh 
rathore
Sent: Thursday, April 30, 2020 6:27 AM
To: Amit Kumar 
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] sip 404 not found for incoming calls

hi


I tried both, via translation pattern or directly pointing a particular number 
to phone but still the same result.

Regards



From: Amit Kumar mailto:amit3@gmail.com>>
Sent: Thursday, April 30, 2020 6:41 PM
To: naresh rathore mailto:nare...@hotmail.com>>
Cc: James B mailto:james.buchan...@gmail.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> 
mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] sip 404 not found for incoming calls

Are you having a dn, exact to called number, of you are doing some translation, 
then make sure route pattern incoming css shoold have access to xlate pt. Nd 
xlate css shoud have access to phones pt.

On Thu, Apr 30, 2020, 2:02 PM naresh rathore 
mailto:nare...@hotmail.com>> wrote:
hi,


Thanks for the reply.


pls see following snapshot and attached gateway config. outgoing dialpeer 
(200,201) is currently matching correctly to cucm (for incoming call)

[cid:9c8082fb-a47a-4859-8d73-bd22200523c5]
[cid:f721c217-c6cf-4fd5-bbc6-10962f7f7269]
[cid:2300f744-b399-4d90-ab4b-133bb37a3611]
[cid:a2643290-7308-42d9-b6bc-699c2df07a6f]


Regards

Naray

From: James B mailto:james.buchan...@gmail.com>>
Sent: Thursday, April 30, 2020 5:39 PM
To: naresh rathore mailto:nare...@hotmail.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> 
mailto:cisco-voip@puck.nether.net>>
Subject: RE: [cisco-voip] sip 404 not found for incoming calls


Hello,



Can you send your gateway configuration and a screenshot of your CUCM trunk 
configuration? That'd give us more to go off of.



Thanks,



James







From: naresh rathore<mailto:nare...@hotmail.com>
Sent: 30 April 2020 08:36
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] sip 404 not found for incoming calls



hi,







i have cucm version 12.0. outgoing call is working without any issue. but 
incoming call is failing. the call request is received by cucm but its 
responding with 404 not found. i checked CSS and also pointed call directly to 
ip phone using significant digits and incoming css but still the same issue. 
also sip uri have called number. not sure why 404 not found msg is sent by cucm 
to cube.





Regards



Naray


___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] sip 404 not found for incoming calls

2020-04-30 Thread naresh rathore
hi


I tried both, via translation pattern or directly pointing a particular number 
to phone but still the same result.

Regards



From: Amit Kumar 
Sent: Thursday, April 30, 2020 6:41 PM
To: naresh rathore 
Cc: James B ; cisco-voip@puck.nether.net 

Subject: Re: [cisco-voip] sip 404 not found for incoming calls

Are you having a dn, exact to called number, of you are doing some translation, 
then make sure route pattern incoming css shoold have access to xlate pt. Nd 
xlate css shoud have access to phones pt.

On Thu, Apr 30, 2020, 2:02 PM naresh rathore 
mailto:nare...@hotmail.com>> wrote:
hi,


Thanks for the reply.


pls see following snapshot and attached gateway config. outgoing dialpeer 
(200,201) is currently matching correctly to cucm (for incoming call)

[cid:9c8082fb-a47a-4859-8d73-bd22200523c5]
[cid:f721c217-c6cf-4fd5-bbc6-10962f7f7269]
[cid:2300f744-b399-4d90-ab4b-133bb37a3611]
[cid:a2643290-7308-42d9-b6bc-699c2df07a6f]


Regards

Naray

From: James B mailto:james.buchan...@gmail.com>>
Sent: Thursday, April 30, 2020 5:39 PM
To: naresh rathore mailto:nare...@hotmail.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> 
mailto:cisco-voip@puck.nether.net>>
Subject: RE: [cisco-voip] sip 404 not found for incoming calls


Hello,



Can you send your gateway configuration and a screenshot of your CUCM trunk 
configuration? That’d give us more to go off of.



Thanks,



James







From: naresh rathore<mailto:nare...@hotmail.com>
Sent: 30 April 2020 08:36
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] sip 404 not found for incoming calls



hi,







i have cucm version 12.0. outgoing call is working without any issue. but 
incoming call is failing. the call request is received by cucm but its 
responding with 404 not found. i checked CSS and also pointed call directly to 
ip phone using significant digits and incoming css but still the same issue. 
also sip uri have called number. not sure why 404 not found msg is sent by cucm 
to cube.





Regards



Naray



___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] sip 404 not found for incoming calls

2020-04-30 Thread James B
Hello, Can you send your gateway configuration and a screenshot of your CUCM trunk configuration? That’d give us more to go off of. Thanks, James   From: naresh rathoreSent: 30 April 2020 08:36To: cisco-voip@puck.nether.netSubject: [cisco-voip] sip 404 not found for incoming calls hi,   i have cucm version 12.0. outgoing call is working without any issue. but incoming call is failing. the call request is received by cucm but its responding with 404 not found. i checked CSS and also pointed call directly to ip phone using significant digits and incoming css but still the same issue. also sip uri have called number. not sure why 404 not found msg is sent by cucm to cube.  Regards Naray 
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


[cisco-voip] sip 404 not found for incoming calls

2020-04-30 Thread naresh rathore
hi,



i have cucm version 12.0. outgoing call is working without any issue. but 
incoming call is failing. the call request is received by cucm but its 
responding with 404 not found. i checked CSS and also pointed call directly to 
ip phone using significant digits and incoming css but still the same issue. 
also sip uri have called number. not sure why 404 not found msg is sent by cucm 
to cube.


Regards

Naray
Apr 30 15:36:07.075: //-1//SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.11.162.253:5060 SIP/2.0
Via: SIP/2.0/TCP 10.10.16.101:5060;branch=z9hG4bKac40e360612d2
From: ;tag=945014576
To: 
Date: Thu, 30 Apr 2020 05:36:07 GMT
Call-ID: 7c19c300-1eb1a8a7-98413-65100a0a@10.10.16.101
User-Agent: Cisco-CUCM12.5
CSeq: 101 OPTIONS
Contact: 
Max-Forwards: 0
Content-Length: 0


Apr 30 15:36:07.077: //-1//SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.10.16.101:5060;branch=z9hG4bKac40e360612d2
From: ;tag=945014576
To: ;tag=958B7013-8B8
Date: Thu, 30 Apr 2020 05:36:07 GMT
Call-ID: 7c19c300-1eb1a8a7-98413-65100a0a@10.10.16.101
Server: Cisco-SIPGateway/IOS-16.6.4
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, 
NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 172

v=0
o=CiscoSystemsSIP-GW-UserAgent 7967 2005 IN IP4 10.11.162.253
s=SIP Call
c=IN IP4 10.11.162.253
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 10.11.162.253

Apr 30 15:37:01.181: //-1//SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.11.162.253:5060 SIP/2.0
Via: SIP/2.0/TCP 10.10.160.101:5060;branch=z9hG4bK3f58f704715f6
From: ;tag=455360857
To: 
Date: Thu, 30 Apr 2020 05:37:01 GMT
Call-ID: 9c498200-1eb1a8a7-3f3dc-65a00a0a@10.10.160.101
User-Agent: Cisco-CUCM12.5
CSeq: 101 OPTIONS
Contact: 
Max-Forwards: 0
Content-Length: 0


Apr 30 15:37:01.182: //-1//SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.10.160.101:5060;branch=z9hG4bK3f58f704715f6
From: ;tag=455360857
To: ;tag=958C436C-2618
Date: Thu, 30 Apr 2020 05:37:01 GMT
Call-ID: 9c498200-1eb1a8a7-3f3dc-65a00a0a@10.10.160.101
Server: Cisco-SIPGateway/IOS-16.6.4
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, 
NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 172

v=0
o=CiscoSystemsSIP-GW-UserAgent 7492 3960 IN IP4 10.11.162.253
s=SIP Call
c=IN IP4 10.11.162.253
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 10.11.162.253

Apr 30 15:37:07.844: //-1//SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.11.162.253:5060 SIP/2.0
Via: SIP/2.0/TCP 10.10.16.101:5060;branch=z9hG4bKac41f133e465f
From: ;tag=1449156682
To: 
Date: Thu, 30 Apr 2020 05:37:07 GMT
Call-ID: 9fdd0900-1eb1a8a7-9841c-65100a0a@10.10.16.101
User-Agent: Cisco-CUCM12.5
CSeq: 101 OPTIONS
Contact: 
Max-Forwards: 0
Content-Length: 0


Apr 30 15:37:07.846: //-1//SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.10.16.101:5060;branch=z9hG4bKac41f133e465f
From: ;tag=1449156682
To: ;tag=958C5D74-1A6C
Date: Thu, 30 Apr 2020 05:37:07 GMT
Call-ID: 9fdd0900-1eb1a8a7-9841c-65100a0a@10.10.16.101
Server: Cisco-SIPGateway/IOS-16.6.4
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, 
NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 172

v=0
o=CiscoSystemsSIP-GW-UserAgent 3546 5802 IN IP4 10.11.162.253
s=SIP Call
c=IN IP4 10.11.162.253
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 10.11.162.253

Apr 30 15:38:02.499: //-1//SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.11.162.253:5060 SIP/2.0
Via: SIP/2.0/TCP 10.10.160.101:5060;branch=z9hG4bK3f5957a97b787
From: ;tag=1212600559
To: 
Date: Thu, 30 Apr 2020 05:38:02 GMT
Call-ID: c0a55e80-1eb1a8a7-3f3e2-65a00a0a@10.10.160.101
User-Agent: Cisco-CUCM12.5
CSeq: 101 OPTIONS
Contact: 
Max-Forwards: 0
Content-Length: 0


Apr 30 15:38:02.501: //-1//SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.10.160.101:5060;branch=z9hG4bK3f5957a97b787
From: ;tag=1212600559
To: ;tag=958D32F2-20CF
Date: Thu, 30 Apr 2020 05:38:02 GMT
Call-ID: c0a55e80-1eb1a8a7-3f3e2-65a00a0a@10.10.160.101
Server: Cisco-SIPGateway/IOS-16.6.4
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, 
NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 172

v=0
o=CiscoSystemsSIP-GW-UserAgent 5297 3081 IN IP4 10.11.162.253
s=SIP Call
c=IN IP4 10.11.162.253
t=0 0
m=audio 0 RTP/AVP 18 0 8