[Spce-user] Incoming calls from sip trunk

[Christopher Saroli]

Adding the 1 in the rewrite rule ended up working.  Thanks for your help Jon.  

Match:    ^([A-Za-z0-9]+)$
Replace:  1\1


I still would like to know if it is possible to send calls to an IP instead of a registered endpoint, let me know if this is possible. 
---------------------------------
Christopher Saroli
csaroli at isysp.com

                                 586-226-7800 (Main Office)
                                 586-884-0800 (Direct)


-----Original Message-----
From: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Christopher Saroli
Sent: Thursday, July 05, 2012 4:01 PM
To: Jon Bonilla
Cc: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Incoming calls from sip trunk

I am actually getting a different error than before, it is a "404 not found" error.  I have attached the log

We receive *no* country code from the SIP trunk provider- It's just a 10 digit American dialed-number as a destination.   It does not seem to match the subscriber's E.164 properly because if I make the SIP URI the telephone number, it does match and the call is completed.
Do we need a regex re-write rule to add "1" or "+1" to the number being received in order for it to match properly?  If so, where would we specifiy the re-write rule?

Thank you
---------------------------------
Christopher Saroli
csaroli at isysp.com


-----Original Message-----
From: Jon Bonilla [mailto:jbonilla at sipwise.com] 
Sent: Thursday, July 05, 2012 2:55 PM
To: spce-user@
Cc: Christopher Saroli
Subject: Re: [Spce-user] Incoming calls from sip trunk

El Thu, 5 Jul 2012 17:33:20 +0000
Christopher Saroli <csaroli at isysp.com> escribió:

> I have attached the capture, Thanks again
> 

Hi Christopher.

Next time please use "ngrep-sip b" to avoid OPTIONS traffic. What I can see in your trace is an INVITE request being rejected with 407 for auth challenge and your device does not send another INVITE with the auth credentials.

Please check your device. Make sure you have configured the user and password and the device is capable of authenticating. This is not a server problem.


cheers,

Jon