Mailing List Archive

404 not found means just that. If this is an inbound leg check the Calling search space for the sip gateway.



> On Oct 13, 2019, at 7:58 PM, Dana Tong <dana.tong@yellit.com.au> wrote:
>
> Hi all,
>
> Customer recently changed from ISDN gateways (H323 registered) to centralised SIP and now the UCCX IVR isn’t working.
>
> The SIP trunk is set to use the 64K region and I did also try setting the CODEC to both G.711alaw and ulaw on the dial-peers on the SIP CUBE router.
> It’s weird.
>
> The debug CCSIP messages are showing 404 not found, and the voip dialpeer inout were showing a match on the correct dial-peers.
> But then the logs say no match as per below.
>
> Anyone seen this kind of error after changing from ISDN to SIP?
>
> Somewhat sanitised below. Trying to get RTMT access.
>
>
>
> Sent:
> SIP/2.0 404 Not Found
> Via: SIP/2.0/UDP 203.52.3.164:5060;branch=z9hG4bKritgbh304ou76jse28v0.1
> From: <sip:000000@10.119.243.144;user=phone <sip:000000@10.119.243.144;user=phone>>;tag=39906919-1571014929892-
> To: "777 777"<sip:754420777@customer.com.au;user=phone <sip:754420777@customer.com.au;user=phone>>;tag=EDD3AA89-2562
> Date: Mon, 14 Oct 2019 11:02:09 GMT
> Call-ID: BW120209892141019-860012483@10.10.10.10 <mailto:BW120209892141019-860012483@10.10.10.10>
> CSeq: 602191603 INVITE
> Allow-Events: telephone-event
> Warning: 399 10.10.253.10 "No matching outgoing dial-peer"
> Server: Cisco-SIPGateway/IOS-15.5.3.S4b
> Reason: Q.850;cause=1
> Content-Length: 0
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip <https://puck.nether.net/mailman/listinfo/cisco-voip>

Are you using early offer in from the gateway?

How about best effort MTP option? (Sorry don’t remember exact verbage)

Might need CUCM logs, to see what CUCM is doing with it.

> On Oct 13, 2019, at 7:58 PM, Dana Tong <dana.tong@yellit.com.au> wrote:
>
> Hi all,
>
> Customer recently changed from ISDN gateways (H323 registered) to centralised SIP and now the UCCX IVR isn’t working.
>
> The SIP trunk is set to use the 64K region and I did also try setting the CODEC to both G.711alaw and ulaw on the dial-peers on the SIP CUBE router.
> It’s weird.
>
> The debug CCSIP messages are showing 404 not found, and the voip dialpeer inout were showing a match on the correct dial-peers.
> But then the logs say no match as per below.
>
> Anyone seen this kind of error after changing from ISDN to SIP?
>
> Somewhat sanitised below. Trying to get RTMT access.
>
>
>
> Sent:
> SIP/2.0 404 Not Found
> Via: SIP/2.0/UDP 203.52.3.164:5060;branch=z9hG4bKritgbh304ou76jse28v0.1
> From: <sip:000000@10.119.243.144;user=phone <sip:000000@10.119.243.144;user=phone>>;tag=39906919-1571014929892-
> To: "777 777"<sip:754420777@customer.com.au;user=phone <sip:754420777@customer.com.au;user=phone>>;tag=EDD3AA89-2562
> Date: Mon, 14 Oct 2019 11:02:09 GMT
> Call-ID: BW120209892141019-860012483@10.10.10.10 <mailto:BW120209892141019-860012483@10.10.10.10>
> CSeq: 602191603 INVITE
> Allow-Events: telephone-event
> Warning: 399 10.10.253.10 "No matching outgoing dial-peer"
> Server: Cisco-SIPGateway/IOS-15.5.3.S4b
> Reason: Q.850;cause=1
> Content-Length: 0
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip <https://puck.nether.net/mailman/listinfo/cisco-voip>

Sort of sounds like you may have a Class of Service (CSS/Partition) issue with the SIP trunk between CUBE and CUCM, since that is most likely the most significant configuration change/add since moving to SIP, that could generate 404 responses.

Could also be an issue with the device pool on the SIP trunk, depending on how you have the dialplan structured.

CUCM Generally won’t issue a station not found (404) message, unless CUCM ingress element (the SIP trunk) doesn’t find the station; either because the station doesn’t truly exist, or doesn’t exist in the configuration context it has access to.

Regional problems would issue a 404 generally.

Sent from my iPhone

On Oct 13, 2019, at 21:58, Dana Tong <dana.tong@yellit.com.au> wrote:

?
Hi all,

Customer recently changed from ISDN gateways (H323 registered) to centralised SIP and now the UCCX IVR isn’t working.

The SIP trunk is set to use the 64K region and I did also try setting the CODEC to both G.711alaw and ulaw on the dial-peers on the SIP CUBE router.
It’s weird.

The debug CCSIP messages are showing 404 not found, and the voip dialpeer inout were showing a match on the correct dial-peers.
But then the logs say no match as per below.

Anyone seen this kind of error after changing from ISDN to SIP?

Somewhat sanitised below. Trying to get RTMT access.



Sent:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 203.52.3.164:5060;branch=z9hG4bKritgbh304ou76jse28v0.1
From: <sip:000000@10.119.243.144;user=phone>;tag=39906919-1571014929892-
To: "777 777"<sip:754420777@customer.com.au;user=phone>;tag=EDD3AA89-2562
Date: Mon, 14 Oct 2019 11:02:09 GMT
Call-ID: BW120209892141019-860012483@10.10.10.10
CSeq: 602191603 INVITE
Allow-Events: telephone-event
Warning: 399 10.10.253.10 "No matching outgoing dial-peer"
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Reason: Q.850;cause=1
Content-Length: 0
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7Cf8a7858daf594c9c0c1f08d7504a0d4c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066151290735716&amp;sdata=MEMPChCZTf9Fkl4a7n%2BVjLO%2Fkd2gkOVy20TqdO0ZBss%3D&amp;reserved=0

*** Regional issues would NOT cause a 404 response generally.

Sent from my iPhone

On Oct 13, 2019, at 22:15, Ryan Huff <ryanhuff@outlook.com> wrote:

? Sort of sounds like you may have a Class of Service (CSS/Partition) issue with the SIP trunk between CUBE and CUCM, since that is most likely the most significant configuration change/add since moving to SIP, that could generate 404 responses.

Could also be an issue with the device pool on the SIP trunk, depending on how you have the dialplan structured.

CUCM Generally won’t issue a station not found (404) message, unless CUCM ingress element (the SIP trunk) doesn’t find the station; either because the station doesn’t truly exist, or doesn’t exist in the configuration context it has access to.

Regional problems would issue a 404 generally.

Sent from my iPhone

On Oct 13, 2019, at 21:58, Dana Tong <dana.tong@yellit.com.au> wrote:

?
Hi all,

Customer recently changed from ISDN gateways (H323 registered) to centralised SIP and now the UCCX IVR isn’t working.

The SIP trunk is set to use the 64K region and I did also try setting the CODEC to both G.711alaw and ulaw on the dial-peers on the SIP CUBE router.
It’s weird.

The debug CCSIP messages are showing 404 not found, and the voip dialpeer inout were showing a match on the correct dial-peers.
But then the logs say no match as per below.

Anyone seen this kind of error after changing from ISDN to SIP?

Somewhat sanitised below. Trying to get RTMT access.



Sent:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 203.52.3.164:5060;branch=z9hG4bKritgbh304ou76jse28v0.1
From: <sip:000000@10.119.243.144;user=phone>;tag=39906919-1571014929892-
To: "777 777"<sip:754420777@customer.com.au;user=phone>;tag=EDD3AA89-2562
Date: Mon, 14 Oct 2019 11:02:09 GMT
Call-ID: BW120209892141019-860012483@10.10.10.10
CSeq: 602191603 INVITE
Allow-Events: telephone-event
Warning: 399 10.10.253.10 "No matching outgoing dial-peer"
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Reason: Q.850;cause=1
Content-Length: 0
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7Cf8a7858daf594c9c0c1f08d7504a0d4c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066151290735716&amp;sdata=MEMPChCZTf9Fkl4a7n%2BVjLO%2Fkd2gkOVy20TqdO0ZBss%3D&amp;reserved=0
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7Cc730cfd38ea844c2a80808d7504c69de%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066161430811593&amp;sdata=pXmnFKefxRS%2FQkrQI%2FSFOG1rn%2Bdh5Xm2WeFfwX8TWTA%3D&amp;reserved=0

Ryan, that’s what I was thinking, but when Dana said to a station works fine, I started thinking a bit like some of the fun and weird messages that show up with codecs, etc. (basically codec mismatch and a bounce off to another number/pattern and that failed it…. Might need a few logs to see what its doing with uccx in the mix.



> On Oct 13, 2019, at 8:15 PM, Ryan Huff <ryanhuff@outlook.com> wrote:
>
> Sort of sounds like you may have a Class of Service (CSS/Partition) issue with the SIP trunk between CUBE and CUCM, since that is most likely the most significant configuration change/add since moving to SIP, that could generate 404 responses.
>
> Could also be an issue with the device pool on the SIP trunk, depending on how you have the dialplan structured.
>
> CUCM Generally won’t issue a station not found (404) message, unless CUCM ingress element (the SIP trunk) doesn’t find the station; either because the station doesn’t truly exist, or doesn’t exist in the configuration context it has access to.
>
> Regional problems would issue a 404 generally.
>
> Sent from my iPhone
>
>> On Oct 13, 2019, at 21:58, Dana Tong <dana.tong@yellit.com.au> wrote:
>>
>> ?
>> Hi all,
>>
>> Customer recently changed from ISDN gateways (H323 registered) to centralised SIP and now the UCCX IVR isn’t working.
>>
>> The SIP trunk is set to use the 64K region and I did also try setting the CODEC to both G.711alaw and ulaw on the dial-peers on the SIP CUBE router.
>> It’s weird.
>>
>> The debug CCSIP messages are showing 404 not found, and the voip dialpeer inout were showing a match on the correct dial-peers.
>> But then the logs say no match as per below.
>>
>> Anyone seen this kind of error after changing from ISDN to SIP?
>>
>> Somewhat sanitised below. Trying to get RTMT access.
>>
>>
>>
>> Sent:
>> SIP/2.0 404 Not Found
>> Via: SIP/2.0/UDP 203.52.3.164:5060;branch=z9hG4bKritgbh304ou76jse28v0.1
>> From: <sip:000000@10.119.243.144;user=phone>;tag=39906919-1571014929892-
>> To: "777 777"<sip:754420777@customer.com.au;user=phone>;tag=EDD3AA89-2562
>> Date: Mon, 14 Oct 2019 11:02:09 GMT
>> Call-ID: BW120209892141019-860012483@10.10.10.10
>> CSeq: 602191603 INVITE
>> Allow-Events: telephone-event
>> Warning: 399 10.10.253.10 "No matching outgoing dial-peer"
>> Server: Cisco-SIPGateway/IOS-15.5.3.S4b
>> Reason: Q.850;cause=1
>> Content-Length: 0
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7Cf8a7858daf594c9c0c1f08d7504a0d4c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066151290735716&amp;sdata=MEMPChCZTf9Fkl4a7n%2BVjLO%2Fkd2gkOVy20TqdO0ZBss%3D&amp;reserved=0 <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7Cf8a7858daf594c9c0c1f08d7504a0d4c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066151290735716&amp;sdata=MEMPChCZTf9Fkl4a7n%2BVjLO%2Fkd2gkOVy20TqdO0ZBss%3D&amp;reserved=0>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip <https://puck.nether.net/mailman/listinfo/cisco-voip>

Could be that the UCCX trigger’s partition isn’t in the SIP trunk’s inbound CSS. I assume the trigger’s css can reach the partition of the CTI ports as that doesn’t seem like something that would have been changed in a scenario like this.

Sent from my iPhone

On Oct 13, 2019, at 22:20, Kent Roberts <kent@fredf.org> wrote:

? Ryan, that’s what I was thinking, but when Dana said to a station works fine, I started thinking a bit like some of the fun and weird messages that show up with codecs, etc. (basically codec mismatch and a bounce off to another number/pattern and that failed it…. Might need a few logs to see what its doing with uccx in the mix.



On Oct 13, 2019, at 8:15 PM, Ryan Huff <ryanhuff@outlook.com<mailto:ryanhuff@outlook.com>> wrote:

Sort of sounds like you may have a Class of Service (CSS/Partition) issue with the SIP trunk between CUBE and CUCM, since that is most likely the most significant configuration change/add since moving to SIP, that could generate 404 responses.

Could also be an issue with the device pool on the SIP trunk, depending on how you have the dialplan structured.

CUCM Generally won’t issue a station not found (404) message, unless CUCM ingress element (the SIP trunk) doesn’t find the station; either because the station doesn’t truly exist, or doesn’t exist in the configuration context it has access to.

Regional problems would issue a 404 generally.

Sent from my iPhone

On Oct 13, 2019, at 21:58, Dana Tong <dana.tong@yellit.com.au<mailto:dana.tong@yellit.com.au>> wrote:

?
Hi all,

Customer recently changed from ISDN gateways (H323 registered) to centralised SIP and now the UCCX IVR isn’t working.

The SIP trunk is set to use the 64K region and I did also try setting the CODEC to both G.711alaw and ulaw on the dial-peers on the SIP CUBE router.
It’s weird.

The debug CCSIP messages are showing 404 not found, and the voip dialpeer inout were showing a match on the correct dial-peers.
But then the logs say no match as per below.

Anyone seen this kind of error after changing from ISDN to SIP?

Somewhat sanitised below. Trying to get RTMT access.



Sent:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 203.52.3.164:5060;branch=z9hG4bKritgbh304ou76jse28v0.1
From: <sip:000000@10.119.243.144;user=phone>;tag=39906919-1571014929892-
To: "777 777"<sip:754420777@customer.com.au;user=phone>;tag=EDD3AA89-2562
Date: Mon, 14 Oct 2019 11:02:09 GMT
Call-ID: BW120209892141019-860012483@10.10.10.10<mailto:BW120209892141019-860012483@10.10.10.10>
CSeq: 602191603 INVITE
Allow-Events: telephone-event
Warning: 399 10.10.253.10 "No matching outgoing dial-peer"
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Reason: Q.850;cause=1
Content-Length: 0
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7Cf8a7858daf594c9c0c1f08d7504a0d4c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066151290735716&amp;sdata=MEMPChCZTf9Fkl4a7n%2BVjLO%2Fkd2gkOVy20TqdO0ZBss%3D&amp;reserved=0<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C8d90619e914141ab1a1c08d7504d136d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066164269172139&sdata=bUSBUwbrcL%2FrI2x7ANOxjumFpUxFKoTvfqcwQUrM24c%3D&reserved=0>
_______________________________________________
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%7C8d90619e914141ab1a1c08d7504d136d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066164269172139&sdata=bUSBUwbrcL%2FrI2x7ANOxjumFpUxFKoTvfqcwQUrM24c%3D&reserved=0>

Sorry my bad. It’s okay now.

The translation rule was pushing it into another partition. The Trunk CSS didn’t have access to it.

Had a brain fart moment. Sorry all.

From: Ryan Huff <ryanhuff@outlook.com>
Sent: Monday, 14 October 2019 12:25 PM
To: Kent Roberts <kent@fredf.org>
Cc: Dana Tong <dana.tong@yellit.com.au>; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] UCCX not working after change to SIP

Could be that the UCCX trigger’s partition isn’t in the SIP trunk’s inbound CSS. I assume the trigger’s css can reach the partition of the CTI ports as that doesn’t seem like something that would have been changed in a scenario like this.
Sent from my iPhone


On Oct 13, 2019, at 22:20, Kent Roberts <kent@fredf.org<mailto:kent@fredf.org>> wrote:
? Ryan, that’s what I was thinking, but when Dana said to a station works fine, I started thinking a bit like some of the fun and weird messages that show up with codecs, etc. (basically codec mismatch and a bounce off to another number/pattern and that failed it…. Might need a few logs to see what its doing with uccx in the mix.




On Oct 13, 2019, at 8:15 PM, Ryan Huff <ryanhuff@outlook.com<mailto:ryanhuff@outlook.com>> wrote:

Sort of sounds like you may have a Class of Service (CSS/Partition) issue with the SIP trunk between CUBE and CUCM, since that is most likely the most significant configuration change/add since moving to SIP, that could generate 404 responses.

Could also be an issue with the device pool on the SIP trunk, depending on how you have the dialplan structured.

CUCM Generally won’t issue a station not found (404) message, unless CUCM ingress element (the SIP trunk) doesn’t find the station; either because the station doesn’t truly exist, or doesn’t exist in the configuration context it has access to.

Regional problems would issue a 404 generally.

Sent from my iPhone


On Oct 13, 2019, at 21:58, Dana Tong <dana.tong@yellit.com.au<mailto:dana.tong@yellit.com.au>> wrote:
?
Hi all,

Customer recently changed from ISDN gateways (H323 registered) to centralised SIP and now the UCCX IVR isn’t working.

The SIP trunk is set to use the 64K region and I did also try setting the CODEC to both G.711alaw and ulaw on the dial-peers on the SIP CUBE router.
It’s weird.

The debug CCSIP messages are showing 404 not found, and the voip dialpeer inout were showing a match on the correct dial-peers.
But then the logs say no match as per below.

Anyone seen this kind of error after changing from ISDN to SIP?

Somewhat sanitised below. Trying to get RTMT access.



Sent:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 203.52.3.164:5060;branch=z9hG4bKritgbh304ou76jse28v0.1
From: <sip:000000@10.119.243.144;user=phone>;tag=39906919-1571014929892-
To: "777 777"<sip:754420777@customer.com.au;user=phone>;tag=EDD3AA89-2562
Date: Mon, 14 Oct 2019 11:02:09 GMT
Call-ID: BW120209892141019-860012483@10.10.10.10<mailto:BW120209892141019-860012483@10.10.10.10>
CSeq: 602191603 INVITE
Allow-Events: telephone-event
Warning: 399 10.10.253.10 "No matching outgoing dial-peer"
Server: Cisco-SIPGateway/IOS-15.5.3.S4b
Reason: Q.850;cause=1
Content-Length: 0
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&amp;data=02%7C01%7C%7Cf8a7858daf594c9c0c1f08d7504a0d4c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066151290735716&amp;sdata=MEMPChCZTf9Fkl4a7n%2BVjLO%2Fkd2gkOVy20TqdO0ZBss%3D&amp;reserved=0<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C8d90619e914141ab1a1c08d7504d136d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066164269172139&sdata=bUSBUwbrcL%2FrI2x7ANOxjumFpUxFKoTvfqcwQUrM24c%3D&reserved=0>
_______________________________________________
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%7C8d90619e914141ab1a1c08d7504d136d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637066164269172139&sdata=bUSBUwbrcL%2FrI2x7ANOxjumFpUxFKoTvfqcwQUrM24c%3D&reserved=0>