[asterisk-bugs] [JIRA] (ASTERISK-25457) Chan_PJSIP No MoH / Hold

Rusty Newton (JIRA) noreply at issues.asterisk.org
Wed Nov 18 16:02:33 CST 2015


    [ https://issues.asterisk.org/jira/browse/ASTERISK-25457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228346#comment-228346 ] 

Rusty Newton commented on ASTERISK-25457:
-----------------------------------------

>Will the changes from the GIT repository be merged into the next release?

Yes they will. I'll go ahead and close this out then. Thanks for reporting back.

Also I'll mention the other issue that I found in case it is of use to you. When calling the Snom phone it fails to answer if the *display name* section of the From URI in the INVITE contains a format like "name <number>". Specifically the greater than and less than signs. When receiving a call as described the Snom does not respond upon lifting the handset or pressing the answer button. Very strange! I reported this bug to Snom.

> Chan_PJSIP No MoH / Hold
> ------------------------
>
>                 Key: ASTERISK-25457
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25457
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.6.0
>         Environment: Snom 7XX, SNOM 3XX, CISCO SPAXXXX
>            Reporter: Ross Beer
>            Assignee: Rusty Newton
>            Severity: Minor
>
> When using PJSIP with Snom and Cisco SPA phones MoH is not initiated. MoH works fine with queues etc.
> I believe the issue is that the phones are setting the 'sendonly' header on the invite instead of an IP address of 0.0.0.0. The 'sendonly' method does however work with chan_sip for all devices.
> {noformat}
> INVITE sip:<IPADDRESS>:5060 SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.104:8400;branch=z9hG4bK-5w3f4vtw2br5;rport
> From: "<NUMBER>" <sip:<USERNAME>@<IPADDRESS>>;tag=4fwufutws8
> To: <sip:<NUMBER>@<IPADDRESS>;user=phone>;tag=3e9c3595-e535-47fc-a5b2-d1e241b2c7b3
> Call-ID: 3134343433383534313932353436-c7z7ca4mvv41
> CSeq: 3 INVITE
> Max-Forwards: 70
> User-Agent: snom760/8.7.5.28
> Contact: <sip:<USERNAME>@192.168.100.104:8400>;reg-id=1
> X-Serialnumber: 000413710A91
> P-Key-Flags: resolution="31x13", keys="4"
> Accept: application/sdp
> Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE
> Allow-Events: talk, hold, refer, call-info
> Supported: timer, replaces, from-change
> Session-Expires: 3600;refresher=uac
> Min-SE: 90
> Content-Type: application/sdp
> Content-Length: 271
> v=0
> o=root 358968259 358968260 IN IP4 192.168.100.104
> s=call
> c=IN IP4 192.168.100.104
> t=0 0
> m=audio 65284 RTP/AVP 8 0 3 101
> a=rtpmap:8 PCMA/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:3 GSM/8000
> a=rtpmap:101 telephone-event/8000
> a=fmtp:101 0-16
> a=ptime:20
> a=sendonly
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list