Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: <[email protected]>
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <50956>
Message-ID: <[email protected]>



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: [email protected][/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: [email protected][/email]
> <[email protected][/email]>
> To: [email protected][/email]
> <[email protected][/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:[email protected][/email][/email][/email]Phone:
> 616-532-4985
> _______________________________________________
> sipx-users mailing list
> [email protected][/email]
> List Archive:
> http://list.sipfoundry.org/archive/sipx-users/


-- 
Mike Burden
Lynk Systems, Inc       
e-mail: mailto:[email protected][/email][/email]    
Phone: 616-532-4985

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to