Just to elaborate on what Dale says, the SIP responses aren't there for
the purpose of mapping to QSIG - they mean what they mean. If the
response has some significance on the ISDN side then it seems like it
ought to be mapped. (If the gateway was replaced with a more
conventional UAC, would you want *it* to ignore the meaning of the
response as well?)
For instance, if the response is 180 Ringing, are you asking that the
gateway not indicate the alerting status via QSIG?
Paul
[EMAIL PROTECTED] wrote:
> From: "Jayesh Sangpal" <[EMAIL PROTECTED]>
>
> Hi Experts,In my scenario, Caller is ISDN-SIP gateway,Callee
> receieves INVITE request and responds with 18X response. Callee TU
> want to specify that 18X should not be mapped to equivalent QSIG
> message at Caller TU.Is there any mechanism in SIP (extention/
> Header/ Header-param) by which UAS can tell UAC to treat the 18X
> specially ? (not to map the 18X to ISDN in my case). Thus
> Callee would check this mechanism and then make decisionThe
> mechanism could be application specific. (as TU is involvedin
> sending 18X)Thanks in Advance ,Jayesh
>
> Perhaps have the callee use a custom 1xx response. Any 1xx other than
> 100 is functionally equivalent to a standard SIP UAC, it carries a
> to-tag and establishes an early dialog. But if it's not one that has
> a defined QSIG mapping, it shouldn't cause the UAC to generate an ISDN
> status.
>
> Dale
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
