[Spce-user] SIP REINVITE

Daniel Grotti dgrotti at sipwise.com
Mon May 26 05:24:39 EDT 2014


Hi,
I suggest to increase sems log "sems-stat -c "set_loglevel 3" and the
check your kamailio-proxy.log and sems.log.
408 means that somebody is not responding, so you need to figure out
where and why the reinvite gets 408.
Reinvites and moh are fully supported, there is no configuration to set.

Daniel







On 05/25/2014 09:40 PM, Tabi Tabe Tabi wrote:
> Hi Colleagues,
>
> We have a situation with MoH from a PBX connected to SPCE 3.2.1
>
> When a call is placed on hold, there is no MoH and the call drops. We
> ran packet capture and noticed the following:
>
>   * When the call is placed on hold, a second invite message is sent
>     to SPCE
>   * SPCE replies with a 408 timeout *(they are both on the same LAN
>     and normal call flow is fine)*
>   * *Then the call drops*
>   * Also, in the invite from SPCE to the PBX we see the following 18 4
>     8 100 13 118 110 96, but no 101 (RTP Payload). Not sure if they
>     are related.
>
> We were informed by the PBX vendor that the the reason for the MoH
> failure is due SIP REINVITE not activated on SPCE. I know SPCE support
> SIP REINVITE but not sure how and where to verify the configuration.
> Any ideas in the right direction is appreciated.
>
> Regards,
>
>
> -- 
> ...Tabi
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://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/20140526/d27ce39d/attachment-0001.html>


More information about the Spce-user mailing list