Thank you very much for the response. I would think I could have a different route table for each IF_FXO interface that uses a different mapping table, the devil (for me) is that the example config doesn't have any route table at all for IF_FXO calls, the FXO interface just points right at the SIP interface -- so I'm not sure how to attach the route.
Now that I know I'm on the right track at least I'll study the docs some more (and probably ping Patton) and let you and the list know what I come up with. -Eric Varsanyi On Jan 25, 2010, at 1:03 PM, Jim Canfield wrote: > On Mon, Jan 25, 2010 at 10:20 AM, Eric Varsanyi <[email protected]> wrote: >> To try to be a bit clearer: in receiving calls from the PSTN on (in this >> case) interface IF-FXO0 (which is bound to one fxo port) sometimes I get >> caller ID and sometimes I don't. When I don't something is creating a 'from' >> header of [email protected]:5060 . Some of these FXO's will go to >> doorphones and I'd like the callerID that shows up on the phones to be >> something like 'Lobby' or 'Dock' rather than 'anonymous'. I also have some >> POTS lines that do not receive caller ID and I'd like to identify which line >> if a call comes in on it ("AlarmCo" say). > > So, yes...you will need to do address translation on the from-header. > I'm not sure how you will make this dynamic though. In my mind it > seems static - all or nothing. You could "I assume" create a > address-translation line for the from-header under IF_SIPX, however I > think it's going to show up like that for every call. Might be worth > sending an email to Patton ([email protected]) and see if they know > any magic that can accomplish this. I'd be curious to know what they > come up with. > > Sorry, I know that wasn't much help. > > -Jim _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
