On Fri, 2010-04-30 at 22:40 -0500, D. R. Lang wrote: > Just a guess > > If the inbound "invite" field or to "to" field call from matches the your > ITSP account you can create a hunt group with that name and give it a numeric > alias. Mine worked by naming with the "XXX" part of the "x...@provider.com" > Test the hunt group by calling it internal alias number. > > Duane
I had a hunch it might work this way. Need to figure out why inbound calls aren't routed to extensions first... Any other takers on the 302 and 407 'errors'? Regards, Djerk > -----Original Message----- > From: Djerk Geurts [mailto:d.m.geu...@geurtscass.com] > Sent: Friday, April 30, 2010 9:23 PM > To: sipx-users@list.sipfoundry.org > Subject: [sipx-users] Call routing for DID from ITSP > > Hi, > > I'm new to sipxecs, upgrading from an old asterisk machine to a virtualbox > vm. So far so good, managed to get the guest additions and virtio-net going > fine. Also internal calling works. > > I have 3 ITSP accounts with 2 ITSP's for 3 DID numbers. I have 3 other ITSP's > for out bound calls. Neither in or out bound calls currently work. I have > attached a siptrace xml file. I'm hoping for some hints and explanation as to > why there's a 302 and a 407 error code in the trace. > > currently I have extension 201 set up with aliases for the full ENUM and the > userid for that ITSP/DID. It seems to want to route to the correct extension > but the call is never established. > > Eventually I'd like to route the call to a hunt group. Any hints on the > possibilities for this are also most welcome. > > Regards, > Djerk > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
