On 05/15/2010 12:32 PM, Alex Balashov wrote:
Albert,

On 05/15/2010 01:11 AM, Albert Paijmans wrote:

I have been playing around with SEMS. I like the early_announce
application with database support. Play an announcement to the caller.
But the *wav file is the dialed number and not the caller id.
It sends an 183 and then 404 not found wich works with a proxy.

Is it possible to have the early_announce application play the wav file
corresponding to caller id? So if extensions 2345 would dial a number it
hears 2345.wav and when extension 6789 would dial a number it would hear
6789.wav and then the call would continu.

Unfortunately, it does not appear that early_announce has any SIP header
parameters that allow you to forcibly specify the file to be played back
in spite of RURI. However, the module could, in principle, be hacked
rather easily to do this.

I suppose if you don't want to do this, the other option is to put another proxy on the other side of the B2BUA and then encode the original RURI in a custom header which is passed through SEMS. You can then put the user part of the From URI ($fU) in the RURI temporarily to encode the CID as the request passes through the B2BUA, and, on the other side, swap it with the value of the custom header in which you encoded the original again. For example:

On proxy A:

    append_hf("X-Orig-Ruri: $ru\r\n");

    $rU = "6789";

And on proxy B:

    if(is_present_hf("X-Orig-Ruri")) {
       $ru = $hdr(X-Orig-Ruri);
       remove_hf("X-Orig-Ruri");
    }

--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to