[Spce-user] SOLVED: Incoming calls are not working (403 - invalid called party domain)

[Thomas Georg]

Hi Daniel,

thank you for this hint!
Now it works with the right Inbound peering rule and rewrite rule.

The 500 server error  in the call verification tool still exists but I will debug that later....

Regards
Thomas


Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von Daniel Grotti
Gesendet: Donnerstag, 15. Februar 2018 10:39
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Incoming calls are not working (403 - invalid called party domain)

Hi Thonma,
this is not a problem of Rewrting rules, but "Inbound Peering Rules". Please check documentation for that.
Please notice, as well, the log:


Field 'to_domain' with value '93.189.171.93' did not match pattern 'sip\.omnidat\.net'


So the TO header is not accepted by your Inbound peering Rules defined in your SIP Peering Group.

Cheers,



--

Daniel Grotti

Head of Customer Support

Sipwise GmbH, Campus 21/Europaring F15

AT-2345 Brunn am Gebirge



Office: +43(0)130120332

Email: dgrotti at sipwise.com<mailto:dgrotti at sipwise.com>

Website: https://www.sipwise.com
On 02/15/2018 01:44 AM, Thomas Georg wrote:
Hi list,

with debug level 2 I got the following output in kamailio-proxy.log  (thanks to Daniel for this hint):

Feb 15 01:07:39 spce proxy[3215]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:+4971422289800 at 185.156.158.12:5060<mailto:R=sip:+4971422289800 at 185.156.158.12:5060> F=sip:+49854711 at 93.189.171.91<mailto:F=sip:+49854711 at 93.189.171.91> T=sip:+4971422289800 at 93.189.171.93:5060<mailto:T=sip:+4971422289800 at 93.189.171.93:5060> IP=93.189.168.93:5060 (127.0.0.1:5060) ID=521c-47c-11520180539-SS7_FRA1_1_1-0-93.189.171.91 UA='Dialogic-SIP/10.5.3.52851 SS7_FRA1_1_1 0'
Feb 15 01:07:39 spce proxy[3215]: INFO: <script>: Load domain preferences for callee - R=sip:+4971422289800 at 185.156.158.12:5060<mailto:R=sip:+4971422289800 at 185.156.158.12:5060> ID=521c-47c-11520180539-SS7_FRA1_1_1-0-93.189.171.91 UA='Dialogic-SIP/10.5.3.52851 SS7_FRA1_1_1 0'
Feb 15 01:07:39 spce proxy[3215]: INFO: <script>: Clean domain preferences for callee - R=sip:+4971422289800 at 185.156.158.12:5060<mailto:R=sip:+4971422289800 at 185.156.158.12:5060> ID=521c-47c-11520180539-SS7_FRA1_1_1-0-93.189.171.91 UA='Dialogic-SIP/10.5.3.52851 SS7_FRA1_1_1 0'
Feb 15 01:07:39 spce proxy[3215]: NOTICE: <script>: Call from PSTN - R=sip:+4971422289800 at 185.156.158.12:5060<mailto:R=sip:+4971422289800 at 185.156.158.12:5060> ID=521c-47c-11520180539-SS7_FRA1_1_1-0-93.189.171.91 UA='Dialogic-SIP/10.5.3.52851 SS7_FRA1_1_1 0'
Feb 15 01:07:39 spce proxy[3215]: INFO: <script>: Checking PSTN peer group '2' - R=sip:+4971422289800 at 185.156.158.12:5060<mailto:R=sip:+4971422289800 at 185.156.158.12:5060> ID=521c-47c-11520180539-SS7_FRA1_1_1-0-93.189.171.91 UA='Dialogic-SIP/10.5.3.52851 SS7_FRA1_1_1 0'
Feb 15 01:07:39 spce proxy[3215]: NOTICE: <script>: Field 'to_domain' with value '93.189.171.93' did not match pattern 'sip\.omnidat\.net' - R=sip:+4971422289800 at 185.156.158.12:5060<mailto:R=sip:+4971422289800 at 185.156.158.12:5060> ID=521c-47c-11520180539-SS7_FRA1_1_1-0-93.189.171.91 UA='Dialogic-SIP/10.5.3.52851 SS7_FRA1_1_1 0'
Feb 15 01:07:39 spce proxy[3215]: NOTICE: <script>: Rejecting call with 403 - invalid called party domain - R=sip:+4971422289800 at 185.156.158.12:5060<mailto:R=sip:+4971422289800 at 185.156.158.12:5060> ID=521c-47c-11520180539-SS7_FRA1_1_1-0-93.189.171.91 UA='Dialogic-SIP/10.5.3.52851 SS7_FRA1_1_1 0'
Feb 15 01:07:39 spce proxy[3215]: INFO: <script>: Runtime for request INVITE was 2562 usec - ID=521c-47c-11520180539-SS7_FRA1_1_1-0-93.189.171.91

After that I built the following rule to replace the ip address with the sip domain
Match pattern:                                 \b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b
Replacement Pattern :                  sip.omnidat.net
Field:                                                    Callee

But I got the same output in the log.

Any hints?

Thank you
Thomas

Von: Thomas Georg
Gesendet: Sonntag, 11. Februar 2018 10:16
An: 'spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>' <spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>>
Betreff: Call Routing Verfication Test results in Server error 500 (sometimes)

Hi,

I am new to sipwise and installed e fresh instance with the iso on my vmware server (4 Cores, 4GB RAM, 128GB HDD).
I did all steps in the manual and am able to call in and out if I dial the number in E.164 format.
If I establish a call with a local number e.g. 08154711 the outbound rule for the callee doesn't do anything.
I tried to test with the call routing verification tool but sometimes it gives an result (without using the number manipulation) but most of the time I get an 500 Server error.

Any idea? Where are the incident information stored on the  filesystem to debug a little bit by myself?

Regards
Thomas





_______________________________________________

Spce-user mailing list

Spce-user at lists.sipwise.com<mailto: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/mailman/private/spce-user_lists.sipwise.com/attachments/20180215/4dfd37f5/attachment.html>