[Spce-user] Inbound and Outbound failing

[Hohl Matthias]

Hello,

 

I have an outbound rule that I left all options blank and put the description as default rule.

No, it is correct this way. It means that you allow all traffic out there.

 

I been communicating with our career. I do need to strip off the country code on outgoing and use their domain name. On receiving calls, they do not add the country code. Could this be breaking incoming?

If this is so, then you need to create rewrite rules for this peering for outgoing and incoming.

Firstly I would prefer to speak with your carrier to accept and send in full E.164 number format like 1 234 1234567 … 1 is for country like USA, 234 for area and 1234567 is the number.

If he agree with that, you have a lot of rewrite work less.

 

Btw: “striping off the country code” is bit confusing for me.. how your carrier then know, where to route your call? Or is this carrier just for country internal calls only? Like 1 for USA… normal behavior is, that carrier just accept call with valid country code like (example Austria)    +43 / 43 / 0043 

 

Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von Travis Garrison
Gesendet: Freitag, 9. März 2018 21:11
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Inbound and Outbound failing

 

I been communicating with our career. I do need to strip off the country code on outgoing and use their domain name. On receiving calls, they do not add the country code. Could this be breaking incoming? I tried creating a rewrite rule but according to the logs, it didn't actually apply or gets applied later. What peering rules do I need to change or create to accept all calls from this peer and to send out?

  _____  

From: Travis Garrison
Sent: Friday, March 9, 2018 8:18:06 AM
To: Matthias Hohl
Cc:  <mailto:spce-user at lists.sipwise.com> spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Inbound and Outbound failing 

 

Just recieved this from our provider

 

Basic logs show that on your outbound calls you are not using the domain sip.missouri-telecom.com and have a leading 1 on the calling number, ie looks like the calling number came through as  <sip:14178511779 at nvc.sip.netviscom.com> sip:14178511779 at nvc.sip.netviscom.com and  <sip:14178511779 at 69.55.128.80> sip:14178511779 at 69.55.128.80 and it should have been  <sip:4178511779 at sip.missouri-telecom.com> sip:4178511779 at sip.missouri-telecom.com.  Those calls got rejected with 403 - From URI not recognized which you should be able to see in your logs.

I tried putting sip.missouri-telecom.com in the host field on the peer but it still tries to send out as the ip address. I have an outbound rule that I left all options blank and put the description as default rule. Is that not correct? I followed the directions. I also have an inbound rule that matched from-user and .*

  _____  

From: Matthias Hohl < <mailto:matthias.hohl at telematica.at> matthias.hohl at telematica.at>
Sent: Friday, March 9, 2018 2:36:28 AM
To: Travis Garrison
Cc:  <mailto:spce-user at lists.sipwise.com> spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Inbound and Outbound failing 

 

Hello:

 ERROR: <script>: No PSTN gateways available -

This normally comes if you didnt create outbound peering rules for the peering group.

Also inbound you need a inbound peering rule... if there is none, no calls will be transported of this peering.

> Am 09.03.2018 um 05:33 schrieb Travis Garrison < <mailto:travis at netviscom.com> travis at netviscom.com>:
> 
> ERROR: <script>: No PSTN gateways available -

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180311/19701076/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5532 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180311/19701076/attachment-0001.p7s>