[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    [Sip-implementors] more 404-Not Found calls
From:       Mahudeswaran A <mahudeswaran.a () acqueon ! com>
Date:       2014-04-27 7:56:51
Message-ID: 1f1b61e75ac54623b3f0f9e0afc26903 () HKNPR06MB305 ! apcprd06 ! prod ! outlook ! com
[Download RAW message or body]

Hello All,

Would like to clarify under what circumstances UAC gets "404-NOT \
Found---Reason=unallocated number"  for an INVITE request; Sip trunk established \
between UAC & Cisco call manager;

Call path:
UAC -----> cisco cm ----> voice gateway ------> (ITSP)

We captured wireshark traces for 404-Not Found messages and some phone numbers are \
actually invalid numbers and some phone numbers are valid; The INVITE request having \
timeout set as 'SIP header ==Expires: 180'. This is as suggested & being asked us to \
put in here for the calls to work; We did faced more calls getting 404-NotFound \
response.

So trying to find what are all the possible scenarios the cisco cm could send the \
404-NotFound error response; Some reason like

1.       The dialling number itself is invalid and service provider plays the message \
saying "like...number is invalid.."

2.       Due to not enough bandwidth between voice gateway & ITSP

3.       Due to not enough bandwidth between cisco cm & voice gateway --- (This is \
least option if all the ports in gateway are busy.... The cm should send busy instead \
of 404-NotFound..)

4.       Comments from other team says the UAC is sending something wrong here \
because of which more 404-NotFound; --- randomly we picked some 404-NotFound numbers \
and tested by manual dialling and found those were valid numbers.

Any other reasons for 404-NotFound?? -- How to troubleshoot these issues;

Regards
Mahu

_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors


[prev in list] [next in list] [prev in thread] [next in thread]