sip servlet - Mobicents SIP error response handling - what's the proper way to re-proxy? -


the mobicents sip servlet container appears handle error responses differently other sip containers i've used. situation that:

  • on receipt of invite, app handles , proxies (supervised) downstream (so may receive responses invite).

  • on receipt of error response initial target, app proxies new destination (in non-supervised way).

this should prevent initial error response propagating upstream (since transaction has new target). however, mobicents container, though invite indeed proxied out new destination, received error response still propagates upstream. believe bug in mobicents implementation - how 1 work around this?

code:

public void doinvite(sipservletrequest req) {   req.getproxy().proxyto(req.getrequesturi()); }  public void doerror(sipservletresponse res) {     proxy p = res.getproxy();     p.setsupervised(false);     p.proxyto(...);     // request proxied, error response still passes     // upstream - retargeting of transaction (through     // proxying new destination ought prevent that). } 

which other sip containers migrating application ? doing sequential or parallel proxying ? error response receive ? version of mobicents sip servlets container using ? have full log available on gist.github.com or pastebin.com ?


Comments

Popular posts from this blog

Java 3D LWJGL collision -

spring - SubProtocolWebSocketHandler - No handlers -

methods - python can't use function in submodule -