It would be cool if someone put an Ethereal trace somewhere on the web
to see how this stuff works in "real life".

CS 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Gaurav Kheterpal
> Sent: Sunday, January 08, 2006 11:31 PM
> To: Keys, Peter; [email protected]
> Subject: Re: [Sip-implementors] T.38 SIP call trace
> 
> Hello Peter,
> 
> You can refer to draft-mule-sip-t38callflows-02.txt for 
> detailed examples of SIP/ SDP call flows for T.38 Fax Relay. 
> Though the draft is *expired*, it is quiet a handy reference 
> for understanding T.38 and has numerous flows for various 
> T.38 call scenarios.
> 
> The draft is available at
> http://quimby.gnus.org/internet-drafts/tmp/draft-mule-sip-t38c
> allflows-0
> 2.txt
> 
> My 2 cents,
> Gaurav
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Keys, Peter
> Sent: Saturday, January 07, 2006 3:12 AM
> To: [email protected]
> Subject: [Sip-implementors] T.38 SIP call trace
> 
> Dear List,
> 
>  
> 
>             Could someone please provide me with an actual 
> SIP/SDP trace for a T.38 call, as per T.38 annex D. The 
> scenario I am looking for is for a call standard voice call 
> that is setup using any voice codec. Once the called party 
> fax machine answers, and the fax tone is received, I am 
> especially interested, in an actual trace of the re-INVITE 
> from the receiving gateway.
> 
>  
> 
> Thanks
> 
>  
> 
> Peter Keys
> 
>  
> 
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> 
> 
> 
> 
> ********************** Legal Disclaimer 
> **************************** "This email may contain 
> confidential and privileged material for the sole use of the 
> intended recipient.  Any unauthorized review, use or 
> distribution by others is strictly prohibited.  If you have 
> received the message in error, please advise the sender by 
> reply email and delete the message. Thank you."
> **********************************************************************
> 
> 
> _______________________________________________
> 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

Reply via email to