Up to Discussions in OpenSBC

This Question is Possibly Answered

1 "correct" answer available (5 pts) 2 "helpful" answers available (1 pts)
10 Replies Last post: Jun 30, 2009 8:25 PM by dablackgreek  
 
dmigardos
3 posts since
May 9, 2008

May 9, 2008 4:24 PM

MWI (Message Waiting Indication) with opensbc & asterisk

I am using opensbc in front of my asterisk deployment. MWI does not
appear to be working.

I took a sip trace and noticed the notify for MWI is sent from asterisk to
opensbc but opensbc response back with a "405 Method Not Allowed"
. Does MWI work on opensbc when you're using Upper Registration Routes to
asterisk or any other sip server? (Just incase asterisk was sending a strange
notify message i also tried this with my broadsoft switch and received the same
response)

Here is a caption of the logs. My apologies if this has been discussed
in previous posts, I've looked for several hours and could not find any
confirmation on the discussion boards.


Version of opensbc is 1.1.4


6add0e19-e9f1baff-b7a2df44@192.168.7.75
336205:44:40.087 INF: CID=0x0a82 PROXY: Session DESTROYED
336205:44:44.494 DTL: CID=0x0a82 NICT(3433925657) Event( Timer-K ) Interval: 5000
336205:44:44.494 DTL: CID=0x0a82 NICT(3433925657) Event(Final)
336205:44:44.494 DTL: CID=0x0000 *** REMOVED TRANSACTION *** NICT|6add0e19-e9f1baff-b7a2df44@192.168.7.75|z9hG4bK3e6c70bd3b1cdd11969aaf32d5ad55fd-a076b0ee67b01c83cf887de37cd0ac56|REGISTER
336205:44:44.494 DBG: CID=0x0000 GC: First Stale Object SIPTransaction
336205:44:44.495 DBG: CID=0x0a82 TRANSACTION: (NICT) DESTROYED
336205:44:44.495 DTL: CID=0x0a82 NICT(3433925657) *** DESTROYED *** - NICT|6add0e19-e9f1baff-b7a2df44@192.168.7.75|z9hG4bK3e6c70bd3b1cdd11969aaf32d5ad55fd-a076b0ee67b01c83cf887de37cd0ac56|REGISTER
336205:44:44.993 DTL: CID=0x0a82 NICT(3433925661) Event( Timer-K ) Interval: 5000
336205:44:44.994 DTL: CID=0x0a82 NICT(3433925661) Event(Final)
336205:44:44.994 DTL: CID=0x0000 *** REMOVED TRANSACTION *** NICT|6add0e19-e9f1baff-b7a2df44@192.168.7.75|z9hG4bK1c0d92bd3b1cdd11969aaf32d5ad55fd-5ad2325ca4bbb01c9e281b9973397946|REGISTER
336205:44:44.994 DBG: CID=0x0000 GC: First Stale Object SIPTransaction
336205:44:44.995 DBG: CID=0x0a82 TRANSACTION: (NICT) DESTROYED
336205:44:44.995 DTL: CID=0x0a82 NICT(3433925661) *** DESTROYED *** - NICT|6add0e19-e9f1baff-b7a2df44@192.168.7.75|z9hG4bK1c0d92bd3b1cdd11969aaf32d5ad55fd-5ad2325ca4bbb01c9e281b9973397946|REGISTER
336205:44:50.937 DBG: CID=0x0b29 RCV: enc=0 575 Bytes from RCVADDR: xxx.xxx.xxx.82:RCVPORT: 5060:UDP (NOTIFY sip:5164369839@xxx.xxx.xxx.67:65080 SIP/2.0)
336205:44:50.938 DBG: CID=0x0b29
336205:44:50.938 DBG: CID=0x0b29 RECEIVE: REQ: NOTIFY (102)
336205:44:50.938 DBG: CID=0x0b29 FROM: sip:asterisk@xxx.xxx.xxx.82
336205:44:50.938 DBG: CID=0x0b29 TO: sip:5164369839@xxx.xxx.xxx.67:65080
336205:44:50.938 DBG: CID=0x0b29 XOR: FALSE
336205:44:50.938 DBG: CID=0x0b29 SRC: xxx.xxx.xxx.82 PORT: 5060
336205:44:50.938 DBG: CID=0x0b29
336205:44:50.939 DBG: CID=0x0b29
336205:44:50.939 DBG: CID=0x0b29 *** CREATING TRANSACTION (NIST) ***
336205:44:50.939 DBG: CID=0x0b29 Message: NOTIFY sip:5164369839@xxx.xxx.xxx.67:65080 SIP/2.0
336205:44:50.939 DBG: CID=0x0b29 Call-Id: 2ffc421156409b7551b56acb307c4a73@xxx.xxx.xxx.82
336205:44:50.939 DBG: CID=0x0b29
336205:44:50.940 DTL: CID=0x0b29 NIST(3433925663) *** CREATED *** - NIST|2ffc421156409b7551b56acb307c4a73@xxx.xxx.xxx.82|z9hG4bK6e1b55dc|NOTIFY
336205:44:50.941 DTL: CID=0x0b29 NIST(3433925663) Event(SIPMessage) - NOTIFY sip:5164369839@xxx.xxx.xxx.67:65080 SIP/2.0
336205:44:50.941 DBG: CID=0x0b29 TRANSACTION: (NIST) NOTIFY sip:5164369839@xxx.xxx.xxx.67:65080 SIP/2.0 State: 0
336205:44:50.941 DTL: CID=0x0b29 NIST(3433925663) StateIdle->StateTrying
336205:44:50.941 DBG: CID=0x0b29 Event: SIPStack::Enqueue(NOTIFY sip:5164369839@xxx.xxx.xxx.67:65080 SIP/2.0)
336205:44:50.942 DBG: CID=0x0b29 Event: B2BUserAgent::ProcessEvent( NOTIFY sip:5164369839@xxx.xxx.xxx.67:65080 SIP/2.0 )
336205:44:50.942 INF: CID=0x0b29 Event: Setting UA Core BackDoor to handle event NOTIFY
336205:44:50.944 DTL: CID=0x0b29 Event: ---> Inbound - NOTIFY sip:5164369839@xxx.xxx.xxx.67:65080 SIP/2.0
336205:44:50.944 WRN: CID=0x06cb CallSessionManager::OnCreateServerSession() got a None-INVITE request
336205:44:50.944 WRN: CID=0x06cb CallSessionManager::OnCreateServerSession() returning NULL
336205:44:50.944 DTL: CID=0x06cb *** MESSAGE ARRIVAL *** No Session available to handle NOTIFY sip:5164369839@xxx.xxx.xxx.67:65080 SIP/2.0
336205:44:50.945 DTL: CID=0x0b29 Found NIST|2ffc421156409b7551b56acb307c4a73@xxx.xxx.xxx.82|z9hG4bK6e1b55dc|NOTIFY for SIP/2.0 405 Method Not Allowed
336205:44:50.946 DTL: CID=0x0b29 NIST(3433925663) Event(SIPMessage) - SIP/2.0 405 Method Not Allowed
336205:44:50.946 DBG: CID=0x0b29 TRANSACTION: (NIST) SIP/2.0 405 Method Not Allowed State: 1
336205:44:50.947 DTL: CID=0x0b29 NIST(3433925663)HandleStateTrying->StateCompleted
336205:44:50.948 DBG: CID=0x0b29
336205:44:50.948 DBG: CID=0x0b29 TRANSMIT: RESPONSE: SIP/2.0 405 Method Not Allowed
336205:44:50.948 DBG: CID=0x0b29 TO: sip:5164369839@xxx.xxx.xxx.67:65080
336205:44:50.948 DBG: CID=0x0b29 REQ: NOTIFY (102)
336205:44:50.948 DBG: CID=0x0b29 XOR: FALSE
336205:44:50.948 DBG: CID=0x0b29 DST: xxx.xxx.xxx.82 PORT: 5060
336205:44:50.948 DBG: CID=0x0b29
336205:44:50.951 DBG: CID=0x0b29
336205:44:50.951 DBG: CID=0x0b29 SEND: enc=0 327 Bytes to xxx.xxx.xxx.82:5060:UDP (SIP/2.0 405 Method Not Allowed) Interface Address=xxx.xxx.xxx.67
336205:44:50.951 DBG: CID=0x0b29 SIP/2.0 405 Method Not Allowed
336205:44:50.951 DBG: CID=0x0b29 From: "asterisk" <sip:asterisk@xxx.xxx.xxx.82>;tag=as162ffd9e
336205:44:50.951 DBG: CID=0x0b29 To: <sip:5164369839@xxx.xxx.xxx.67:65080>
336205:44:50.951 DBG: CID=0x0b29 Via: SIP/2.0/UDP xxx.xxx.xxx.82:5060;branch=z9hG4bK6e1b55dc;rport=5060;received=xxx.xxx.xxx.82
336205:44:50.951 DBG: CID=0x0b29 CSeq: 102 NOTIFY
336205:44:50.951 DBG: CID=0x0b29 Call-ID: 2ffc421156409b7551b56acb307c4a73@xxx.xxx.xxx.82
336205:44:50.951 DBG: CID=0x0b29 Content-Length: 0
336205:44:50.951 DBG: CID=0x0b29
336205:44:50.951 DBG: CID=0x0b29
336205:45:11.494 DTL: CID=0x0b41 NIST(3433925659) Event( Timer-J ) Interval: 32000
336205:45:11.494 DTL: CID=0x0b41 NIST(3433925659) StateCompleted->StateTerminated
336205:45:11.494 DTL: CID=0x0b3e NIST(3433925658) Event( Timer-J ) Interval: 32000
336205:45:11.494 DTL: CID=0x0b3e NIST(3433925658) StateCompleted->StateTerminated
336205:45:11.494 DTL: CID=0x0a82 NIST(3433925656) Event( Timer-J ) Interval: 32000
336205:45:11.494 DTL: CID=0x0a82 NIST(3433925656)

 
erik1701
11 posts since
Jan 31, 2008
1. May 16, 2008 2:11 PM in response to: dmigardos
Re: MWI (Message Waiting Indication) with opensbc & asterisk
I too get this from my opensbc. I really would like to have a definite answer as to why this does not work. According to Joegen:


{quote:title=joegen wrote:}{quote}
We have tested MWI to work with sipX 3.8 where sipX is also the
registrar. I am not familiar with asterisk and how it handles MWI but
there shouldn't be any reason why it wouldn't work.

I am also using the latest from CVS, OpenSBC 1.1.5-3
 
dmigardos
3 posts since
May 9, 2008
2. May 22, 2008 9:32 PM in response to: erik1701
Re: MWI (Message Waiting Indication) with opensbc & asterisk

I guess this is a dead project.... openser media proxy here I come.
 
erik1701
11 posts since
Jan 31, 2008
3. May 22, 2008 9:56 PM in response to: dmigardos
Re: MWI (Message Waiting Indication) with opensbc & asterisk
I've done some more investigation about how Asterisk handles MWI, and discovered that Asterisk sends the MWI as an unsolicited NOTIFY, which OpenSBC cannot not handle. If anyone could code this into the CVS I think a LOT of people would be greatly appreciate it.
Click to view joegen's profile  
joegen
519 posts since
Apr 28, 2007
4. Jun 3, 2008 6:23 AM in response to: dmigardos
Re: MWI (Message Waiting Indication) with opensbc & asterisk

Hi Guys,

Why dont you setup a box and install the latest opensbc code there. Point it to your asterisk. Give me ssh access to it and details how I could test MWI. I'll see what I can do about it.

Joegen

 
erik1701
11 posts since
Jan 31, 2008
5. Jun 4, 2008 2:59 PM in response to: joegen
Re: MWI (Message Waiting Indication) with opensbc & asterisk

Joegen,

I have setup a test lab box with ssh access per your request. Details are included in the email I sent to you.


Thanks again,

Erik Boyer

Network Operations Specialist

 
dablackgreek
30 posts since
Jun 24, 2009
6. Jun 29, 2009 9:35 PM in response to: erik1701
Re: MWI (Message Waiting Indication) with opensbc & asterisk

Whats the status of MWI...

Any ideas... confirmed I see the Unsolicted Notifies

What can we help you with Joegen

Click to view joegen's profile  
joegen
519 posts since
Apr 28, 2007
7. Jun 30, 2009 7:09 PM in response to: dablackgreek
Re: MWI (Message Waiting Indication) with opensbc & asterisk
AFAIK, NOTIFY sent by asterisk for MWI is already being forwarded in the current version. What exactly is the problem?
 
dablackgreek
30 posts since
Jun 24, 2009
8. Jun 30, 2009 7:20 PM in response to: joegen
Re: MWI (Message Waiting Indication) with opensbc & asterisk
I am using the lastest RC5 Build for Windows... I am not getting my MWI to update on my Cisco Phones or my Grandstream Phones
Click to view joegen's profile  
joegen
519 posts since
Apr 28, 2007
9. Jun 30, 2009 7:26 PM in response to: dablackgreek
Re: MWI (Message Waiting Indication) with opensbc & asterisk
Please attach your level 5 log here starting from REGISTER up to the NOTIFY that was dropped
 
dablackgreek
30 posts since
Jun 24, 2009
10. Jun 30, 2009 8:25 PM in response to: joegen
Re: MWI (Message Waiting Indication) with opensbc & asterisk

Joegen,

Scratch issue...

FYI: If using OSBC in front Asterisk, remember to set NAT and QUALIFY on SIP EXTENSION to "NO"

Else SOBC behaves weird

Regards

Greek

Actions

More Like This