Hello, Recently I've noticed that phones on our Audiocodes MP-124 adapter do not get the message waiting indicator. It seems like this behaviour has started a while ago after some upgrade (don't know whether it was Freeswitch or Audiocodes). The current versions are FS 1.0.6 and AudioCodes 5.6
From various tests I've done with SIPSACK and tcpdumps I find the following:
- after a Register command a "correct" notify is sent (i.e., the AudioCodes understands it). - later on "incorrect" notify's are sent which are rejected by the AC with "user not found". The "correct" notify is: NOTIFY sip:80633@10.64.0.8:5060 SIP/2.0 Via: SIP/2.0/UDP 10.64.0.3;rport;branch=z9hG4bKap2H5DSe6Zm7a Max-Forwards: 70 From: <sip:80633@pbx-gr.XXX>;tag=vtgH30805ZH1Q To: <sip:80633@pbx-gr.XXX>;tag=1c1710947583 Call-ID: 17109472461062010161640@10.64.0.8 CSeq: 131971366 NOTIFY Contact: <sip:80633@10.64.0.3:5060> User-Agent: FreeSWITCH-mod_sofia/1.0.6-svn-exported Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Event: message-summary Allow-Events: talk, presence, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Subscription-State: active;expires=7200 Content-Type: application/simple-message-summary Content-Length: 106 Messages-Waiting: no Message-Account: sip:80633@pbx-gr.XXX Voice-Message: 0/0 (0/0) While the "incorrect one" differs in the following two lines: From: <sip:80633@10.64.0.3 <sip%3A80633@10.64.0.3>>;tag=vtgH30805ZH1Q To: <sip:80633@10.64.0.3 <sip%3A80633@10.64.0.3>>;tag=1c1710947583 Taking the second one, changing the domain name and sending it with SIPSACK made it work correctly. (10.64.0.3 is the adderss of pbx-gr.XXX and 10.64.0.8 is the Audiocodes). Whose side is not working properly and should be asked to be fixed? Thanks! __Yehavi: