drachtio / drachtio-fn-b2b-sugar Goto Github PK

Hi @davehorton ,

We use simringer.

When one of the forks answers, I'd like to be able to add a "Reason" header to all the cancels sent on the other legs, viz 'Reason: SIP;cause=200;text="Call completed elsewhere"'.

This is so the client devices can adjust how they show the "missed" invite. Kamailio includes such a header, at least in our configuration.

My skim through the code here shows calls to req.cancel() and I don't see any place for something to set the headers for the cancel sent.

In related news if I receive a CANCEL from the upstream (caller) side, then I want to proxy the Reason: header from the incoming cancel to my outgoing cancels. Not sure if there's a way to do that - I added 'reason' to my proxyRequestHeaders which I will try now but its just a guess as to what to do.

Thanks,
Steve

Hi,

If I call addUri on a Simringer, is there a way to get back the result of that particular branch/call?

IE in our code we have req._simringer.addUri(remoteUri, additionalCallOpts);

(we've stashed the simringer on the original req).

In the case I'm looking at, I see:

[2020-04-25 15:25:00.166 +0000] DEBUG (83163 on maximus.daviesfam.org): CallManager#_attemptOne: launched call to sip:[email protected]; 2 calls in progress
[2020-04-25 15:25:00.170 +0000] INFO  (83163 on maximus.daviesfam.org): CallManager#attemptOne: call to sip:[email protected] failed with 503

Another branch goes on to connect so the whole simringer succeeds.
But this particular branch gets a 503 - can I get my hands on that result?

Thanks,
Steve

I was hoping to be able to use this, but there doesn't seem to be a way for me to construct different RTP offers for each leg (when you have a variety of different endpoint types, like web, mobile, desk). Just making sure I'm not missing something!