Nevermind, I found it! Thanks!
13.2.1 Creating the Initial INVITE Since the initial INVITE represents a request outside of a dialog, its construction follows the procedures of Section 8.1.1. 8.1.1.1 Request-URI The initial Request-URI of the message SHOULD be set to the value of the URI in the To field. Mike Burden Lynk Systems, Inc e-mail: m...@lynk.com Phone: 616-532-4985 -----Original Message----- From: Burden, Mike Sent: Tuesday, August 24, 2010 8:31 AM To: 'Tony Graziano'; sipx-users@list.sipfoundry.org Subject: RE: [sipx-users] sipXecs registrar gives 404 for new DID number? Tony, I'm parsing my way through RFC3261, but so far I haven't found anything to indicate that the standard specifies that the DID Number should be in the INVITE header. Can you point me at something that I can forward to the ITSP to help make my case? Mike Burden Lynk Systems, Inc e-mail: m...@lynk.com Phone: 616-532-4985 -----Original Message----- From: Tony Graziano [mailto:tgrazi...@myitdepartment.net] Sent: Monday, August 23, 2010 2:58 PM To: Burden, Mike; sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] sipXecs registrar gives 404 for new DID number? I can't read the trace on my blackberry. I suspected as much. There is an "unstable" 4.3 version that might allow using the "to" header. Its "typical" with a lot of providers to not be flexible enough to send the DID in the INVITE. As Carriers go, it "behooves" them to be able to adhere to standards. In certain markets though, its hard to accept that as a rule. A lot of carriers in parts of europe "think" differently. Residentially focused carriers think they don't have to send the DID in the INVITE and have a hard time making allowances for customers. Its helpful that sipxbridge is trying to be more flexible, but you might have to flip a coin with some carriers depending on their location, capabilities and focus. Hope they can work it out for you. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: sipx-users-boun...@list.sipfoundry.org <sipx-users-boun...@list.sipfoundry.org> To: sipx-users@list.sipfoundry.org <sipx-users@list.sipfoundry.org> Sent: Mon Aug 23 14:43:31 2010 Subject: Re: [sipx-users] sipXecs registrar gives 404 for new DID number? Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <3c943b856968015e7218c392056c2...@mail.gmail.com> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <50964> Message-ID: <c714.4c72c...@forum.sipfoundry.org> No need to ask them, it was in the sipxtrace I posted. That is exactly it. They are sending our userid in the INVITE header, and the DID in the "To". I'm working with them now to get it sorted. Tony Graziano wrote on Mon, 23 August 2010 13:35 > Your itsp might be sending the did in the to header > instead. > > Ask them what they send in the invite and what they send > in the "to". > ============================ > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: tgrazi...@myitdepartment.net[/email] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > ----- Original Message ----- > From: sipx-users-boun...@list.sipfoundry.org[/email] > <sipx-users-boun...@list.sipfoundry.org[/email]> > To: sipx-us...@list.sipfoundry.org[/email] > <sipx-us...@list.sipfoundry.org[/email]> > Sent: Mon Aug 23 13:29:29 2010 > Subject: Re: [sipx-users] sipXecs registrar gives 404 > for new DID number? > > > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > In-Reply-To: > <441bfbae39ea697532231391887cb...@mail.gmail.com[/email]> > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <50956> > Message-ID: > <c70c.4c72a...@forum.sipfoundry.org[/email]> > > > > 1. 4.0.4-017289 (Yes, I know we're overdue for an > upgrade. > The upgrade will be happening mid-September.) > > 2. Yes, both sides show that the registration was > successful, and outbound calls through the 2nd ITSP > succeed > normally. > > 3. MidwestSIP (a local SIP provider) > > > As far as I can tell, the INVITE from MidwestSIP looks > fine, > but for some reason the sipXregister is rejecting it as > 404. > > > > > > > Tony Graziano wrote on Mon, 23 August 2010 13:22 > > 1. What version sipx? > > 2. Does sipx and the registrars agree that sipx has > > registered with them? > > 3. Who is the ITSP ( 2nd one)? > > ============================ > > Tony Graziano, Manager > > Telephone: 434.984.8430 > > Fax: 434.984.8431 > > > > Email: tgrazi...@myitdepartment.net[/email][/email] > > > > LAN/Telephony/Security and Control Systems > > Helpdesk: > > Telephone: 434.984.8426 > > Fax: 434.984.8427 > > > > Helpdesk Contract Customers: > > http://www.myitdepartment.net/gethelp/ > > > > ----- Original Message ----- > > From: > > sipx-users-boun...@list.sipfoundry.org[/email][/email] > > > > <sipx-users-boun...@list.sipfoundry.org[/email][/email]> > > To: sipx-us...@list.sipfoundry.org[/email][/email] > > <sipx-us...@list.sipfoundry.org[/email][/email]> > > Sent: Mon Aug 23 13:09:33 2010 > > Subject: [sipx-users] sipXecs registrar gives 404 > > for > > new DID number? > > > > Good afternoon, > > > > We have two ITSPs, set up as Gateways in our > > sipXecs > > server. > > The two Gateways are configured identically, except > > for > > the > > IP Address, username, and password. > > > > We have six DID Numbers. I have users (DID01, > > DID02, > > DID03, > > ..., DID06) configured for each DID Number, with > > the > > actual > > phone numbers configured as aliases (three times: > > 1xxxyyyzzz xxxyyyzzz yyyzzz). The forwarding rules > > for > > the > > user are configured to forward calls to our > > "everyone" > > hunt > > group (we all answer phones here.) > > > > This morning I created a new user, DID08, specified > > the > > DID > > number from the 2nd ITSP as the alias (three times, > > as > > above) and configured forwarding to forward calls > > to > > our > > "everyone" hunt group. > > > > > > As far as I can tell, the Gateways are configured > > identically (except for the identification info) > > and > > the > > users are configured identically. > > > > > > When I call any of the DID numbers from the 1st > > ITSP, > > everything works as expected. > > > > When I call the DID number from the 2nd ITSP, the > > sipXecs > > registrar returns a 404 to the sipXproxy, which > > returns > > a > > 404 to the sipXbridge, which returns it to the > > ITSP, > > causing > > the call to fail. > > > > > > Anyone have any idea where I went wrong? I've > > attached > > the > > sipXtrace of the failed inbound call. > > > > -- > > Mike Burden > > Lynk Systems, Ince-mail: > > > > mailto:m...@lynk.com[/email][/email][/email][/email]Phone: > > 616-532-4985 > > _______________________________________________ > > sipx-users mailing list > > sipx-us...@list.sipfoundry.org[/email][/email] > > List Archive: > > http://list.sipfoundry.org/archive/sipx-users/ > > > -- > Mike Burden > Lynk Systems, Ince-mail: > mailto:m...@lynk.com[/email][/email][/email]Phone: > 616-532-4985 > > _______________________________________________ > sipx-users mailing list > sipx-us...@list.sipfoundry.org[/email] > List Archive: > http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ > sipx-users mailing list > sipx-us...@list.sipfoundry.org[/email] > List Archive: > http://list.sipfoundry.org/archive/sipx-users/ -- Mike Burden Lynk Systems, Ince-mail: mailto:m...@lynk.com[/email][/email]Phone: 616-532-4985 _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
