[Spce-user] 2 asterisk subscribers - subscriber sst setting ignored?

[Matthew Ogden]

Ok, I just thought that NGCP would strip that out for some reason :).

Is this only in the case of subscribers I assume. In the case of a peer,
the reinvite from the peers subscriber will never reach my subscriber will
it?
(If it does reach my subsciber, how would I be able to control their
them?) But if it doesn't why is two subscribers any different to my
subscriber, in-dialog to a peers subscriber?

Sorry if that's a silly question, just thought the role of handling
"hiding details" and creating compatibility of the SBC was the same
between two subscribers as it was between a subscriber and a peer. But
before I disabled SST when my subscriber made a call out to my peer, the
peer used "UPDATE", and my subscriber used "REINVITE", but they appeared
to be on completely different timing mechanisms etc. (So it didn't make
sense that the REINVITE from one subscriber goes to the other - I thought
it was only for its own call leg, and timers were negotiated independently
on each leg).

Kind Regards

> -----Original Message-----
> From: spce-user-bounces at lists.sipwise.com [mailto:spce-user-
> bounces at lists.sipwise.com] On Behalf Of Daniel Grotti
> Sent: 11 October 2013 02:54 PM
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] 2 asterisk subscribers - subscriber sst setting
> ignored?
>
> Hi,
>
> sst_enable=no means that NGCP will not send out SST to subscribers and
> not that NGCP does't accept SST.
>
> So in your case, since the callee sends the reinvite, you need to manage
it on
> the caller side or disable sst on the callee side.
>
> Daniel
>
>
>
>
> On 10/11/2013 02:36 PM, Matthew Ogden wrote:
> > Hi all,
> >
> >
> >
> > I have two asterisk subscribers, and SPCE sitting in the middle. My
> > domain is setup to ignore SST by default and rely on SEMS to dead call
> > detection. The caller asterisk configuration itself has SST set to
> > refuse. The called party doesn't have this set to Accept.
> >
> >
> >
> > Then the caller calls the callee, its passing the "supported:
> > replaces, timer" in the INVITE to the callee. The callee asterisk box,
> > picks this up, an in its 200 OK, says "require: timer". All goes well
> > for 15 minutes, and then the calls ends, because the callee, does a
> > REINVITE, the REINVITE goes through to the caller, and the caller says
> > "420 Option Disabled".
> >
> >
> >
> > 1)      If SST is disabled, why is it passing "supported: replaces,
> > timer" to the callee?
> >
> > 2)      Why is the callee reinvite being passed to the caller? (Surely
> > the reinvite is only for its leg of the call?)
> >
> >
> >
> > I can disable it on my callee, but I was wondering if 1 or 2 above is
> > actually a bug in SPCE as well that should be looked at?
> >
> >
> >
> > If its SPCE or Homer teammembers I can give you the pcap, and any logs
> > you need if you want.
> >
> >
> >
> > Regards
> >
> > matthew
> >
> >
> >
> > _______________________________________________
> > Spce-user mailing list
> > Spce-user at lists.sipwise.com
> > http://lists.sipwise.com/listinfo/spce-user
> >
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user