OpenSBC is receiving the MWI from Asterisk through our MetaSwitch. The Meta sends a NOTIFY and the SBC comes back with a 404 not found. I have attached a SIP trace as a quote below:
---------------|------------------------------------------------------------
|192.168.1.200:5060
---------------|------------------------------------------------------------
15:41:37.90445 |--------------------------------->
|NOTIFY sip:4197583705@192.168.1.18
|0:5062 SIP/2.0
|Via: SIP/2.0/UDP 192.168.1.200;rpo
|rt;branch=z9hG4bK-895809f5bd1dde41
|fe7cfa28188b926e-192.168.1.200-1
|Allow-Events: message-summary
|Allow-Events: refer
|Allow-Events: dialog
|Allow-Events: line-seize
|Allow-Events: presence
|Max-Forwards: 70
|Call-ID: 39439448@192.168.1.200
|From: ;tag=192.168.1.200+1+0+ab9f392e
|CSeq: 1017433993 NOTIFY
|Organization: MetaSwitch
|Supported: 100rel
|Subscription-State: active
|Content-Length: 23
|Content-Type: application/simple-m
|essage-summary
|Event: message-summary
|Contact:
|To:
|Messages-Waiting: yes
|
---------------|------------------------------------------------------------
|192.168.1.180:5062
---------------|------------------------------------------------------------
15:41:37.91582 | <---------------------------------
| SIP/2.0 404 Not Found
| From: ;tag=192.168.1.200+1+0+ab9f392e
|
| To:
| Via: SIP/2.0/UDP 192.168.1.200;iid
| =11865;branch=z9hG4bK-895809f5bd1d
| de41fe7cfa28188b926e-192.168.1.200
| -1;rport=5060;received=192.168.1.2
| 00
| CSeq: 1017433993 NOTIFY
| Call-ID: 39439448@192.168.1.200
| Server: OpenSIPStack-1.1.7-21
| Content-Length: 0
We would like to use OpenSBC as our deployment of a Session Border Controller, as we can't really afford to buy a pizza box of somekind such as a Ditech; the only thing that is stopping us from really pushing our VoIP offers is MWI.
Network Operations
