I hope this is apropos for this listserv. Is there a good source somewhere
which describes (with examples) the messaging inherent in making a trunk?
What does it mean "to be a trunk"?
Thanks,
Paul
___
Sip-implementors mailing list
Sip-implementors@l
On 7/22/15 3:12 PM, Brett Tate wrote:
Hi,
Concerning the 408, I assume that a transaction stateful middle box
generated it upon re-INVITE transaction timeout (or similar issue) hitting
the "best response" behavior of RFC 3261 section 16.7.
Oh, duh. When I wrote my response I was thinking of 48
Hi,
Concerning the 408, I assume that a transaction stateful middle box
generated it upon re-INVITE transaction timeout (or similar issue) hitting
the "best response" behavior of RFC 3261 section 16.7.
> -Original Message-
> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:si
I generally agree with what Tarun is saying, but have one clarification
On 7/22/15 1:39 PM, Tarun2 Gupta wrote:
Hi
Please refer Section 7.2 of RFC 4028.
If the UAS did not include a SE header in 200 OK response, it means that it
does not want / support session expiration. In this case, UAC ca
Hi
Please refer Section 7.2 of RFC 4028.
If the UAS did not include a SE header in 200 OK response, it means that it
does not want / support session expiration. In this case, UAC can perform
refreshes but for its own benefit only. UAC should behave as if the 200 OK
response contained refresher
Dear All,
I need your help to understand a logic behind the session expires.
My doubt is.
--> Invite have "session-expire" header in Invite (from UAC to UAS)
--> UAS did not included "session-expire" header in 200 OK to the
correspondence of initial invite.
1) So in this case what we should as
