[SIPForum-discussion] Reasons for SIP response 501 not implemented

[Nitin Kapoor]

Hi Amit,

As far as i know this thing can also come in the case of ISUP,
especially inMid-Call transactions which do not change SIP state.

When interworking with the PSTN, there are situations when gateways will
need to send messages to each other over SIP that do not correspond to any
SIP operations. In support of mid-call transactions and other ISUP events
that do not correspond to existing SIP methods, SIP gateways MUST support
the INFO method.

So here gateways MUST accept "405 Method Not Allowed" and "501 Not
Implemented" as non-fatal responses to INFO requests - that is, any call in
progress MUST NOT be torn down if a destination so rejects an INFO request
sent by a gateway.

Thanks,
Nitin Kapoor

On 10 September 2010 16:58, amit salunkhe <amitsalunkhe21 at gmail.com> wrote:

> Dear All
>
> Please help me with the diffrent reasons due to which call fail with SIP
> response 501 not implemented.As oper the RFC 3261 *SIP 501 we can expect
> when a UAS does not recognize the request method and is not capable of
> supporting it for any user.*
>
> Alos is there any chance Caller id or from header value can create problem,
> for example if my caller id is amit223 or amit22* or 1224asdf* whther such
> Caller id ceate the problem & call may failed fromfar end with SIP 501 not
> implemnted?
>
> Please help em with this.
>
> Regards
> Amit Salunkhe
>
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20100911/754e3f75/attachment-0002.html>