Re: [reSIProcate-users] 405 Method Not Allowed

[Scott Godin <sgodin@xxxxxxxxxxxxxxxxx>]

If the MESSAGE is out-of-dialog – then you need to implement a ServerPagerMessageHandler.

 

DialogUsageManager:

      void setClientPagerMessageHandler(ClientPagerMessageHandler*);

      void setServerPagerMessageHandler(ServerPagerMessageHandler*);

 

Check out dum/test/basicMessage.cpp for a sample.

 

Scott

 

From: resiprocate-users-bounces@xxxxxxxxxxxxxxx [mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Richard Stellingwerff
Sent: Friday, October 23, 2009 2:04 PM
To: resiprocate-users@xxxxxxxxxxxxxxx
Subject: [reSIProcate-users] 405 Method Not Allowed

 

Hi,

When my UAC (powered by reSIProcate) receives a message of method type 'MESSAGE' the UAC automatically responds with 405 Method Not Allowed.

In the master profile I have enabled both the method as well as the mime type, like this:

profile->addSupportedMimeType(resip::MESSAGE, resip::Mime("application", "ivocs-alarm+xml"))
profile->addSupportedMethod(resip::MESSAGE);

Every other method so far has worked just fine.. Anyone have any idea what I might be missing?

Kind regards,
Richard Stellingwerff.