[Spce-user] Multiple SIP Interfaces Peering Problem

afshin afzali a.afzali2003 at gmail.com
Thu Dec 3 02:57:35 EST 2015


Hi Andrew,

I do not know how to thank you for the exceptional support :) I did as it
has been stated in that conversion. I removed rtp_ext from eth2 and added a
new type (i.e. rtp_core) and used it as rtp_interface in my peer's
preference. It works! (still I receive 500 from my peer server however. But
the ip address is the new one) The thing that I am not sure about is that
should I remove sip_ext type from eth1 interface (the interface that I
added extra socket). If I remove sip_ext, will I be able able to receive
calls?

Best,

- Afshin

On Wed, Dec 2, 2015 at 7:45 PM, afshin afzali <a.afzali2003 at gmail.com>
wrote:

> Andrew,
>
> really interesting :) let me do it!
> I'll be back soon.
>
> Best,
> - Afshin
>
> On Wed, Dec 2, 2015 at 7:34 PM, Andrew Pogrebennyk <
> apogrebennyk at sipwise.com> wrote:
>
>> That takes a little bit more knowledge about the system internals
>> because it's not documented yet :)
>> Check this thread:
>> https://lists.sipwise.com/pipermail/spce-user/2015-August/009279.html
>> Also it'll be described in the handbook for our next release mr4.2,
>> check the attached html - the same also applies to mr3.8+ versions.
>>
>> On 12/02/2015 04:57 PM, afshin afzali wrote:
>> > Hi Andrew,
>> >
>> > Yes you are right. I am getting 500 from the peer server. I do not know
>> > why but I have noticed that in the offer SDP which I am sending, the IP
>> > address is set to eth0's address. I need to set it to my eth2's IP
>> > address (I have a dedicated ip for the peer's rtp). How I can do it ? :)
>> >
>> > Best,
>> > - Afshin
>> >
>> > On Wed, Dec 2, 2015 at 7:06 PM, Andrew Pogrebennyk
>> > <apogrebennyk at sipwise.com <mailto:apogrebennyk at sipwise.com>> wrote:
>> >
>> >     On 12/02/2015 04:32 PM, afshin afzali wrote:
>> >     > Hi Andrew,
>> >     >
>> >     > One step forward :) Seems that it works properly except one
>> thing. The
>> >     > peer server replies with 500 internal server error! as you can
>> see in
>> >     > the following log traces. The magic is that I can not see any sip
>> packet
>> >     > exchange with my peer server (using tcpdump) :(
>> >     >  [...]
>> >     > Dec  2 10:19:02 ngcp lb[32609]: NOTICE: <script>: Reply from
>> Outbound -
>> >     > S=500 - Server Internal Error M=INVITE IP=udp:myPeerServer:5060
>> >     > ID=da6a8305f1290f52 at QUZTSElOLVBDLkJhc2FtYWQuQ09N_b2b-1
>> UA='<null>'
>> >
>> >     In the IP field we see that 500 is coming from the server.
>> >     Why tcpdudmp doesn't see it, perhaps you are capturing on eth0? Try
>> with
>> >     -i any option.
>> >
>> >     Andrew
>> >
>> >
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20151203/cda0d4d6/attachment-0001.html>


More information about the Spce-user mailing list