Brett, I have a story you may find entertaining. I did exactly as you say -- rewrite the RURI user and leave the To header as it came in. In my case that meant an 11-digit To and RURI from the customer, since their PBX saw this as a long distance call.
The call made it all the way through my network, to a carrier partner on SIP, who sent it to a carrier partner on SS7, who sent it to the end office in Naples, FL. My customer was calling a steak house down there. The steak house had a two line POTS hunt group from the LEC, with voicemail. The problem we chased for a month was when my customer called, they heard "unknown voicemail box" or something like that from the LEC's VM system. When I called, I got the steak house's VM every time. It turned out the 11-digit To header from my customer made it into some field in the ISUP IAM that the LEC's voicemail system used to identify which voicemail box should answer the call. The voicemail box was created with 10-digits, not 11. It was because of this incident I started normalizing the To header as well with uac_replace_to(). So be aware, if you or your customers use Opensips to handle calls to steak houses in Naples, FL... you may want to consider rewriting the To header as well. :) - Jeff On Sep 1, 2011, at 9:52 AM, Brett Nemeroff wrote: On Thu, Sep 1, 2011 at 4:51 AM, Mike O'Connor <[email protected]<mailto:[email protected]>> wrote: So I need another method of rewriting the phone number, the $tU does not allow R/W so I need another function which will allow me to edit the $tU field. Careful here.. Normally rewriting the TO or FROM headers is undesirable. This is only necessary when connecting to broken equipment. Normally you should only re-write the RURI and leave the TO as is. -Brett <ATT00001..txt>
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
