[Spce-user] New: cant figure out some things
skchopperguy at gmail.com
Wed Sep 7 07:26:57 EDT 2011
On Wed, 2011-09-07 at 12:56 +0200, Andreas Granig wrote:
> In my opinion, it's a huge red flag when a SIP provider tells you that
> the To header is not according to his needs.
> Also, P-Asserted-Identity
> is a standardized header (RFC3325), whereas Remote-Party-ID never made
> it beyond a draft.
> If you can, change your SIP provider.
If you need recommendations for solid providers in Canada I don't mind
telling you off list whom I do business with. Drop me a note privately.
> If not, there are ways to
> accomplish what you want, but no out-of-the-box ones.
And...SPCE is a solid solution already, don't waste your time trying to
fix a problem that doesn't exist only to serve a provider's needs. Its
your needs that are important...you are the customer after all ;)
> /etc/ngcp-config/templates/etc/sems/etc/ngcp.sbcprofile.conf.tt2 there
> is, quite on top, something like this:
> This means that the To header is passed through transparently from the
> proxy (and thus the calling party) to the called party. You can change
> it to something like
> And then in proxy.cfg.tt2, do:
> append_hf("My-New-To: <sip:$rU at your.desired.domain>\r\n");
> This should do the trick, at least for the To.
> On 09/07/2011 10:58 AM, Skyler wrote:
> > Hello Dave,
> > On Tue, 2011-09-06 at 18:21 -0400, Dave Massey wrote:
> >> Im getting into sipwise CE for possible use as a VOIP provider addon to my ISP.
> >> I was able to get it to receive calls OK. but when I try to make calls, my provider says that my SIP TO is wrong, he says Im sending a SIP:905772000 at 0.0.0.0 (where 0.0.0.0 is my IP) when I should be sending the provider's IP in the TO part.
> > This makes no sense. The TO should be sip:9057720000 at 18.104.22.168:5060
> > if that is the domain added in SPCE and the device is registered with.
> > SPCE would not send sip:9057720000 at 0.0.0.0 if it did, no calls would
> > work at all and your INVITE would never reach your provider.
> > Your provider should be routing by the request URI not the TO in any
> > case. I have no suggestion for you here, but I've constructed an INVITE
> > below for you to match with your own. Yours should look exactly the same
> > and is perfectly normal.
> > You can paste the INVITE message here by running the below command,
> > making an outbound call and pasting it to the list.
> > ngrep -d any -qt -W byline port 5060 > /tmp/outboundtest.txt
> >> He also says that the contact header is saying ngcp-lb where it should say the phone number that Im calling from.
> > The phone number is in the FROM and Contact is just a contact address,
> > nothing more. They must be used to working with end-user devices.
> >> And there is no remote party ID either.
> > I don't see R-PID anywhere in my INVITES, only P-A-I which is fine.
> > Couldn't know for sure without seeing an INVITE from your box.
> >> here is a log excerpt
> >> Reply from Outbound - S=403 - Forbidden To F=sip:19056670000 at 22.214.171.124 T=sip:9057720000 at 0.0.0.0 IP=126.96.36.199:5060 ID=sTOglmQQyiaAvzZKTUAR6LrFoSbsz9XE_b2b-1
> >> The docs arent very clear nor are there any examples available from my provider.
> >> Can anyone help?
> > Here is what an INVITE from you to them should look like.
> > U 2011/09/07 04:23:52.331277 188.8.131.52:5060 -> 184.108.40.206:5060
> > INVITE sip:9057720000 at 220.127.116.11:5060 SIP/2.0.
> > Max-Forwards: 10.
> > Record-Route:
> > <sip:18.104.22.168;r2=on;lr=on;ftag=57F6B415-4E672A1800034D60-8D868700>.
> > Record-Route:
> > <sip:127.0.0.1;r2=on;lr=on;ftag=57F6B415-4E672A1800034D60-8D868700>.
> > Via: SIP/2.0/UDP 22.214.171.124;branch=z9hG4bKf57d.f6e74992.0.
> > Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKVssPdalO;rport=5080.
> > From: Dave
> > <sip:9057720000 at 126.96.36.199:5060>;tag=57F6B415-4E672A1800034D60-8D868700.
> > To: <sip:9057720000 at 188.8.131.52:5060>.
> > CSeq: 10 INVITE.
> > Call-ID: c73cfbbd-923d5d6 at 192.168.1.134_b2b-1.
> > P-Asserted-Identity: <sip:9057720000 at 184.108.40.206:5060>.
> > Supported: timer.
> > Session-Expires: 300.
> > Min-SE: 90.
> > Content-Type: application/sdp.
> > Content-Length: 462.
> > Contact: <sip:ngcp-lb at 220.127.116.11:5060>
> > --Skyler
More information about the Spce-user