20 Mar
2007
20 Mar
'07
9:35 p.m.
If you pay attention to the SIP packets, you'll see that the SIP To: header
doesn't change even through the URI might. What we do is keep track of anyone who has
call forwarding turned on, and if that's the case, we forward the calls to a DIFFERENT
AGI on the Asterisk box. That AGI takes into account the incoming SIP To: header and
ensures that billing is charged to the SIP To: user.
For instance, if you call 6363(a)yourserver.com and 6363 overwrites the RURI to
004428364825, then looking at the SIP To: header, you'll still see that the call went
to 6363. You can then bill to the appropriate user.
Is it a foolproof scenario? Probably not, but it hasn't broken yet, and we don't
have to put the onus on the UA.
N.
On Tue, 20 Mar 2007 10:15:34 -0800, Ali Zaidi wrote
Hi,
Interesting, i was facing similar problem, i had quick fix for that. If it possible leave
call forwarding part to UA if you using any hardware/software user agent and don't use
SER for call forwarding.
If you find other solution through ser, let me know.
Ali...
On 3/20/07, Jai Rangi <jprangi(a)gmail.com> wrote:Hello,
I have a ser and asterisk setup. Users register on ser and all the national and
international calls go through asterisk. Asterisk handles the billing part for long
distance calls. Now I got an issue with call forwarding. Here is the situation.
Useragent A calls Usergent B. User B has setup the call the call forwarding to his cell
phone. So when user A calls user B, ser check that user B has set the forwarding and send
the call to Asterisk box. Asterisk box sees user A in the callerID and bills user A for
that call. We want user B to be billed for that call, cause he is forwarding the calls to
his cell phone (long distance number).
How can I achieve this.
Thank you,
-Jai
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers