sip server - Why do we need SIP "100 Trying" response over TCP? -
sip server - Why do we need SIP "100 Trying" response over TCP? -
sip on udp: it's necessary have sip response "100 trying" sip on udp shut timer-a off have been started caller , hence stopping re-transmission of sip message. of import because other responses (provisional , final) might take while initial invite message have consider scenario of forking, ue-b not reachable, fallback... etc might take time.
sip on tcp: timer-a not started caller , no re-transmission of message. tcp beingness reliable, not re-transmission required. then, why implementation sends 100 trying on tcp ???
there few reasons 100 trying still needed sip on tcp.
having tcp connection not guarantee sip application working or if sip - aware application @ all. 100 trying provides feedback request beingness processed sip application.
the lack of 100 trying can right trigger not re-transmissions re-attempt maybe different server in configuration. may not want elapse 32 seconds every server in configuration when connection tcp.
in deployment scenarios, if there elements sbc or load balancer, tcp connection established them. application behind can different entity , these border elements pass on messaging or generate messaging indicate phone call in action state.
sip sip-server opensips
Comments
Post a Comment