Hi,
i've installed one OpenSER-Server only for SIP-Trunking. (it is used for security and reliability reasons between a softswitch and some customer-pbx's)
one of our customer wants to use asterisk with its "monitor peer" feature. so the asterisk sends every second a OPTIONS SIP Message. But the OpenSER does only answer with "Request Timeout". So asterisk thinks, the SIP Proxy is offline. What can i do about it?
Bye, Martin
martin@campus-merseburg.de wrote:
Hi,
i've installed one OpenSER-Server only for SIP-Trunking. (it is used for security and reliability reasons between a softswitch and some customer-pbx's)
one of our customer wants to use asterisk with its "monitor peer" feature. so the asterisk sends every second a OPTIONS SIP Message. But the OpenSER does only answer with "Request Timeout". So asterisk thinks, the SIP Proxy is offline. What can i do about it?
You have to find out why openser does not relay the OPTIONS message. - watch syslog (put log statements into your openser.cfg) - use ngrep to verifiy if the OPTIONS request is forwarded "ngrep -d any port 5060"
Maybe there is a problem with the OPTIONS request (missing Route headers ...)
regards klaus
Am 28.4.2006 schrieb "Klaus Darilion" klaus.mailinglists@pernau.at:
Hi,
i've installed one OpenSER-Server only for SIP-Trunking. (it is used for security and reliability reasons between a softswitch and some customer-pbx's)
one of our customer wants to use asterisk with its "monitor peer" feature. so the asterisk sends every second a OPTIONS SIP Message. But the OpenSER does only answer with "Request Timeout". So asterisk thinks, the SIP Proxy is offline. What can i do about it?
You have to find out why openser does not relay the OPTIONS message.
- watch syslog (put log statements into your openser.cfg)
- use ngrep to verifiy if the OPTIONS request is forwarded "ngrep -d any
port 5060"
Maybe there is a problem with the OPTIONS request (missing Route headers ...)
should it work when i relay the message to the softswitch?
ciao
martin@campus-merseburg.de wrote:
Am 28.4.2006 schrieb "Klaus Darilion" klaus.mailinglists@pernau.at:
Hi,
i've installed one OpenSER-Server only for SIP-Trunking. (it is used for security and reliability reasons between a softswitch and some customer-pbx's)
one of our customer wants to use asterisk with its "monitor peer" feature. so the asterisk sends every second a OPTIONS SIP Message. But the OpenSER does only answer with "Request Timeout". So asterisk thinks, the SIP Proxy is offline. What can i do about it?
You have to find out why openser does not relay the OPTIONS message.
- watch syslog (put log statements into your openser.cfg)
- use ngrep to verifiy if the OPTIONS request is forwarded "ngrep -d any
port 5060"
Maybe there is a problem with the OPTIONS request (missing Route headers ...)
should it work when i relay the message to the softswitch?
You have to relay the message to the softswitch.
regards klaus
Klaus Darilion wrote:
martin@campus-merseburg.de wrote:
Am 28.4.2006 schrieb "Klaus Darilion" klaus.mailinglists@pernau.at:
Hi,
i've installed one OpenSER-Server only for SIP-Trunking. (it is used for security and reliability reasons between a softswitch and some customer-pbx's)
one of our customer wants to use asterisk with its "monitor peer" feature. so the asterisk sends every second a OPTIONS SIP Message. But the OpenSER does only answer with "Request Timeout". So asterisk thinks, the SIP Proxy is offline. What can i do about it?
You have to find out why openser does not relay the OPTIONS message.
- watch syslog (put log statements into your openser.cfg)
- use ngrep to verifiy if the OPTIONS request is forwarded "ngrep -d any
port 5060"
Maybe there is a problem with the OPTIONS request (missing Route headers ...)
should it work when i relay the message to the softswitch?
You have to relay the message to the softswitch.
or you fake the reply:
if (is_method("OPTIONS")) { sl_send_reply("200","ok"); }
Am 28.4.2006 schrieb "Klaus Darilion" klaus.mailinglists@pernau.at:
Klaus Darilion wrote:
martin@campus-merseburg.de wrote:
Am 28.4.2006 schrieb "Klaus Darilion" klaus.mailinglists@pernau.at:
Hi,
i've installed one OpenSER-Server only for SIP-Trunking. (it is used for security and reliability reasons between a softswitch and some customer-pbx's)
one of our customer wants to use asterisk with its "monitor peer" feature. so the asterisk sends every second a OPTIONS SIP Message. But the OpenSER does only answer with "Request Timeout". So asterisk thinks, the SIP Proxy is offline. What can i do about it?
You have to find out why openser does not relay the OPTIONS message.
- watch syslog (put log statements into your openser.cfg)
- use ngrep to verifiy if the OPTIONS request is forwarded "ngrep -d any
port 5060"
Maybe there is a problem with the OPTIONS request (missing Route headers ...)
should it work when i relay the message to the softswitch?
You have to relay the message to the softswitch.
or you fake the reply:
if (is_method("OPTIONS")) { sl_send_reply("200","ok"); }
tanks. that is what i searched for.
-
Klaus Darilion -
martin＠campus-merseburg.de