*8 And SIP

Home » Asterisk Users » *8 And SIP
Asterisk Users 5 Comments

Greetings all, First time poster, Sorry if this has been answered here before. We recently replaced a failed 1.4x asterisk PBX at a customer location. Voicemail access was setup when the customer dialed *8, This worked in
1.4. Now, Running 1.6 (I know it’s old I had to load it quickly, And that’s what I got working first. It’ll get upgraded to 1.8 soon). The strange part is *8 no longer works.The only CLI feedback I get is “=Using SIP RTP CoS mark 5”
In features.conf, Callpickup *8 is commented out, But just incase I also changed it to *7 (We don’t use that feature). It appears to be something completely SIP based, As if the call originates from DAHDI, It works fine.. If anyone has any ideas, Please let me know. Thanks!
SIP Trace Below

<--- SIP read from UDP:208.65.55.170:5063 --->
INVITE sip:*8@10.65.6.10:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.10.101:5063;branch=z9hG4bK908225576
From: “nicktest” ;tag70823868
To:
Call-ID: 695101044@172.16.10.101
CSeq: 1 INVITE
Contact:
Content-Type: application/sdp Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T46G 28.71.0.180
Supported: replaces Allow-Events: talk,hold,conference,refer,check-sync Content-Length: 308

v=0
o=- 20402 20402 IN IP4 172.16.10.101
s=SDP data c=IN IP4 172.16.10.101
t=0 0
m=audio 11792 RTP/AVP 0 8 18 9 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no a=rtpmap:9 G722/8000
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=ptime:20
a=sendrecv

<------------->
— (14 headers 15 lines) –

5 thoughts on - *8 And SIP

  • Maybe it’s a context issue. Check the dialplan context for the *8
    logic. Crank up the verbosity of the CLI and make a test call. You might have to reboot after the features.conf change.

    Adrian

  • Dialplan is solid..

    exten => *8,1,VoicemailMain(@default)
    exten => *8,2,Hangup exten => 88,1,VoicemailMain(@default)
    exten => 88,2,Hangup

    Also tried “_*8” in the dialplan at the request of a fellow BOFH.

    Using 88 temporarily, Which works fine. Also, DAHDI dumps into the same context and has no issue. I did indeed restart the service after any features change. I always run my CLI with about 8 million v’s, But still don’t get any useful feedback on this issue.

    I understand I can easily change the voicemail number. But this customer
    (hotel) has the voicemail number printed on in-room cards. So I’m hoping not to cause them a re-print. Nick Olsen Network Operations
    (855) FLSPEED x106

    ————————————–

  • I suggest trying command ‘features show’ to pinpoint the conflict.

    # asterisk -rx ‘features show’

    Builtin Feature Default Current
    ————— ——- —–

  • That did it.

    For some reason, Even commented out. Pick up was still *8. And persisted even after an asterisk service restart. Changed the feature to *7, Rebooted the whole PBX and it finally took effect.

    Nick Olsen Network Operations
    (855) FLSPEED x106

    ————————————–