RE: SIP-T and Q.Sig

["Dan Wing" <dwing@cisco.com>]

...
> > RFC3398 may not be "complete" as it seems to only specify ISDN cause 
> > codes, and I am blissfully un-aware of what more hideous and complex 
> > messages may reside inside of SS7.  I'd be interested in hearing any 
> > other comments on this topic, since the mismatch between ISUP and SIP 
> > sometimes causes minor un-smoothness (but I have not yet had it be a 
> > "problem" - merely an inconvenience.)
> 
> Here is an example.  
> 
> If we receive a Term Code 1, we terminate the call.
> If we receive a Term Code 3, we advance to the next route
> Both Term Code 1 and Term Code 3 map to SIP 404.
> SIP 404 maps to Term Code 1.

So, what of using GTD to preserve the ISUP messages for other
GTD-aware devices?  I understand GTD was recently standardized
in ITU (am on a plane right now so can't check).

-d



--
To unsubscribe send a message to voip-peering-request@psg.com with
the word 'unsubscribe' in a single line as the message text body.
An archive is at <http://psg.com/lists/voip-peering/>.