[Spce-user] Ris: connect 2 sipwise as trunk

Thu Nov 30 16:29:22 EST 2017

If I remove the ‘trusted source ip’ I get a 407 error.

Apparently tries to apply the caller’s realm to the subscriber auth and it
fails to authenticate

Proxy-Authorization: Digest username="0110002222", realm="d.voceblu.it",
nonce="WiB2m1ogdW+McwtYdiMw6t/WoFxcsYiR",
uri="sip:3355416588 at 94.125.235.56:5060;transport=udp",
response="4fd4ed9b67e55d141fb57bc193d08bd6", algorithm=MD5

But this is how it is configured:

domain=c.voceblu.it

user=0110002222

pwd=xxxxxxxxxxxxxxx

proxy=sip:[% sip_lb_ips.0 %]:[% kamailio.lb.port %]

[% IF sip_adv_ips.size -%]

contact=sip:[% sip_adv_ips.0 %]:[% kamailio.lb.port %]

[% ELSE -%]

contact=sip:[% sip_ext_ips.0 %]:[% kamailio.lb.port %]

[% END -%]

On 30 November 2017 at 22:13:53, stefanormc (stefanormc at gmail.com) wrote:

So I wiped and reconfigured peer/subscriber and now is registered again.

I Get a 403 error, relaying not allowed

Any suggestions?

Nov 30 22:11:37 centrale03 proxy[3478]: NOTICE: <script>: New request on
proxy - M=INVITE R=sip:3355416588 at 94.125.235.56:5060;transport=udp F=
sip:390110133435 at d.voceblu.it T=sip:3355416588 at 94.125.235.56 IP=
94.125.232.155:5060 (127.0.0.1:5060)
ID=88253ZmFkMTAxZWJjNjdlNjhjMzI4MTU2YTZlMzE3NDIxMjE_b2b-1 UA='<null>'

Nov 30 22:11:37 centrale03 proxy[3478]: NOTICE: <script>: Call from trusted
peer with uuid 'eee76c3b-1019-411d-b1f4-6815e2e76bdd' -
R=sip:3355416588 at 94.125.235.56:5060;transport=udp
ID=88253ZmFkMTAxZWJjNjdlNjhjMzI4MTU2YTZlMzE3NDIxMjE_b2b-1 UA='<null>'

Nov 30 22:11:37 centrale03 proxy[3478]: NOTICE: <script>: Rejecting peering
attempt with non-local request domain -
R=sip:3355416588 at 94.125.235.56:5060;transport=udp
ID=88253ZmFkMTAxZWJjNjdlNjhjMzI4MTU2YTZlMzE3NDIxMjE_b2b-1 UA='<null>'

Nov 30 22:11:37 centrale03 proxy[3478]: NOTICE: <script>: Setting acc
source-leg for uuid 'eee76c3b-1019-411d-b1f4-6815e2e76bdd':
'eee76c3b-1019-411d-b1f4-6815e2e76bdd|<null>|<null>|0|||0||||call|<null>|1512076297.538332||||||||||||0|'
- R=sip:3355416588 at 94.125.235.56:5060;transport=udp
ID=88253ZmFkMTAxZWJjNjdlNjhjMzI4MTU2YTZlMzE3NDIxMjE_b2b-1 UA='<null>'

Nov 30 22:11:37 centrale03 proxy[3478]: NOTICE: <script>: Setting acc
destination-leg for uuid '0':
'0|||0|<null>|0|3355416588|94.125.235.56|||0||||||||||||3355416588|' -
R=sip:3355416588 at 94.125.235.56:5060;transport=udp
ID=88253ZmFkMTAxZWJjNjdlNjhjMzI4MTU2YTZlMzE3NDIxMjE_b2b-1 UA='<null>'

Nov 30 22:11:37 centrale03 proxy[3463]: NOTICE: <script>: New request on
proxy - M=ACK R=sip:3355416588 at 94.125.235.56:5060;transport=udp F=
sip:390110133435 at d.voceblu.it T=sip:3355416588 at 94.125.235.56 IP=
94.125.232.155:5060 (127.0.0.1:5060)
ID=88253ZmFkMTAxZWJjNjdlNjhjMzI4MTU2YTZlMzE3NDIxMjE_b2b-1 UA='<null>'

Thanks

Stefano

On 30 November 2017 at 16:49:47, stefanormc (stefanormc at gmail.com) wrote:

Still not working!

I did manage to send calls from peer —> subscriber but I get a 407 error

I can’t seem to get the peer registered against the subscriber as I did
yesterday

I first configured the web interface and then manually updated
/etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.tt2;
then I re-applied ngcpcfg but no registration

How do I match credentials in reg_agent to the right peer?

Il giorno 30 novembre 2017 @ 15:06:41, stefanormc (stefanormc at gmail.com) ha
scritto:

I had to delete and recreate the rule. Apparently adding the description
solved it

centrale:~# ngcp-sercmd proxy lcr.dump_rules

{

lcr_id: 1

rule_id: 11

prefix:

from_uri: ^sip:.+ at v\.voceblu\.it$

request_uri:

stopper: 0

}

{

gw_index: 2

priority: 1

weight: 1

}

{

lcr_id: 1

rule_id: 10

prefix:

from_uri: ^sip:.+ at d\.voceblu\.it$

request_uri:

stopper: 0

}

Il giorno 30 novembre 2017 @ 13:11:44, Barry Flanagan (barry at flanagan.ie)
ha scritto:

On 30 November 2017 at 11:48, stefanormc <stefanormc at gmail.com> wrote:

> Instead of deleting and recreating the rule I moved it to the other peer.
> Could that be the problem?
>
>
>
It seems to me your caller patterns are not right. I would have thought
something like:

^sip:.+ at d\.voceblu\.it$

...would be mo0re what is needed.

-Barry Flanagan

On 30 November 2017 at 12:42:46, stefanormc (stefanormc at gmail.com) wrote:
>
> It doesn’t seem to effect the rules
>
> I’m on 5.4.1
>
>
> On 30 November 2017 at 12:37:19, Daniel Grotti (dgrotti at sipwise.com)
> wrote:
>
> Try to run:
>
> ngcp-sercmd proxy  lcr.reload
>
> and then again:
>
> ngcp-sercmd proxy lcr.dump_rules
>
> --
> Daniel Grotti
> Head of Customer Support
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
>
> Office: +43(0)130120332 <+43%201%2030120332>
> Email: dgrotti at sipwise.com
> Website: https://www.sipwise.com
>
> On 11/30/2017 12:32 PM, stefanormc wrote:
>
> There is no rule in ngcp-sercmd proxy lcr.dump_rules
>
> Last login: Thu Nov 30 12:04:19 2017 from 93-57-17-112.ip162.fastwebnet.it
>
> centrale:~# ngcp-sercmd proxy lcr.dump_rules
>
> {
>
> lcr_id: 1
>
> rule_id: 9
>
> prefix:
>
> from_uri: @digi.voceblu.it
>
> request_uri:
>
> stopper: 0
>
> }
>
> {
>
> gw_index: 3
>
> priority: 1
>
> weight: 1
>
> }
>
> {
>
> lcr_id: 1
>
> rule_id: 7
>
> prefix:
>
> from_uri: @voceblu.it
>
> request_uri:
>
> stopper: 0
>
> }
>
> {
>
> gw_index: 1
>
> priority: 2
>
> weight: 1
>
> }
>
> {
>
> lcr_id: 1
>
> rule_id: 6
>
> prefix:
>
> from_uri: old at d.voceblu.it
>
> request_uri:
>
> stopper: 0
>
> }
>
> {
>
> gw_index: 4
>
> priority: 1
>
> weight: 1
>
> }
>
> {
>
> lcr_id: 1
>
> rule_id: 4
>
> prefix:
>
> from_uri: @geva.voceblu.it
>
> request_uri:
>
> stopper: 0
>
> }
>
> {
>
> gw_index: 1
>
> priority: 2
>
> weight: 1
>
> }
>
> 0
>
> centrale:~#
>
>
> But there is in web interface:
>
> # Prefix Caller Pattern State Description Peer Group Peer Name Peer Host Peer
> IP Peer State Priority Weight
> 4
> @geva.voceblu.it 1
> TWT TWT voce.voipeople.it 77.239.128.7 1 2 1
> 6
> ^d\.voceblu\.it$ 1 seleziona numeri digitel centrale03 centrale03
> 94.125.235.56 1 1 1
> 7
> @voceblu.it 1
> TWT TWT voce.voipeople.it 77.239.128.7 1 2 1
> 8
> @v.voceblu.it 1
> centrale03 centrale03
> 94.125.235.56 1 1 1
> 9
> @digi.voceblu.it 1 seleziona tutti quelli diretti digitel Digitel diretto Digitel
> diretto voip.digitelitalia.it 109.238.17.166 1 1 1
>
>
> On 30 November 2017 at 11:59:24, Daniel Grotti (dgrotti at sipwise.com)
> wrote:
>
> it seems you do not have it.
> Please try to re-save the rule, and also do:
>
> ngcp-sercmd proxy lcr.dump_gws
> ngcp-sercmd proxy lcr.dump_rules
>
>
> Do you see your peer there and the rule?
>
> --
> Daniel Grotti
> Head of Customer Support
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
>
> Office: +43(0)130120332 <+43%201%2030120332>
> Email: dgrotti at sipwise.com
> Website: https://www.sipwise.com
>
> On 11/30/2017 11:54 AM, stefanormc at gmail.com wrote:
>
> There is a rule catching all d.voceblu.it
>
>
> -------- Messaggio originale --------
> Oggetto: Re: [Spce-user] connect 2 sipwise as trunk
> Da: Daniel Grotti
> A: stefanormc ,spce-user at lists.sipwise.com
> CC:
>
>
> Hi,
> problem is that you do not have a peering rule matching the called (anc
> callind) part, see below.
> Please check your peering rules in your peerin server. Have you at least
> created the "catch-all" rule?
>
> --
> Daniel Grotti
> Head of Customer Support
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
>
> Office: +43(0)130120332 <+43%201%2030120332>
> Email: dgrotti at sipwise.com
> Website: https://www.sipwise.com
>
> On 11/30/2017 11:29 AM, stefanormc wrote:
>
> Load gws matching calling part 'sip:390118118673 at d.voceblu.it' and called
> user '3355416588' and called part 'sip:3355416588 at d.voceblu.it;user=phone'
> - R=sip:3355416588 at d.voceblu.it;user=phone ID=3c4632c304e2-1vukdq0ac0ql at snom190
> UA='snom190/3.60x'
>
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20171130/58b65455/attachment-0001.html>